bugKawa - Bugs: bug #36727, Inconsistency between quasisyntax...

 
 

bug #36727: Inconsistency between quasisyntax and #`

Submitter:  Jamison Hope <jhope>
Submitted:  Mon 25 Jun 2012 04:15:45 PM UTC
   
 
Category:  Scheme language Severity:  3 - Normal
Item Group:  None Status:  None
Privacy:  Public Assigned to:  None
Open/Closed:  Open
* Mandatory Fields

Add a New Comment Rich Markup
   

Mon 25 Jun 2012 04:15:45 PM UTC, original submission:  

A while back, using unquote inside quasisyntax became deprecated:


#|kawa:1|# (quasisyntax ,(cons 1 2))
/dev/stdin:1:15: warning - unquote inside quasisyntax is deprecated - use unsyntax or #,
(1 . 2)


Following the warning's advice, however, leads to an error:


#|kawa:2|# (quasisyntax #,(cons 1 2))
/dev/stdin:2:26: unknown reader constructor cons


Using literal unsyntax instead of #, works, though:


#|kawa:3|# (quasisyntax (unsyntax (cons 1 2)))
(1 . 2)


As does using both #` and #,:


#|kawa:4|# #`#,(cons 1 2)
(1 . 2)


The problem appears to be that ReaderDispatchSyntaxQuote#read sets reader.inQuasiSyntax = true when it sees #`, but nothing sets that flag for literal quasisyntax. So in the latter case, when it gets to #, it erroneously calls ReaderDispatchSyntaxQuote#readNamedConstructor.

Jamison Hope <jhope>
Group Member

 

(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

 

Carbon-Copy List
  • -email is unavailable- added by jhope (Submitted the item)
  •  

    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.

     

    No changes have been made to this item

    Back to the top

    Powered by Savane 3.13-f8d8.
    Corresponding source code