emacs-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[debbugs-tracker] bug#18004: closed (export does not check that its argu


From: GNU bug Tracking System
Subject: [debbugs-tracker] bug#18004: closed (export does not check that its arguments are symbols or pairs of symbols)
Date: Sun, 13 Jul 2014 13:39:02 +0000

Your message dated Sun, 13 Jul 2014 09:37:16 -0400
with message-id <address@hidden>
and subject line Re: bug#18004: export does not check that its arguments are 
symbols or pairs of symbols
has caused the debbugs.gnu.org bug report #18004,
regarding export does not check that its arguments are symbols or pairs of 
symbols
to be marked as done.

(If you believe you have received this mail in error, please contact
address@hidden)


-- 
18004: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=18004
GNU Bug Tracking System
Contact address@hidden with problems
--- Begin Message --- Subject: export does not check that its arguments are symbols or pairs of symbols Date: Sat, 12 Jul 2014 16:59:01 +0200
Guile happily compiles the following module:

(define-module (test))
(define (foo) #t)
(export (foo))

This exports foo as (), because (foo) = (foo . ()) and export treats pairs as renaming.

If you use this module, readline breaks because it looks up the module's exported symbols and then tries to call (symbol->string '()):

scheme@(guile-user)> (use-modules (test))
scheme@(guile-user)> x<TAB>
While reading _expression_:
ERROR: In procedure symbol->string: Wrong type argument in position 1 (expecting symbol): ()


--- End Message ---
--- Begin Message --- Subject: Re: bug#18004: export does not check that its arguments are symbols or pairs of symbols Date: Sun, 13 Jul 2014 09:37:16 -0400 User-agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux)
Hi,

Tobias Brandt <address@hidden> writes:
> Guile happily compiles the following module:
>
> (define-module (test))
> (define (foo) #t)
> (export (foo))
>
> This exports foo as (), because (foo) = (foo . ()) and export treats
> pairs as renaming.

This is already fixed in the latest release (2.0.11), commit
df3acd296e7149630fd6030aced6331ae6dd424b.

I'm closing this bug, but feel free to reopen if there's still a
problem.

      Thanks!
        Mark


--- End Message ---

reply via email to

[Prev in Thread] Current Thread [Next in Thread]