On 2012-02-21 14:55, McKown, John wrote:
Good point. I use set symbols for unprintable characters. Like:
&TAB SETC BYTE(05)
VAR DC C'This has a&TAB. tab in it.'
This raises an interesting question. How does a cross assembler
running on an ASCII platform and processing source code which
may or not antedate the BYTE BIF know whether a hex constant
is intended to be an EBCDIC character or a binary number?
In your example, the elaboration of the BYTE() must be deferred
until after other ASCII->EBCDIC translation is finished.
-- gil
