|
This type of thing always strikes me as being "programming archeology", in
that you had to be there to really know why something was done (what it is
doing is not too hard to discern, but the "why's" become dimmer over time).
There should probably be some project launched as a wiki to collect and
document these kinds of idioms. Somebody 10 years from now won't have any
idea why this was done, and those who remember, well, they might not be on
this list. Legacy COBOL is probably the same way (to pick another widely
used language with an enormous legacy code base).
As an Amazon Associate we earn from qualifying purchases.
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.
midrange.com
