RE: Prototyping a constructor of java String class

["Steffan, Otto \(GE Consumer Finance\)" <Otto.Steffan@xxxxxx>]

Hello Barbara,

thank You for Your contribution, I am afraid it'll take me some time to process 
it in my mind to extract the answer to my initial question.

Just a note to
>Regarding performance of parameters, for CONST parameters, usually no
>temporary is created if the format of the passed parameter matches the
>prototype.  So if you will most often be passing varying length
>parameters, code VARYING, and if you will most often be passing fixed
>length parameters, code OPTIONS(*VARSIZE) without VARYING.  (This
>parameter passing stuff applies to all calls with CONST, not just Java
>method calls.)
I undestand that if I MORE often pass fixed-length field, VARYING is still 
possible but not very good because parameters do not match(?) and RPG must 
handle it. 
Does it mean that my idea of having a single prototype for String constructor 
is basically wrong ? I have intended the prototype available to the RPG 
programmers here (knowledge of Java support in RPG has not spread here yet) and 
I do not know which parameter passing method will prevail.

Best regards
Otto Steffan