Re: status update

[Sam S. <sd...@gn...>]

Hi,

> * Daniel Jour <qnavry.bregjvt@tznvy.pbz> [2016-08-08 02:30:01 +0200]:
>
> *) Is WIDE_AUXI still in use / of interest? It was introduced
>  2002-12-04 by Bruno, but as far as I can tell won't get used unless
>  explicitly requested during configure via setting -D WIDE_AUXI in
>  CFLAGS.

I have no idea why Bruno introduced it (we already have WIDE_SOFT).
Unless he explains, I think we can discard it.

> *) Bug report numbers. At various places in the code there are bug
>  report numbers (like 710737, lispbibl.d, "Global register
>  declarations"). I guess these numbers are from an abandoned bug
>  tracker? Is there a backup of these bug reports somewhere? (I'm
>  mostly just curious, there's no real need for these reports atm.)

These numbers refer to the old SF bug tracker.
See emacs/misc.el:clisp-bug-reference-url-format for a hint on how to
convert those numbers to the new ones.

> *) intparam.h, floatparam.h: Instead of creating these headers during
> the build, I just wrote them using standard (C99) features (for
> example FLT_MANT_DIG from float.h).

Whatever you find easy to maintain.

> This makes cross-building much easier (did it even work before?).

I am sure it did :-)

> One thing that surprised me was that intparam.h contains endianness
> defines for each of short, int, long and long long. Since all these
> defines get "merged" into a single BIG_ENDIAN_P define, I guess
> systems with different endianness for different sized integer types
> are no longer supported? (Did we actually support such systems, like
> the PDP-11, at some point?)

You would be surprised by the zoo of systems once supported by CLISP.

> *) Not GSoC related: If I understood this correctly, the math code
>  backing CLISPs number system has at some point been extracted as a
>  library, CLN (http://www.ginac.de/CLN/). Would it make sense to
>  "throw out" our math code and to use that library instead? Looking at
>  its code it has probably seen massive rewrites: It's now written in
>  C++. It seems to be actively maintained and suitable for an ANSI CL
>  number system.

It might.

Note that all these issues should be postponed until AFTER you make the
release.
The ONLY focus of the release is making it work on all 3 major platforms
OOTB.



-- 
Sam Steingold (http://sds.podval.org/) on Ubuntu 16.04 (xenial) X 11.0.11803000
http://www.childpsy.net/ http://camera.org http://memri.org
http://openvotingconsortium.org http://thereligionofpeace.com
Sufficiently advanced stupidity is indistinguishable from malice.