On Monday 05 June 2006 16:54, Stephen Pelc wrote:
> On 5 Jun 2006 at 15:04, Bernd Paysan wrote:
> > Not really. The PC has a 8042 based keyboard, which is then
> > translated to the X keyboard event (which is an abstraction for
> > quite a number of different possible keyboards, and developed when
> > Linux PCs where not even thought about). It then goes into a xterm,
> > which emulates a VT102 terminal.
>
> I take your point, but both start from the Linux kernel and
> libc. There are other operating systems.
From VAX to zSeries: They all can work with X servers, by mapping key
strokes to KeySyms. And the same works on Windows and Mac OS, which are
again different, but sufficiently similar. I can use a Windows machine
to log into Anton's b3, and hit the F2 key, and Gforth will recognise
this correctly, again.
> The point at issue is really that the proposal seems to be
> derived from writing editors in GUI desktop applications. I
> regard this as a library issue, and increasingly would like to
> see some separation of language and library. This does not mean
> that I want the same separation as in the "C Standard library".
> I'm arguing that there are at least three major application
> domains, and that we should recognise this. The -EXT labelling
> is inadequate for this.
The -EXT labelling is "you may or may not implement it", which is indeed
not very adequate. You may label this -PC, aka "you are supposed to
implement it when you have a PC-style keyboard".
> LIB: Desktop key handling for Linux and libc
This is not limited to Linux and libc in any way.
> and some problems go away, otherwise the Forth200x standard is
> in danger of being perceived as the gForth extension standard.
> Has anyone implemented this EKEY under the Windows API or
> Symbian?
On Windows: Yes, definitely. Win32Forth implements something that
differs from this RFD only that it uses '_' instead of '-' in the name.
> A standard should be derived from common practice, maybe from
> another language. What common pratice does this proposal have in
> Forth *applications* as opposed to *kernels*?
--
Bernd Paysan
"If you want it done right, you have to do it yourself"
http://www.jwdt.com/~paysan/