I would find it extremely unlikely that _any_ existing code was taking advantage of the fact that the program continued to execute the SUBR statements. Given your mantra, nothing would ever get fixed, just in case someone had taken advantage of something that was a bug.

I understand your intent, but I think you're defending a position that can't be defended...

----- Original Message ----- From: "Luis Colorado" <LuisC@xxxxxxxxxxxxxxxx>
To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>
Sent: Tuesday, January 29, 2008 12:52 PM
Subject: RE: Strange CL problem with SUBR


Well, it would be *less* unfortunate. As I said, some people may actually have code using this quirk -not stopping at a SUBR statement- intentionally, or eve unintentionally, so if IBM fixes is, IBM may actually break the code of that people.

I know it's an unlikely scenario, but I don't like seeing fixes that break existing code. That's one of the success secrets of the iSeries.




As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

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.