On Tue, Feb 18, 2020 at 07:50:05AM +0100, [email protected] wrote:
>
> On Tue 18 Feb 2020 at 02:34, Aaron Sloman <[email protected]>
> wrote:
>
> > Andreas wrote:
> >
> > > I don't know enough about poplog to add jmuch of value here,
> > > but
> > > maybe you have a different readline in your image? Probably
> > > there is
> > > emacsreadline linked in?
> > > Just a wild guess.
<snip>
> I was talking about the emacsreadline in
> 'pop/lib/lib/emacsreadline.p'.
> It is linked into the image in e.g. 'pop/com/mkstartup.bham'.
> I was just suggesting this might be the source of differernt
> behaviour.
That is probably correct explanation. Using V16 I get:
./poplog pop11 :"lib emacsreadline; readline() => 1 + 1 =>"
;;; LOADING LIB emacsreadline
? Hello
** [Hello]
** 2
so loading 'emacsreadline' gives behaviour from V15. In V15
'mkstartup' loads a lot of things, including 'readline'.
In V16 'mkstartup' is much smaller. Smaller 'mkstartup' is
needed to allow build without X. AFAICS if more things
should go into startup image, then they should be added
to 'pop/lib/lib/startup.p'. This requires a bit of work,
as things depending on X should go into proper conditional.
BTW: 64-bit V15 had a bug in memory management and putting
stuff in 'mkstartup' probably was a workaround. But no
such workaround should be needed in V16.
--
Waldek Hebisch
