"Ewww GOTOs"?
Erm....sometimes GOTOs can save time...
If you really want to be structured, you''re not even allowed to return early from a function but rather must save the value in a variable and force control to fall through, so...
Screw the structure when performance is needed, and keep it if you want readable code. Personally I don''t see why a few GOTOs are bad.
See Anything I missed(source)
okay, i haven''t looked through it properly, but...
1. at first glance i cant see where you are deleting Object.
(remember to use delete []Object
2. you are defining temp as 32 charcters. and then using fscanf.
i wouldn''t do that... the string could be longer then 32 chars!
(imagine a corrupt file) and will crash if it is.
try to set temp to be 8000 or so for now, with a view to replace
it in the future. near future.
PS: STL stands for "Standard Template Library".
1. at first glance i cant see where you are deleting Object.
(remember to use delete []Object
2. you are defining temp as 32 charcters. and then using fscanf.
i wouldn''t do that... the string could be longer then 32 chars!
(imagine a corrupt file) and will crash if it is.
try to set temp to be 8000 or so for now, with a view to replace
it in the future. near future.
PS: STL stands for "Standard Template Library".
This topic is closed to new replies.
Advertisement
Popular Topics
Advertisement
Recommended Tutorials
Advertisement