Linked by Eugenia Loli on Sun 16th Dec 2007 00:04 UTC, submitted by obsethryl
Permalink for comment 291695
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 06/18/13 22:33 UTC
Linked by Anonymous on 06/18/13 22:26 UTC
Linked by Thom Holwerda on 06/18/13 22:25 UTC
Linked by Thom Holwerda on 06/18/13 17:45 UTC
Linked by Thom Holwerda on 06/18/13 17:32 UTC, submitted by poundsmack
Linked by Thom Holwerda on 06/17/13 17:58 UTC
Linked by Thom Holwerda on 06/17/13 17:52 UTC
Linked by Thom Holwerda on 06/14/13 21:03 UTC
Linked by Thom Holwerda on 06/14/13 20:46 UTC
Linked by Thom Holwerda on 06/14/13 17:32 UTC
More News »
Sponsored Links



Member since:
2005-08-31
Of course it will catch as many error as possible, but when you compare python with C++ (or any compile vs runtime language), it's not accurate to say that all the errors you'll find will be somewhere undetected in a python program.
Just to bring one, there's many type in C++ that needed to be check where in python it doesn't matter at all. Like integer, in C++ the compiler need to check for int, long, unsigned, etc. In python, who cares? it's an integer. If you do some mixing in C++, the compiler will complain, but these errors are irrelevent in python. So as many errors in C++ are far less in python. (but I agree that some will not be check)
At the end it is a matter of design and the quality of code. Bad python code will end on error, bad c++ might throw a buffer overflow.
the first problem for portage that he said is :
I think this is the real issue. Not C++ or Python or whatever.