answer the result

[Dave Cragg]

On 10 Apr 2006, at 15:43, Trevor DeVore wrote:
>
> I've noticed this behavior in recent versions as well (OS X/ 
> Windows).  I've resorted to using
>
> get the result
> answer it
>
> Though that isn't how things used to work.

Thanks for the confirmation. I've submitted it as a bug (3513). I  
suspect it will hit a lot of older stacks that get updated to a newer  
engine. That's how I found it.

Not sure what to do about the libUrl documentation now. :-(

Cheers
Dave