For readability, `then` allows splitting with newlines very long conditional expressions, without having to wrap the condition in parentheses: if x + y + z > a or verylongconditionalhere () or…
Still true for C++. Can still mentally map new features to the core language C. A modern Cfront transpiler can still be written. Template meta-programming maps to C pre-processor macros. The sad part with both is…
That place is C++/Lua, with most of the code in Lua. Concurrency model is thread-per-lua-state. Interthread comms is message passing implemented via textbook c++11 atomic and condition variables. Lua is just a small C…
PHP should do a real major compatibility break and remove $ sigil from variable names. It's gonna be worth the pain!
Tl;dr: it's an autoconf problem Article also misses: comparing speed of full rebuilds. Pch gives massive speedup on edit-compile-debug cycle or when several modules can share a single pch.
Yes you should. You'll need a glob function, cd/getcwd/setcwd, pretty-printer. That's about it. Lua stdlib replaces sed, awk, grep, cut, tr, tail, etc. Startup time is the best. In my testing, a lua script that…
Load the table. Modify. Serialize to file. Not too hard. Emacs does it with the .emacs file, mixing generated and manual content.
Lua is C in Lisp's clothing. Lisp killer features were GC, good data representation, first class functions. Lua has all that and more. But its being a "thin" library over the C runtime shows through the clothes.
You are correct wrt to iostream, it's bad. I stick to studio.h.
It's probably auto when you wanted auto&. A copy was made instead of a reference. I've been bitten by that.
For readability, `then` allows splitting with newlines very long conditional expressions, without having to wrap the condition in parentheses: if x + y + z > a or verylongconditionalhere () or…
Still true for C++. Can still mentally map new features to the core language C. A modern Cfront transpiler can still be written. Template meta-programming maps to C pre-processor macros. The sad part with both is…
That place is C++/Lua, with most of the code in Lua. Concurrency model is thread-per-lua-state. Interthread comms is message passing implemented via textbook c++11 atomic and condition variables. Lua is just a small C…
PHP should do a real major compatibility break and remove $ sigil from variable names. It's gonna be worth the pain!
Tl;dr: it's an autoconf problem Article also misses: comparing speed of full rebuilds. Pch gives massive speedup on edit-compile-debug cycle or when several modules can share a single pch.
Yes you should. You'll need a glob function, cd/getcwd/setcwd, pretty-printer. That's about it. Lua stdlib replaces sed, awk, grep, cut, tr, tail, etc. Startup time is the best. In my testing, a lua script that…
Load the table. Modify. Serialize to file. Not too hard. Emacs does it with the .emacs file, mixing generated and manual content.
Lua is C in Lisp's clothing. Lisp killer features were GC, good data representation, first class functions. Lua has all that and more. But its being a "thin" library over the C runtime shows through the clothes.
You are correct wrt to iostream, it's bad. I stick to studio.h.
It's probably auto when you wanted auto&. A copy was made instead of a reference. I've been bitten by that.