#MicroEMACS 3.10 & 5.0d
4 messages in this thread
The version of Daniel Lawrence's MicroEMACS 3.10 which used to compile and
run correctly under Manx 5.0a & 5.0b is failing under the new Manx 5.0d. It
compiles (-so option) and links ok with no errors, but when attempting to
run it, the window only seems to output characters up to column 56.
Everything else past that, including the mode/status line is truncated. Any
ideas what may have changed in 5.0d that would cause this? I tried
simulating 5.0b behaviour by compiling with the -r6 option to no avail.
John
None whatsoever. We did fix a number of compiler bugs – the only thing I
can think of is that the u-EMACS code depended on particular code
generation which obscured a bug in the code. If you can isolate the
problem to a short example I'd be glad to take a look at it, but there's
enough (er, not enough) to go on from what you've told me.
-Mike
Mike,
You did it! MicroEMACS 3.10 now compiles and runs correctly with the
latest fix. Than you very much. It is support like this that makes me
happy that I purchased Manx. It's not only the fact that you found the
problem and fixed it quickly that impresses me (I know how the problem got
fixed, I read the Manx BBS), but that you were willing to look at the
problem with the scant information I had available even though your gut
reaction may have been that it was an application problem and not a
compiler problem. Once again, thanks very much and keep up the good work!
Now a couple of questions:
Will the Manx library source for the changed modules be given out to
those who have purchased library source?
When I specify the -so option, is -ss automatically turned off?
John
Glad to hear we fixed it. 😎
Library source for 5.0d is now available – you should probably call our
update dept. at (201)542-2121 and ask for it, I believe it's free of charge
if you have the lib source from a previous 5.0 version.
For now, we've just completely stubbed out the string-squisher code –
there's a fairly serious design flaw in it, and we didn't want to muck with
it in a maintenance release like 5.0d. Neither -so or -ss will turn it on.
-Mike