Re: Build failures - compiling TeXmacs under guile 2.0.5

2012-05-30 Thread Jan Synacek
Hello! On 05/29/12 at 03:54pm, Ludovic Courtès wrote: > Hi! > > Jan Synacek skribis: > > > Hm, this is weird. So TeXmacs seems to bundle the same eval.scm as guile has > > (among others)? > > You mean TeXmacs ships a file called ice-9/eval.scm? If that is the > case, we’re in trouble. It doe

Re: Build failures - compiling TeXmacs under guile 2.0.5

2012-05-30 Thread Ludovic Courtès
Hi, Jan Synacek skribis: > Texmacs complains when started: > > Backtrace: > In unknown file: >?: 7 [boot-closure #t # ...] >?: 6 [catch-closure] >?: 5 [boot-closure #t # #] >?: 4 [catch-closure] >?: 3 [boot-closure #t # #] >?: 2 [catch-closure] >?: 1 [primitive-eval

%default-port-conversion-strategy and string ports

2012-05-30 Thread Ludovic Courtès
Hello! Commit b22e94db7c91d7661204e33f3bc2bfead002c9b7 adds ‘%default-port-conversion-strategy’, a natural friend of ‘%default-port-encoding’. First, I’m wondering whether ‘port’ should be part of the name, given that it’s also referred to by ‘scm_stringn’ & co. It’s good to have it in the name,

Re: %default-port-conversion-strategy and string ports

2012-05-30 Thread Mike Gran
>Second, in commit 9f6e3f5a997f484548bd03e7e7573c38a95c8d09, I changed >string ports to honor it, like other port types, instead of forcing >'error.  This seems like the right thing to me, for the sake of >consistency (in fact, I’d consider the previous behavior as a bug), but >it’s an observable c

Re: assembler in scheme

2012-05-30 Thread Noah Lavine
On Sat, May 26, 2012 at 10:58 PM, Nala Ginrut wrote: > Well, speaking this. I have a question that, is there any convenient > way to add multi-backend in Guile? It depends on what you mean by that. You can add as many low-level languages as you like, including a GCC interface, machine code, and

Re: %default-port-conversion-strategy and string ports

2012-05-30 Thread David Kastrup
l...@gnu.org (Ludovic Courtès) writes: > Hello! > > Commit b22e94db7c91d7661204e33f3bc2bfead002c9b7 adds > ‘%default-port-conversion-strategy’, a natural friend of > ‘%default-port-encoding’. > > First, I’m wondering whether ‘port’ should be part of the name, given > that it’s also referred to by