The facts are interesting, the conclusion doesn't make any sense at all to me.
578 karma · joined January 31, 2017
The facts are interesting, the conclusion doesn't make any sense at all to me.
Possibly interesting links:
https://www.autodeskresearch.com/people/gord-kurtenbach#pate...
Display and control of menus with radial and linear portions https://patents.google.com/patent/US5926178
Methods and system of controlling menus with radial and linear portions https://patents.google.com/patent/US5689667A
Method and apparatus for producing, controlling and displaying menus https://patents.google.com/patent/US6618063B1
The worst aspect was that through all this time my mind was always telling me that, yes, I have some problems, but what if I don't have anything at all? Maybe if I ever did see a doctor about it, I would be wasting their time. It wasn't even about whether or not they would take me seriously. My biggest fear was that a doctor would tell me that there's nothing wrong with me. It's really the worst of all the "what if"'s that Wil was talking about, because that was the one that kept me from getting help.
When I build C++ stuff at home I go to great lengths to shave milliseconds off my compile time, because it is just so much better to have your program built in under 2 s than in 2 minutes.
You're not going to find out if somebody is happy by "casually being around".
> Don’t neglect your family and friends for the sake of productivity—that’s a very stupid tradeoff (and very likely a net productivity loss, because you’ll be less happy). Don’t neglect doing things you love or that clear your head either.
Really? This is news?
If the class is being used, then the definition has got to be somewhere, hopefully in a header. It's simply a file that is included somewhere. And it will be human readable. There is no magic.
// This %thing% was generated from %template% using data from %data%.
If your language is too restrictive to add sensible tools, you should write the tools yourself. As with any code, write it in a way such that other people will be able to understand it.
There is no magic, it's just code. I wish people would stop using that word.
> The ability to write generic reusable programs, called polymorphism, is fundamental to advanced software engineering. I am interested in static type-systems providing polymorphism without the use of subtyping. The problem with subtyping is that it imposes significant restrictions on reuse when static type-checking is required. This work has resulted in a new dialect of C language, called Cforall, which adds parametric polymorphism and extensive overloading to provide a more general type-system.
I don't think that's necessarily true. It depends on the implementation. In an actor based system, the syntax might not change that much. You just sprinkle in some async() here and some yield() there. So the code still looks like it is using function calls, and uses the stack/instruction pointer for state management, but is running asynchronously.
I do very much agree with you point about coupling.
What is the scope? Is this an open source project? How many people are working with it?
To me it looks like this is a personal project that only you are working on. I don't see any problem using this approach. I mean, I use a batch file as my build "system" for my personal projects. But for anything else it would be worth discussing the trade-offs versus using one of the available build systems.
I didn't understand how this works: scanCmd = 'scanincludes-%s' %(oPath). What is this scanincludes thing?
Maybe you ran into this issue? https://www.myce.com/news/windows-7-dont-receive-security-up...
My strategy was to start with a very small grammar and grow it.