3 ms·
,---- | With C you are usually delivering a compiled binary executable. If | they did add a feature to C, you could use the new compiler on your | local deve
by signa11 9y ago
,----
| With C you are usually delivering a compiled binary executable. If
| they did add a feature to C, you could use the new compiler on your
| local development environment, and it wouldn't matter at all to the
| place you deployed it as long as you delivery a compatible binary.
`----
with C probably not, which has not been accumulating features for like
forever. C++ however, is another beast.
some machines might not have new fangled c++11 stuff
installed on them. sources that use these features, might have a tough time. as an example: c++11 introduced unique_ptr to the world. if you try to use that, you
might notice that not all of c++ gets compiled into the binary. some
of it e.g. libstdc++ lives on the disk as well, and gets linked during
runtime. this can now be fixed via some '-rpath' incantations or
'-static' linking (which increases the size etc.) perhaps then you
might start looking at 'LD_LIBRARY_PATH' ?
what about creating your own little sandboxes e.g. via chroot's ? but
if you step back a bit, all this boils down to is creating little
environments within which programs, which are supposed to be running
from command-line are now sequestered...
what a grate mess :)