|
Authored by: artp on Sunday, May 06 2012 @ 11:12 AM EDT |
Don't worry! If Oracle gets their way, and their absurd
claims go to their [il]logical conclusion, the CS and
engineering programs will no longer be able to teach
rangecheck functions.
That's the problem with trying to extrapolate from this mess.
I keep coming up with doomsday scenarios.
---
Userfriendly on WGA server outage:
When you're chained to an oar you don't think you should go down when the galley
sinks ?[ Reply to This | Parent | # ]
|
|
Authored by: Anonymous on Sunday, May 06 2012 @ 04:08 PM EDT |
If I read the description right, rangecheck only checks whether the index of the
requested item falls within the range of the list / array being addressed.
I used to do this as a standard practice when programming in Delphi, even had a
macro for it. I used only one line, something along the lines of:
Assert((index > -1) and (index < List.Count), 'Index out of range');
If the assertion failed (condition is false), an exception whould be raised
using the provided text. I used to add class and method name as well.
If this is infringing, because the same programmer followed industry best
practices somewhere else as well, it would boggle the mind.[ Reply to This | Parent | # ]
|
|
|
|
|