In my prior speedups, I replace c.allNodes_iter with something like
c.all_nodes_with_unique_tnodes and I believe I have not changed the
results generated. I see two more opportunities, but this *would*
change the Leo semantics. c.allNodes_iter is used to look for both
@settings and for @button nodes.
If I were to make this change, it would affect situations where you
had
@settings
@bool foo False # tx="sps.20080202000824"
@bool foo True # tx="sps.20080202000825"
@bool foo False # tx="sps.20080202000824"
E.g., the first and third foo are clone; we currently get a foo value
of False; the change would generate a foo value of True. Similarly:
@button do nothing # tx="sps.20080202000826"
@button do nothing # tx="sps.20080202000826"
E.g., a button has a clone, and generates two buttons. Under the
change only one button would get generated.
I very much doubt the above scenarios currently occur on purpose.
Would the proposed change to the semantics be acceptable?
- Stephen
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"leo-editor" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/leo-editor?hl=en
-~----------~----~----~----~------~----~------~--~---
