>> link in the docs, and report it via the electronic Reader
On 24/06/2008, at 7:58 AM, CRPence wrote:
Word the /problem/ as a documentation issue for a
Comment from InfoCenter. That process requires that they
reply to you <<SNIP>>
I have difficulty wording this problem as a "documentation" error because as far as I can tell the documentation is correct. The
problem is that Rexx doesn't behave properly in certain specific
circumstances. I guess it could be worded as an omission in the
documentation i.e., Rexx documentation fails to state that calling an
external function with omitted parameters when a External Function
Exit Program is defined will fail with Error 48.
I'm sure anyone can see that adding such a statement to the Rexx documentation would not be the correct solution to the problem and I don't want to suggest a "fix it in the docs" solution.
Also, if you send me an email, I can forward the details to [someone who I know that can forward it to] the proper contact.
I'll send you a save file with code to reproduce the problem and instructions on how to prove the defect. Do you want that sent to
your yahoo address?
This mailing list archive is Copyright 1997-2013 by MIDRANGE dot 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 here. If you have questions about this, please contact