fep

Kazumasa Utashiro utashiro at sran84.sra.JUNET
Fri Nov 18 17:30:19 AEST 1988


In article <2626 at uhccux.uhcc.hawaii.edu>
	lee at uhccux.uhcc.hawaii.edu (Greg Lee) writes:

>> Here are a couple minor changes to the fep program that was just
>> posted in comp.sources.unix.  (1) re#defines CTRL to what the
>> code apparently supposes it to mean, (2) changes an error check
>> of the malloc return value from '<= 0' to '== 0'.

Thank you Lee. I'm very glad to hear someone is using my tool.
However, according to your definition of CTRL ('c'-64),
CTRL(D) makes 004 (control-D) but CTRL(d) makes 044 ($).  Is
this a correct definition for CTRL?

Your fix for malloc's return value is correct. I didn't find
it because compiler of my UNIX system doesn't complain about
it.  It is fixed in current version of fep.  I already sent 3
patches of fep to Mr. Rich Salz.

Note that this program assumes that the negative address in
32bit integer should be kernel address space, and using the
MSB of address for indirect flag in binding table.  So,
probably fep won't work on the system that uses negative
value for user address space anyway.  It might be better to
cast malloced value to signed integer and make sure it has
positive value. (ugly? yes it is.)

>> Fep has support for Kanji entry and I'm wondering if I can
>> use it.  The program notes say you have to have "ASCII UNIX".
>> What's this?  Can someone explain?

Sorry for confusion.  I wrote "ASCII UNIX" as "ASCII Corp's
Japanese enhanced UNIX system", which can handle Japanese
character set in it.  Official name for it, probably, is
"ASCII UX/4.3bsd system".  Supporting "ASCII UNIX" means fep
is using its libraries like iskanji(3) and some special
ioctrls for tty driver.  Unfortunately, there are no
standard for these kind of Japanization (Sigma? Who are you?).

Kazumasa Kayo Utashiro
Software Research Associates, Inc.
1-1-1 Hirakawa-cho, Chiyoda-ku, Tokyo 102, Japan
	UUCP:	kddlab!srava.sra.junet!utashiro
	ARPA:	utashiro%sra.junet at uunet.uu.net
	JUNET:	utashiro at sra.junet



More information about the Comp.sources.bugs mailing list