RE: [Cobolforgcc-devel] MOVE subroutine in UNSTRING
Status: Pre-Alpha
Brought to you by:
timjosling
From: William M. K. <wm...@ix...> - 2001-04-09 21:23:09
|
Tim, In terms of "priority" - I would delay support for "P" and (possibly?) "0" picture clause items. I believe these are: - little used - poorly defined - basically unneeded if you support 31-digit numeric items and the new BINARY-xxxx and FLOAT-xxxx Usages If you gave a "compile-time" error when such items were "defined" and put these in an "eventual" list of things to do, I don't think many programs/programmers would be "bothered". > -----Original Message----- > From: cob...@li... > [mailto:cob...@li...]On Behalf Of Tim > Josling > Sent: Monday, April 09, 2001 4:09 PM > To: cob...@li... > Subject: Re: [Cobolforgcc-devel] MOVE subroutine in UNSTRING > > > Steven, > > You are right. String is OK. > > For unstring the receiving area must not be justified but may be > an integer without 'P' in the PIC. So it could be usage anything > - binary, packed, display. > > I will have to think about how to structure this. > > Tim Josling > > "Steven O. Ellis" wrote: > > > > Tim, > > > > STRING is OK. The following rule disallows a right-justified receiving > > item. Identifier-3 is the receiving item. > > > > 6.25.3 Syntax rules > > > > 4) Identifier-3 must not represent an edited data item and must > > not be described with the JUSTIFIED clause. > > > > However, for UNSTRING, the receiving area may be numeric. UNSTRING > > General Rule 6.27.3 (2) refers to the sending area, not the receiving > > area. I do believe there is the potential for a numeric move per > > General Rule 6.27.4 (13c), quoted below. And per MOVE General Rule > > 6.19.4 (4b), when the receiving area is numeric and the sending area is > > alphanumeric, "data is moved as if the sending operand were described as > > an unsigned numeric integer." > > > > This is not something that needs to be resolved at once, but I am > > thinking that the final version of UNSTRING is going to have to be able > > to handle a more sophisticated move. > > > > Steven > > _______________________________________________ > Cobolforgcc-devel mailing list > Cob...@li... > http://lists.sourceforge.net/lists/listinfo/cobolforgcc-devel |