RE: Prototyping printf()

Jon:

I think that it should be architected.  I agree that Toronto can do this but
I want to see it extractable from the EPA-level object, not in the
associated space.  I do understand what that means for timing and review but
it also goes to commitment.  There is nothing temporary about this
requirement - this one is forever.

The results from putting SQL package data in the associated space should
convince almost anyone.

Richard Jackson
mailto:richardjackson@richardjackson.net
http://www.richardjacksonltd.com
Voice: 1 (303) 808-8058
Fax:   1 (303) 663-4325

> |-----Original Message-----
> |From: owner-rpg400-l@midrange.com [mailto:owner-rpg400-l@midrange.com]On
> |Behalf Of Jon.Paris@hal.it
> |Sent: Wednesday, September 27, 2000 12:04 PM
> |To: RPG400-L@midrange.com
> |Subject: Re: Prototyping printf()
> |
> |
> |
> | >> What I have in mind is the ability for a compiler to extract
> |"prototype" information from a module or service program, similar to the
> |way Java can extract information directly from a compiled class.  Just a
> |dream ...
> |
> |Hey - just stick the information in the associated space and retrieve it
> |from there - heck if you put it there we'll retrieve it ourselves!
> |
> |Come on Barbara we know you can knock code like that out in your lunch
> |break <vbg>
> |
> |+---
> || This is the RPG/400 Mailing List!
> || To submit a new message, send your mail to RPG400-L@midrange.com.
> || To subscribe to this list send email to RPG400-L-SUB@midrange.com.
> || To unsubscribe from this list send email to
> |RPG400-L-UNSUB@midrange.com.
> || Questions should be directed to the list owner/operator:
> |david@midrange.com
> |+---

+---
| This is the RPG/400 Mailing List!
| To submit a new message, send your mail to RPG400-L@midrange.com.
| To subscribe to this list send email to RPG400-L-SUB@midrange.com.
| To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---