Ok, I have the fix.  I need to contemplate my navel though - It's minor, I
think it's perfectly harmless and simply an oversight, but I want to be sure
this close to 1.3.  Will check in tonight or tomorrow morning early.

Geir


On 2/27/02 2:53 PM, "Paulo Gaspar" <[EMAIL PROTECTED]> wrote:

> Thanks Geir,
> 
> Paulo
> 
>> -----Original Message-----
>> From: Geir Magnusson Jr. [mailto:[EMAIL PROTECTED]]
>> Sent: Wednesday, February 27, 2002 6:42 PM
>> To: Velocity Developer's List
>> Subject: Re: Recursion bug in local VelociMacros
>> 
>> 
>> On 2/27/02 9:46 AM, "Paulo Gaspar" <[EMAIL PROTECTED]> wrote:
>> 
>>> Please... just some guidance and I will try to fix it myself.
>> 
>> As soon as I have some...
>> 
>>> 
>>> Have fun,
>>> Paulo Gaspar
>>> 
>>>> -----Original Message-----
>>>> From: Paulo Gaspar [mailto:[EMAIL PROTECTED]]
>>>> Sent: Wednesday, February 27, 2002 2:51 AM
>>>> To: Velocity-Dev
>>>> Subject: Recursion bug in local VelociMacros
>>>> 
>>>> 
>>>> Hi,
>>>> 
>>>> 
>>>> I have a "tree builder" that uses VelociMacro recursion
>>>> just (the macro) as the sample at:
>>>>   \jakarta-velocity\examples\xmlapp_example
>>>> 
>>>> 
>>>> But this does not work correctly when I set
>>>>   velocimacro.permissions.allow.inline.local.scope
>>>> 
>>>> to true like in:
>>>>   m_runtimeInstance.setProperty(RuntimeInstance.VM_PERM_INLINE_LOCAL,
>>>> "true");
>>>> 
>>>> 
>>>> With 1.2 release it only displays the top 3 levels and
>>>> then the name of the macro (like "#showTree") for each
>>>> call for the 4th level... without calling it.
>>>> 
>>>> 
>>>> If I do not change the default value of the above
>>>> property everything is ok... but I really miss having
>>>> inline macros to be local in my stuff!
>>>> =:o/
>>>> 
>>>> 
>>>> I took a look at the source but I am still lost. Any
>>>> pointers someone? (Geir?)

-- 
Geir Magnusson Jr.                                     [EMAIL PROTECTED]
System and Software Consulting
Java : the speed of Smalltalk with the simple elegance of C++... 


--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Reply via email to