Path: utzoo!news-server.csri.toronto.edu!rutgers!usc!snorkelwacker.mit.edu!thunder.mcrcim.mcgill.edu!mouse
From: mouse@thunder.mcrcim.mcgill.edu (der Mouse)
Newsgroups: comp.sys.next
Subject: Re: XNeXT on NextStep 2.0?????
Message-ID: <1991Mar10.120604.18434@thunder.mcrcim.mcgill.edu>
Date: 10 Mar 91 12:06:04 GMT
References: <1991Mar5.232508.20719@msuinfo.cl.msu.edu>	<1991Mar7.140806.13975@wam.umd.edu> <SCOTT.91Mar7204438@erick.gac.edu>
Organization: McGill Research Centre for Intelligent Machines
Lines: 34

In article <SCOTT.91Mar7204438@erick.gac.edu>, scott@erick.gac.edu (Scott Hess) writes:
> In article <1991Mar7.140806.13975@wam.umd.edu> charlie@wam.umd.edu (Charles William Fletcher) writes:
>> I also question binary compatiblity

As do I.  I had a perfectly good program that didn't even *touch* the
NeXTisms and it broke subtly on 2.0.  I'm still not sure just what
broke.  (To make things worse, it wouldn't recompile on 2.0; I had to
hack on it.  Apparently NeXT decided they wanted to get even farther
from UNIX compatibility than they were before.)

> mouse-X has similar problems, I believe, in that the author, while a
> good programmer,
(Thank you!)
> is not a good _NextStep_ programmer

Not a NextStep programmer at all, if I can help it.  Why do you think I
ported X?  (For the rhetoric-impaired: because I can't stand NextStep.)

> If you look at the sources, you realize rather quickly that these
> were not generated by someone out of developer's camp!  I guess I was
> sort of surprised that they ran under 1.0 :-).

:-)  Well, I really had little choice.  The raison d'etre of the thing
violates the GUI spec - or so I assume; it seems unlikely that the spec
permits programs to take over the whole screen - and NeXT didn't
document their lower-level interfaces.  So I had to dig through .h
files and what documentation there was, until I managed to make it
work.  Of *course* it looks kludged up; it is!

					der Mouse

			old: mcgill-vision!mouse
			new: mouse@larry.mcrcim.mcgill.edu