bugText Extractor TXR - Bugs: bug #35010, Code-walking logic in @(repeat)...

 
 

bug #35010: Code-walking logic in @(repeat) that looks for vars is inadequate now.

Submitter:  Kaz Kylheku <kkylheku>
Submitted:  Thu 08 Dec 2011 12:48:02 AM UTC
   
 
Category:  None Severity:  5 - Blocker
Item Group:  Correctness Status:  Fixed
Privacy:  Public Assigned to:  kkylheku
Originator Name:  Open/Closed:  Closed
Component Version:  None Operating System:  None
Fixed Release:  None Planned Release:  None
Architecture:  * All ABI:  * All
* Mandatory Fields

Add a New Comment Rich Markup
   

Thu 10 Oct 2013 05:27:04 AM UTC, comment #1: 

I had forgotten about this old bug entry.

Recently I ran into this problem, and I put a language hack in to address it.

I didn't make @(repeat) smart enough to look into Lisp code and find free variables. There would likely be downsides to that.

Rather, @(repeat) now takes a :vars argument, which tells it that there exist variables it might not "see" which need to be iterated over anyway.

This approach works well enough that the bug can be closed.

Release 68 has the feature.

Kaz Kylheku <kkylheku>
Group administrator
Thu 08 Dec 2011 12:48:02 AM UTC, original submission:  

Lisp forms can be evaluated in @(output), which breaks under @(repeat) and @(rep) because these directives walk the code looking for variables, and pass down bindings only for the variables that are found. But Lisp code can refer to pattern variables. The code walking does not see these references inside the Lisp code.

Kaz Kylheku <kkylheku>
Group administrator

 

(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 kkylheku (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.

     

    Follow 2 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2013-10-10 kkylheku StatusConfirmed Fixed
        Open/ClosedOpen Closed

    Back to the top

    Powered by Savane 3.13-4448.
    Corresponding source code