RE: Problems with parameter passing

Yes, if passing literals, it seems there would still be a problem. However, I
can't remember the last time I coded a parameter literal in a CLP Call
command..... Still, I concede the point....

This seems to be more of a limitation of the CALL command. It might be nice to
be able to specify each parameter's descriptor (*Char 20, *Dec 9 0, etc.), but
it's generally not necessary since we can create *CMD objects.

Eric

-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx]On Behalf Of AGlauser@xxxxxxxxxxxx
Sent: Monday, June 11, 2007 12:21 PM
To: RPG programming on the AS400 / iSeries
Subject: RE: Problems with parameter passing


Eric DeLong wrote on 11/06/2007 12:22:29:

In a CLP (program), the compiler can determine the attributes of
data being passed, and will not need to analyze the parameter data
in order to declare storage. There are no ambiguities in compiled CL.

I understand how that would work if I was passing values by way of a
declared variable in said CLP. But what if you are passing literals? If
I have a CALL command in my CL that is exactly the same as what Glen said
he was typing on the command line, how would the CL compiler know what
attributes the data should have?

- Adam

Attention:

The information contained in this message and or attachments is
intended only for the person or entity to which it is addressed and may contain
confidential and/or privileged material. Any review, retransmission,
dissemination or other use of, or taking of any action in reliance upon, this
information by persons or entities other than the intended recipient is
prohibited. If you received this message in error, please contact the sender
and
delete the material from any system and destroy any copies. Thank you for your
time and consideration.

Attention:

Le contenu de ce message et(ou) les fichiers ci-joints s'adressent
exclusivement à la personne ou -entité à laquelle ils sont destinés. Ils
peuvent
contenir de l'information confidentielle, protégée et(ou) classifiée. Il est
strictement interdit à toute personne ou entité autre que le(la) destinataire
prévu(e) de ce message d'examiner, de réviser, de retransmettre ou de diffuser
cette information, de prendre une quelconque action en fonction ou sur la base
de celle-ci, ou d'en faire tout autre usage. Si vous avez reçu ce message par
erreur, veuillez communiquer avec l'expéditeur(trice), supprimer ce message et
les fichiers ci-inclus de tout système, et en détruire toutes copies, qu'elles
soient électroniques ou imprimées. Nous vous remercions de votre entière
collaboration.