16 Apr, 2010, Runter wrote in the 22nd comment:
JohnnyStarr said:
When you cpp?
I assume you mean use cpp? I don't know if this is a bad thing.
It might be a pain later on, it might not.
I assume you mean use cpp? I don't know if this is a bad thing.
It might be a pain later on, it might not.
I should have said stings. :)
16 Apr, 2010, JohnnyStarr wrote in the 23rd comment:
:rolleyes:
16 Apr, 2010, David Haley wrote in the 24th comment:
Well you have pretty much identified the issue when it comes to using code from a very recent standard. It sounds like you don't really need to care given what you plan on doing with it. If I were you, I wouldn't – you're using standards that will be widely implemented later, it's not like it's some secret extension to g++ that you've hacked in.
Still, if you like all those features like lambda functions etc., and aren't wedded to C++, I would go with a language that gives you all that and more, and more deliberately from the language's onset.
Still, if you like all those features like lambda functions etc., and aren't wedded to C++, I would go with a language that gives you all that and more, and more deliberately from the language's onset.
Random Picks
I assume you mean use cpp? I don't know if this is a bad thing.
It might be a pain later on, it might not.