Re: `SCM_MAKE_CHAR ()' signedness issue

2009-08-17 Thread Ludovic Courtès
Hi, Ken Raeburn writes: > On Aug 16, 2009, at 18:13, Ludovic Courtès wrote: >>> There's always the inline-function approach, too. >> >> Unfortunately no, because we're still not assuming `inline' keyword >> support from the compiler. > > Right, but inline.h deals with that; if "inline" isn't sup

Error with CYGWIN and latest GIT rep.

2009-08-17 Thread carlo.bramix
Hello, I'm getting these errors when compiling the very latest repository of guile with cygwin. I temporary patched the sources just for collecting all error messages until it compiled guile.exe Sincerely, Carlo Bramini. libtool: compile: gcc -DHAVE_CONFIG_H -DBUILDING_LIBGUILE=1 -I../../gu

Re: Error with CYGWIN and latest GIT rep.

2009-08-17 Thread Ludovic Courtès
Hi, "carlo.bramix" writes: > I'm getting these errors when compiling the very latest repository of guile > with cygwin. > I temporary patched the sources just for collecting all error messages until > it compiled guile.exe It's a known issue, see http://thread.gmane.org/gmane.lisp.guile.devel

Re: Some more elisp aspects: Reader and documentation

2009-08-17 Thread Ludovic Courtès
Hi Daniel, Sorry for the late reply. Daniel Kraft writes: > 2) Write a seperate elisp reader, possibly in Scheme (but could be C > as well if that's important for performance). This helps us keep > "both" readers clean and seperate, but all has to be done from ground > up and the code is proba

Re: Some more elisp aspects: Reader and documentation

2009-08-17 Thread Daniel Kraft
Hi Ludo, Ludovic Courtès wrote: Sorry for the late reply. no problem, thanks for the reply! I had a lot of other stuff to do anyways, and so didn't really get into the situation of waiting for a reply here ;) 2) Write a seperate elisp reader, possibly in Scheme (but could be C as well if

Re: Some more elisp aspects: Reader and documentation

2009-08-17 Thread Ludovic Courtès
Daniel Kraft writes: >>> 2) Write a seperate elisp reader, possibly in Scheme (but could be C >>> as well if that's important for performance). This helps us keep >>> "both" readers clean and seperate, but all has to be done from ground >>> up and the code is probably slower (when written in Sch

Re: Some more elisp aspects: Reader and documentation

2009-08-17 Thread Daniel Kraft
Hi Ludo, 2) Write a seperate elisp reader, possibly in Scheme (but could be C as well if that's important for performance). This helps us keep "both" readers clean and seperate, but all has to be done from ground up and the code is probably slower (when written in Scheme). This sounds like the

Re: `SCM_MAKE_CHAR ()' signedness issue

2009-08-17 Thread Mike Gran
Hi- On Mon, 2009-08-17 at 10:26 +0200, Ludovic Courtès wrote: > Hi, > > Ken Raeburn writes: > > > On Aug 16, 2009, at 18:13, Ludovic Courtès wrote: > >>> There's always the inline-function approach, too. > >> > >> Unfortunately no, because we're still not assuming `inline' keyword > >> support

Re: `SCM_MAKE_CHAR ()' signedness issue

2009-08-17 Thread Ludovic Courtès
Mike Gran writes: > On my system I ran a test with SCM_MAKE_CHAR as a macro, an an inline, > and as a never inlined function. I ran ./check-guile twice for each. You're cheating! ;-) The test suite does lots of things besides calling `SCM_MAKE_CHAR ()', so I'm not sure if it's a good benchmar

Re: GNU Guile 1.9.2 released (alpha)

2009-08-17 Thread Linas Vepstas
2009/8/15 Ludovic Courtès : >  ** Incomplete support for Unicode characters and strings > >  Internally, strings are now represented either in the `latin-1' >  encoding, one byte per character, or in UTF-32, with four bytes per >  character. Will this eventually move to UTF8? European languages t

Re: `SCM_MAKE_CHAR ()' signedness issue

2009-08-17 Thread carlo.bramix
Hello, if I understood the problem, I think it can be easily fixed without using an inline function. For example: #ifdef __GNUC__ #define SCM_MAKE_CHAR(__x)\ ({ scm_t_int32 __t = (scm_t_int32)(__x); \ (__t < 0)

Re: GNU Guile 1.9.2 released (alpha)

2009-08-17 Thread Mike Gran
> From: Linas Vepstas > > 2009/8/15 Ludovic Courtès : > > >  ** Incomplete support for Unicode characters and strings > > > >  Internally, strings are now represented either in the `latin-1' > >  encoding, one byte per character, or in UTF-32, with four bytes per > >  character. > > Will this e

Re: `SCM_MAKE_CHAR ()' signedness issue

2009-08-17 Thread Ken Raeburn
On Aug 17, 2009, at 14:52, carlo.bramix wrote: Hello, if I understood the problem, I think it can be easily fixed without using an inline function. For example: #ifdef __GNUC__ Relying on GCC-specific syntax is probably worse than an inline function. Part of Ludovic's complaint was that

[PATCH] Compile in a fresh module by default

2009-08-17 Thread Ludovic Courtès
Hello Guilers! The attached patch makes `compile' and friends use fresh module rather than the current module as the default compile-time environment. The intent is to make sure macro definitions and side-effects made at expansion time do not (to some extents) clutter the current module's name sp

[PATCH] Honor and confine expansion-time side-effects to `current-reader'

2009-08-17 Thread Ludovic Courtès
Hi! The attached patch allows expansion-time modifications of `current-reader' to be taken into account. For example: (define-macro (install-reader!) (fluid-set! current-reader (let ((first? #t)) (lambda args (if first?