Because the variable was used in the Detail Header. At the point the
variable does not exist (Which is probably not the correct thing)
But I just wanted to make things crash less under the hood to start.
On Wed, 2005-07-20 at 11:29 -0600, William K. Volkman wrote:
> Well I was curious as to why it felt that it had to substitute
> zero for a valid expression. I will admit to not having
> read the code just yet.
>
> On Wed, 2005-07-20 at 09:11, Bob Doan wrote:
> > I could probably take that out. It was for debugging
> >
> >
> >
> > On Wed, 2005-07-20 at 05:43 -0600, William K. Volkman wrote:
> > > In array.xml there is this fragment:
> > > <Variables>
> > > <Variable name="bo" value="2+3" type="expression"/>
> > > </Variables>
> > > Which appears to be causing this message from pcode.c
> > > Variable Resolution: Assuming 0 value because rval is ERROR or NONE
> > > Due to the "amount" portion not being valid. I don't recall
> > > seeing this before, CVS update was done this evening, code was
> > > introduced:
> > >
> > > 2005-07-19 Bob Doan <bd...@si...>
> > > * configure.in: 1.3.5
> > > * libsrc/pcode.c: Tweek the compiler again / Make variables less
> > > picky and not crash on error
> > >
> > > Is this doing what you expected?
>
>
>
>
> -------------------------------------------------------
> SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
> from IBM. Find simple to follow Roadmaps, straightforward articles,
> informative Webcasts and more! Get everything you need to get up to
> speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
> _______________________________________________
> Rlib-devel mailing list
> Rli...@li...
> https://lists.sourceforge.net/lists/listinfo/rlib-devel
|
