Hi,
Maybe this is not clear indicated reasons of this trick (and re-inventing of eval).
Problem is indicated in subject of node. E.g. source filters in 'eval' code magically don't work.
So this is workaround of this problem and this post mean questions :
- Is this is correct workaround ?
- Can this be done more simply ?
- And if it can't, how we can make this work magically ?
E.g. if we can override (re-define) CORE::eval
Isn't that because you used the expression (quoted) form of eval? The code would have already been compiled and (I think) source filters are applied at compile time. What happens if you try a block style eval?
You right, but I can't use block style eval. I need to eval code located in other file and content of this file should be preprocessed first in some way... As trivial example I need to load this code in temporary package and import some function (from other module) into this package: