gcl-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Gcl-devel] Re: Register as developer please.


From: Mike Thomas
Subject: Re: [Gcl-devel] Re: Register as developer please.
Date: Fri, 22 Mar 2002 05:05:52 +1000

> ---
> >     #+winnt
> >     (dotimes (i 12)
> >       (write-char #\^@ o-file))
>
> OK, I haven't yet read your other mail, but this looks a bit strange.
> Go ahead and put it in, as long as its escaped with the #winnt if you
> really need it, but "isn't there a better way?"  What are we trying to
> achieve here?

This is the 12 ascii nul issue I mentioned.  If you go to the original
source (cmpmain.lsp), you'll find similar alternatives for other platforms
in the same place.  In an earlier message I mentioned that I would look
further into this to see whether it really is necessary.

GCL ".o"s are concatenated with these nul's and the ".data" files with a
script, rather than via the compiler, which is where the original problem
came in.


> RCS file: /cvsroot/gcl/gcl/h/mingw.h,v
> Whatever you'd like to do with this file is OK by me :-)!

Yes, my intention is to clean it up eventually.

> OK, this bit looks like Dan Stanger's idea of making DBEGIN a dynamic
> runtime variable.  If it works, great!  I'm very surprised, though, as
> my (weak) understanding is that DBEGIN needs to be the same in the
> raw_gcl run as in the saved_gcl final, as it is used to index the
> types for the pages in memory.  If it moves, the whole GC should be
> compromised.  Of course I could be wrong.

You're more likely to be right than I am - I had no idea what it was for.

> Again, go ahead and use it if you need it as long as its win only for
> the time being.

As it will be.

> 209c216
> <      ADD_FEATURE("I386"); ADD_FEATURE("WINNT")
> ---
> >          ADD_FEATURE("I386"); ADD_FEATURE("WINNT");
ADD_FEATURE("BROKEN_O4_OPT");
>
> This is fine.  I looked into these a bit a while ago.  do they do
> anything?

I haven't chased the I386 one, but WINNT and BROKEN_O4_OPT most certainly
do.

> OK, see above.  Eventually it would be nice to have a generic way of
> dealing with DBEGIN, but with the ifdef you have, use it if it works!

My sentiments entirely.  The breakage with PCL-GCL may be an indication of
further trouble ahead, but as few people are going to use GCL for anything
except Maxima and as that works OK, I am not too worried.

> 126a147,149
> > #ifdef WIN32
> > _fmode = _O_BINARY;
> > #endif
>
> OK

Yes, this was another Rainer one, which I forgot to mention.  I think it is
sensible.

> In general, with all the win specific files, I'd really appreciate if
> you and dan and others with access could take free reign.   changes to
> main.c et.al. we should probably discuss.  What do you think?

Sensible to me.

Mike Thomas




reply via email to

[Prev in Thread] Current Thread [Next in Thread]