Re: C90 fpeek

"Scott Lurndal" <scott@slp53.sl.home> wrote in message
news:fbUkP.928259$2xE6.372374@fx18.iad...

I don't recall ever using stdio streams myself for any real world
problem - for terminal input I generally use libreadline or libedit;
for serial port input/output, open + tcsetattr + fcntl (usually with
O_NOCTTY) + read or write.

And this is the difference I guess.

I am not trying to solve a particular real world problem that
an employer is paying for.

I am trying to DEFINE a world based on nothing but C90.
You could possibly call it a "limited world" rather than a
"real world". I'm not expecting commercial success with
this position.

However, I do recognize that the C90 committee (plus
existing practice) were not perfect in the late 1980s. So
with the benefit of hindsight, and without time pressure,
I'm willing to revisit C90.

In order to get a fullscreen editor I didn't see any good
option but to add ANSI X3.64 and an EBCDIC equivalent.

You could argue that if I'm willing to add ANSI X3.64,
why not also add C23 and POSIX and ...

I don't have a good answer to that, other than I'm trying
to keep movement away from C90 to a minimum.

I've mentioned before I need an ESC_STR and likely
other control characters to extend C90 (on top of
ANSI X3.64) to avoid having to hardcode hex values
in my applications.

I'm happy to remove sin() etc.

And now I'm looking at an fpeek().

And that "looks neat" to me. I realize I can't mathematically
prove that it is neat (and that irks me), but that's the world
that I want to create (not particularly expecting anyone to
join me in that world - not expecting to get any money from
it - but I want it to exist anyway - a "roughly C90" world).

Note that z/PDOS-generic is a great start (in my opinion) -
if the mainframe can operate in a C90 world, most other
environments should be able to as well.

BFN. Paul.