Re: Elisp Reader

2009-08-27 Thread Ken Raeburn
On Aug 27, 2009, at 13:00, Daniel Kraft wrote: yesterday and today I implemented the promised elisp reader and just pushed the changes. Now Guile's elisp support in my branch should be somewhat "complete" because not only there's a compiler but also a genuine parser for elisp, handling for

Re: build failure after "eval is actually compile"

2009-08-27 Thread Ken Raeburn
On Aug 27, 2009, at 18:32, Ken Raeburn wrote: I wonder, though, what is loading up srfi-1 for you? I wish I could tell, but as I mentioned in IRC, backtraces aren't working for me. I suppose I can try instrumenting everything listing srfi-1 in use-modules, to print out a message first...

Re: Unicode-capable srfi-14 charsets (f49dbcadf...)

2009-08-27 Thread Ludovic Courtès
Hi, I haven't looked in details, but here's a minor glitch (when making `srfi-14.doc'): --8<---cut here---start->8--- gawk -f ./guile-func-name-check srfi-14.c srfi-14.c:707:***Missing or erroneous #undef for scm_char_set_cursor: srfi-14.c:737:***Missing or er

Re: build failure after "eval is actually compile"

2009-08-27 Thread Mike Gran
> From: Ken Raeburn > On Aug 27, 2009, at 17:15, Andy Wingo wrote: > > I have reverted that part of the "eval is actually compile" commit that > > seems to have caused you problems. > > Thanks; that puts it back to the "print a warning and go on" case, which lets > me > get other work done. >

Re: build failure after "eval is actually compile"

2009-08-27 Thread Ken Raeburn
On Aug 27, 2009, at 17:15, Andy Wingo wrote: I have reverted that part of the "eval is actually compile" commit that seems to have caused you problems. Thanks; that puts it back to the "print a warning and go on" case, which lets me get other work done. I wonder, though, what is loading

guile-devel@gnu.org

2009-08-27 Thread Andy Wingo
Hey Daniel, Awesome work on the reader! And awesome work in general. I met Neil and Ludovic last weekend, and we're all super-plussed about your work. I want to get Mark's nil patch merged in, then start merging your work to master. We need to get it there before Ken can update, I think. More up

Re: Unicode-capable srfi-14 charsets (f49dbcadf...)

2009-08-27 Thread Andy Wingo
The failing test: FAIL: r6rs-ports.test: 7.2.7 Input Ports: make-custom-binary-input-port -- http://wingolog.org/

Re: Unicode-capable srfi-14 charsets (f49dbcadf...)

2009-08-27 Thread Andy Wingo
On Thu 27 Aug 2009 17:20, Mike Gran writes: > I pushed the commit for Unicode-capable srfi-14. Of all parts necessary > for Unicode, this patch has the largest amount of new code and is most > likely to cause compilation problems. On Linux, this now works fine for me; make succeeds, one test fa

Re: build failure after "eval is actually compile"

2009-08-27 Thread Andy Wingo
On Thu 27 Aug 2009 00:48, Ken Raeburn writes: > Building on GNU/Linux, with a fresh build tree, and without an installed > tree under $prefix, fails for me. I get: > > ./guile_filter_doc_snarfage --filter-snarfage) > regex-posix.doc || { rm > regex-posix.doc; false; } > cat alist.doc [...] regex

Re: deadlock in current git version on error during initialization

2009-08-27 Thread Andy Wingo
Hi Ken, On Thu 27 Aug 2009 00:51, Ken Raeburn writes: > After the build-order problem I just reported causes a module to fail to > load, the build process hangs here: I sometimes get these when I'm hacking the boot process. It's probably a bug, but it never happens -- unless, as in your case, w

Elisp Reader

2009-08-27 Thread Daniel Kraft
Hi all, yesterday and today I implemented the promised elisp reader and just pushed the changes. Now Guile's elisp support in my branch should be somewhat "complete" because not only there's a compiler but also a genuine parser for elisp, handling for instance the [] vectors, all those fancy

Unicode-capable srfi-14 charsets (f49dbcadf...)

2009-08-27 Thread Mike Gran
Hi- I pushed the commit for Unicode-capable srfi-14. Of all parts necessary for Unicode, this patch has the largest amount of new code and is most likely to cause compilation problems. Since the default charsets such as char-set:lower-case are much larger in the Unicode scenario, I had to change