Re: [Cobolforgcc-devel] MOVE subroutine in UNSTRING

[Tim J. <te...@me...>]

Steven,

OK. The main priority for me is to get the pic x(n) ones done.
Later on when I add support for all the esoteric types we can
plug in the mover routine. You are welcome to add support for the
numerics but I would prefer to have enums passed rather than PIC
characters or strings. If you need a new enum then make it up.

I don't know why leading sign seperate is not there. I assume it
will have to be added later on. Just having a quick look I think
the comments in the file may be wrong. I will check. 

Tim Josling

"Steven O. Ellis" wrote:
> 
> Tim,
> 
> Fair enough.  I propose yet another parameter containing the picture
> character string for each receiving area.
> 
> As Bill suggests, "P" and "0" can be disallowed for now, and for the
> immediate purposes, I would disallow "V" and anything else except
> {X,S,(,),0,1,2,3,4,5,6,7,8,9}.  "0" would be allowed only within
> parentheses.  The receiving area could then be text, signed integer, or
> unsigned integer.  I think that would make the UNSTRING routine
> "seaworthy" for the time being.
> 
> Receiving areas will be USAGE DISPLAY because:
> 
> 6.27.3 Syntax Rules
> 
> (3) Identifier-4 may be described as either the category alphabetic,
>     alphanumeric, or numeric (except that the symbol 'P' may not be
>     used in the PICTURE character-string), and must be described
>     implicitly or explicitly, as USAGE IS DISPLAY.
> 
> There is one other thing, though.  In the set of usage flags currently
> defined in cobr_temp_config.h, there is "SIGN IS TRAILING SEPARATE", but
> no "SIGN IS LEADING SEPARATE".  This simplifies the problem.  But will
> the COBOLforGCC implementation always require a separate sign to be
> trailing, or will this be changed in the future?
> 
>         Steven
>