Linked by Eugenia Loli on Fri 11th Nov 2005 00:44 UTC, submitted by esther schindler
Permalink for comment 59188
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 05/25/13 0:45 UTC
Linked by Thom Holwerda on 05/24/13 23:59 UTC
Linked by Thom Holwerda on 05/24/13 22:33 UTC
Linked by Howard Fosdick on 05/24/13 21:41 UTC
Linked by Thom Holwerda on 05/24/13 14:44 UTC
Linked by Thom Holwerda on 05/23/13 23:22 UTC
Linked by Thom Holwerda on 05/23/13 22:04 UTC
Linked by Thom Holwerda on 05/23/13 22:01 UTC
Linked by Thom Holwerda on 05/23/13 17:52 UTC
Linked by Thom Holwerda on 05/22/13 22:23 UTC
More News »
Sponsored Links



Member since:
2005-11-11
Of course I don't know that, but there has to be some reason they put the message in there.
From the article:
Author Kate Gregory explained that the code construct presents a security weakness in a programmer's code. "You can turn off that error checking," Gregory said, "but you probably don't want to."
So then there should be a better way to do things, I'm just wondering what way that is. There's not much point in warning you about something if you can't change it to something better.