× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Jerry:

<snip>
Reminds me of a colleague back in the 70's programming in COBOL on a 
370.  Was having a devil of a time debugging a program; kept getting 
random results even though the data and program remained unchanged.  
Turns out, he said, that a program array was defined with X elements.  
Some variable was using something like X + 1.  Unlike RPG's array index 
error, apparently the COBOL program (at least then) just said, "OK, if 
that's what you want, I'll resolve to that address and give you whatever 
I find."
</snip>

I can vouch for this behavior.  In fact this was the standard hack used if
you needed an array larger than what COBOL allowed.  I remember needing a
very large, multi-dimensioned array with about 150 elements.  The compiler
choked whenever I specified more than 60.  So I left the dimension at 60,
then defined enough "filler" immediately after that to cover the other 90
elements and had no problem referring to all 150 elements!  This is
consistent to what others have been saying about it only "pretending" size
dynamically.

Scary...just scary,
--Bruce Guetzkow



As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.