Re: Prototyping printf()

Simon wrote:
>Then don't use printf() as justification :)  but move it up the list
please!  Although I
>don't see operational descriptors helping in this case (unless I wanted to
write my own
>printf-like function in which case I would need to know the data types).
This problem is
>all in differences between language parameter passing preferences -- VALUE
vs. REFERENCE
>- -- and prototyping limitations.  But now you guys know that at least
some of us want that
>sort of support so I'm sure it'll get on the ToDo list  :)

I think we're all in agreement that we need some form of improvement
in parameter passing and parameter description.  But we're in a
serious case of buck-passing here regarding operational descriptors.
Toronto is waiting on Rochester, and Rochester is waiting on some
other site.  As soon as Rochester gets the go-ahead, we'll have our
bit done in no time!  There are also other good proposals regarding
interface descriptors that aren't getting the attention they deserve.
These things are important enough that we here in TO really don't
need any more convincing.

BTW, I'm glad there aren't many Perl and Python programmers reading
this list.  These interpreted languages can do things with parameter
passing that give us compiler writers nightmares!

Cheers!  Hans

Hans Boldt, ILE RPG Development, IBM Toronto Lab, boldt@ca.ibm.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
+---