bugKawa - Bugs: bug #10613, closure with keyword generates bad...

 
 

bug #10613: closure with keyword generates bad .class file

Submitter:  Chris Dean <ctdean>
Submitted:  Fri 08 Oct 2004 09:04:51 AM UTC
   
 
Category:  Scheme language Severity:  3 - Normal
Item Group:  Unexpected result Status:  Fixed
Privacy:  Public Assigned to:  bothner
Open/Closed:  Closed
* Mandatory Fields

Add a New Comment Rich Markup
   

Thu 19 May 2005 04:52:34 PM UTC, comment #2: 

This was due to evaluating the default expression in the wrong scope.  (It also affects #!optional arguments.)

I check in a fix for this.  I also checked in a somewhat demanding testcase.

Per Bothner <bothner>
Group administrator
Fri 08 Oct 2004 09:24:31 AM UTC, comment #1: 

I should have mentioned, Kawa is confused when a closure var and keyword have the same name.  Or, as in the example, when the keyword refers to itself.

Chris Dean <ctdean>
Fri 08 Oct 2004 09:04:51 AM UTC, original submission:  

The code below generates a Foo$frame.class that throws a
Verifier error when loaded.



(module-name <Foo>)
(module-static #t)

(define (make-replacing-biffer component)
  (lambda (msg #!key (level level))
    (format #t "log-mode: ~A" component)
    level))

Chris Dean <ctdean>

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach Files:
   
   
Comment:
   

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

CC list is empty

 

There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

Only logged-in users can vote.

 

Follow 3 latest changes.

Date Changed by Updated Field Previous Value => Replaced by
2005-05-19 bothner StatusNone Fixed
    Assigned toNone bothner
    Open/ClosedOpen Closed

Back to the top

Powered by Savane 3.13-bb6a.
Corresponding source code