Daniel Richard G. dixit:

>I don't think there would be any instance where the code needs to know
>"I am building for EBCDIC 1047" vs. "for EBCDIC 037" or whatnot. The
>transcoding of char/string literals should be all that's needed.

Unless we convert EBCDIC to Unicode ourselves (as opposed to letting
the system do it; I’m currently convinced that we really want to do
this actually, since we don’t support them all anyway).

>(I think the compiler throws an error if some literal character cannot
>be transcoded, so we would not need to worry about EBCDIC variants that
>lack basic ASCII punctuation or lowercase letters.)

Good.

>I suppose you could leave it up to the user to create e.g. a mksh ->
>zmksh symlink.

Sure, the local admin rules supreme anyway after all.

>> So we assume EBCDIC 1047 mksh + EBCDIC 037 user is allowed to fail,
>> and we only really have to support the code page used at compilation.
>
>Yes, exactly. To do otherwise would be way too much work, for a platform

OK.

>If all of mksh's input/output is being filtered via conversion tables

It isn’t, it never is. That would just be insane ;-) Only some.

>I think that sounds right. Maybe call the binary "emksh"? As much as

Okay, emksh and EBCDIC [ML]KSH it is.

>Very nice hack! I do prefer analog clocks myself.

;-)

I don’t care as long as the clock also shows the day and month,
and preferably also the day-of-week. I tend to not know them.
Oh, and, i̲f̲ I have a clock, it better go right, so it should
do NTP or DCF77 (sadly, most DCF77 clocks only sync once a day
or month or when you trigger it manually, not constantly, so
they are off most of the time, especially when they are often
in buildings that shield radio signals well).

>> Now go get some sleep ;-)
>
>Still working on it...

Ouch. I got some myself, but not enough…

bye,
//mirabilos
-- 
If Harry Potter gets a splitting headache in his scar
when he’s near Tom Riddle (aka Voldemort),
does Tom get pain in the arse when Harry is near him?
        -- me, wondering why it’s not Jerry Potter………

Reply via email to