Comment 4 for bug 173908
Revision history for this message
| Derick Eddington (derick-eddington) wrote | #4 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
67d34a1
(Get the code!)
I'm guessing this is happening because the expander/library stuff isn't seeing the included bindings before it checks if the exported bindings exist, or there's some mismatch with the syntax-object contextual info, or probably there's some deeper reason which is beyond me why it is correct; but if it could be fixed/done, it seems very useful to be able to have macros which can expand to include.