in reply to Re^2: How to simulate a preprocessor macro without one?
in thread How to simulate a preprocessor macro without one?

> In my case I need an access to the lexical scope of the callers environment to eval string type closures as they would exist inside the callers code.

PadWalker

> but I think I need more.

I think you need to rethink your questions... ;)

Cheers Rolf

  • Comment on Re^3: How to simulate a preprocessor macro without one?

Replies are listed 'Best First'.
Re^4: How to simulate a preprocessor macro without one?
by AriSoft (Sexton) on Feb 09, 2010 at 15:57 UTC

    Ok, here is my question rethinked: How could I overload the qq operator?

    With overloaded qq operator I could fully control the interpolation. For example, I could interpolate -> operators which are not available in the standard interpolation.

      How could I overload the qq operator?

      By using overload and overloading q for the constant string parts and the "."-operator for the string concatenations in between.

      Cheers Rolf

      UPDATE: If this whole thread is just about interpolating method-calls in strings/templates, you should consider the De/Ref-trick with @{[...]} :

      perl -e ' {package test; sub test {return "test"}}; $a=[]; bless $a, test; print "@{[$a->test]}" '

      please note: here $a->test is called in list context, for scalar context use ${\$a->test} !

      UPDATE2: After rereading overload I have the impression that overloading "" might be the approach to overload qq ... but this might also affect all other possible stringifications...(!?!)

        By using overload and overloading q for the constant string parts and the "."-operator for the string concatenations in between.

        That doesn't overload qq. It's already done its job by then

        Your example printed the return value of the test() but I didn't see any lexical changes to happen.

        The function I am now looking for, should be able to access the callers lexicals same way as qq operator does, to be able to create other new (better) ways to interpolate strings. Or, as in my original case, I would use callers local variables with the template string from the same caller. You should think the qq as a small template processor function to see the problem in my viewpoint.

        If my goal is possible achieve it also means that you can write new functions which gives allmost same effect as macro proprocessors functions does in C.