bug#10567: Fw: guile-library - make bug report

bug#10567: Fw: guile-library - make bug report

[David Pirotte]

I sent the following bug report to guile-devel by mistake, sorry

;; --

Hello,

	guile 	2.0.3.150-88c0
	guile-lib	release-0.2.1-2-ge9fe22b

...
make[1]: Entering directory `/usr/local/src/guile-lib/git-clone/src'
../dev-environ /usr/local/bin/guile-tools compile -o "text/parse-lalr.go"
"text/parse-lalr.scm" ice-9/boot-9.scm:106:20: In procedure #<procedure 9a66680 at
ice-9/boot-9.scm:97:6 (thrown-k . args)>: ice-9/boot-9.scm:106:20: In procedure
scm_read_expression: text/parse-lalr.scm:1418:45: unexpected ")" make[1]: ***
[text/parse-lalr.go] Error 1 make[1]: Leaving directory
`/usr/local/src/guile-lib/git-clone/src' make: *** [all-recursive] Error 1


David

bug#10567: Fw: guile-library - make bug report

[Andy Wingo]

On Fri 20 Jan 2012 19:25, David Pirotte <david@altosw.be> writes:

> 	guile 	2.0.3.150-88c0
> 	guile-lib	release-0.2.1-2-ge9fe22b
>
> ...
> make[1]: Entering directory `/usr/local/src/guile-lib/git-clone/src'
> ../dev-environ /usr/local/bin/guile-tools compile -o "text/parse-lalr.go"
> "text/parse-lalr.scm" ice-9/boot-9.scm:106:20: In procedure #<procedure 9a66680 at
> ice-9/boot-9.scm:97:6 (thrown-k . args)>: ice-9/boot-9.scm:106:20: In procedure
> scm_read_expression: text/parse-lalr.scm:1418:45: unexpected ")" make[1]: ***
> [text/parse-lalr.go] Error 1 make[1]: Leaving directory
> `/usr/local/src/guile-lib/git-clone/src' make: *** [all-recursive] Error 1

The line in question:

			 (eq? (car rest) ':)

It seems you have (read-set! keywords 'prefix) in your init.scm, which
affects the compile-time environment.

I wonder what is the right thing to do here.

A
-- 
http://wingolog.org/

bug#10567: Fw: guile-library - make bug report

[David Pirotte]

Hi Andy,

> The line in question:
> 
> 			 (eq? (car rest) ':)
> 
> It seems you have (read-set! keywords 'prefix) in your init.scm, which
> affects the compile-time environment.

Yes I do, sorry i din't think of that but i confirm it is the case.

...

Cheers,
David

Aside, I always did actually [read-set! ...], and questioned myself, as an 'old
lisper', why scheme does requirer, per defaut, that we enter 2 chars instead of
one, what ever i would be, to tell guile/scheme it's dealing with a keyword ?

bug#10567: Fw: guile-library - make bug report

[Andy Wingo]

On Fri 03 Feb 2012 16:41, Andy Wingo <wingo@pobox.com> writes:

> On Fri 20 Jan 2012 19:25, David Pirotte <david@altosw.be> writes:
>
>> 	guile 	2.0.3.150-88c0
>> 	guile-lib	release-0.2.1-2-ge9fe22b
>>
>> ...
>> make[1]: Entering directory `/usr/local/src/guile-lib/git-clone/src'
>> ../dev-environ /usr/local/bin/guile-tools compile -o "text/parse-lalr.go"
>> "text/parse-lalr.scm" ice-9/boot-9.scm:106:20: In procedure #<procedure 9a66680 at
>> ice-9/boot-9.scm:97:6 (thrown-k . args)>: ice-9/boot-9.scm:106:20: In procedure
>> scm_read_expression: text/parse-lalr.scm:1418:45: unexpected ")" make[1]: ***
>> [text/parse-lalr.go] Error 1 make[1]: Leaving directory
>> `/usr/local/src/guile-lib/git-clone/src' make: *** [all-recursive] Error 1
>
> The line in question:
>
> 			 (eq? (car rest) ':)
>
> It seems you have (read-set! keywords 'prefix) in your init.scm, which
> affects the compile-time environment.
>
> I wonder what is the right thing to do here.

In this case, probably just to change it to (string->symbol ":").  I
have done that.  We don't need to change the copy in Guile because its
compilation environment is more controlled.

Andy
-- 
http://wingolog.org/