Re: [xHarbour-developers] Questions about ASIZE + AEVAL

2009-02-03 Thread Vicente Guerra
Ron, Thank you. I hadn't pay attention to that code on AEVAL. Atte. Vic On Tue, 3 Feb 2009, Ron Pinkas wrote: >> But, what about the second part? Looks like the following code could >> leave unreleased memory: >> >> x := {} >> AEVAL( x, { || NIL } ) >> AADD( x, DATE(

Re: [xHarbour-developers] Questions about ASIZE + AEVAL

2009-02-03 Thread Ron Pinkas
> But, what about the second part? Looks like the following code could > leave unreleased memory: > > x := {} > AEVAL( x, { || NIL } ) > AADD( x, DATE() )// Dynamically created string... > AADD( x, TIME() )// Dynamically created string... > AEVAL( x, { |x,i|

Re: [xHarbour-developers] Questions about ASIZE + AEVAL

2009-02-03 Thread Vicente Guerra
On Tue, 3 Feb 2009, Ron Pinkas wrote: > Yes, you can move it, it appears to be a valid correction, if user code calls > aEval() with invalid arguments (my mistake). Thank you. I'll move. But, what about the second part? Looks like the following code could leave unreleased memory:

[xHarbour-developers] Questions about ASIZE + AEVAL

2009-02-02 Thread Vicente Guerra
Hi! Ron, in the file source/vm/arrays.c , function hb_arrayEval() , about line 1369, it says "pBaseArray->uiFlags |= 0xF000;" . Can I move it? ulLen = pBaseArray->ulLen; pBaseArray->uiFlags |= 0xF000; / From here... if( pulStart && ( *pulStart