[Info-vax] AlphaVM-free emulator with all additional peripheral components

[Bill Gunshannon]

In article <jvgoc4$q3r$1 at speranza.aioe.org>,
	glen herrmannsfeldt <gah at ugcs.caltech.edu> writes:
> Bob Koehler <koehler at eisner.nospam.encompasserve.org> wrote:
>> In article <jvelpr$3ka$1 at speranza.aioe.org>, glen herrmannsfeldt <gah at ugcs.caltech.edu> writes:
>>> 
>>> Does remind me of trying to get a S/370 disassembler, written
>>> in C, to run under unix/ASCII. All the symbols from the object
>>> program come out in EBCDIC and need to be converted.
> 
>>   Written in C?  I thought EBCDIC didn't have {}, isn't that why
>>   RATFOR allowed <> as substitutes?
> 
> I believe the TN print train has them, though I don't remember
> using them. (The more common print trains don't.)
> 
> In any case, there have been EBCDIC versions of C for some time now.
> (C has substitutes for some characters, too.)
> 
> Also, reminds me of comments in the PL/I (F) library related to
> the character set used. Many routines are specifically character
> set independent. Others have comments indicating that if converted
> to a different character set (or, at least, character constants
> are converted) then they will work in that character set.
> 
> The Tachyon assemblers allow source input in either ASCII
> or EBCDIC, but assemble constants in EBCDIC in either case.
> (Maybe there is an option to assemble constants in ASCII.)
> 

While I never did C on an IBM mainframe I do remember getting C
programs thru BITNET and having to run them thru a program I wrote
to ASCIIfy them before I could use them on other systems.

Hmmm...  Wonder if that program is still sitting somewhere in my
files at the University?

bill

-- 
Bill Gunshannon          |  de-moc-ra-cy (di mok' ra see) n.  Three wolves
billg999 at cs.scranton.edu |  and a sheep voting on what's for dinner.
University of Scranton   |
Scranton, Pennsylvania   |         #include <std.disclaimer.h>