problem with <optimized>

[Konstantin Popov]

Hi Adreas,

> Hi Kostja,
>
> my Oz project (MBASE) takes advantage of
> the fact that the result of
>       OzPatternVS = {VirtualString.toValue DAG 1000 1000}
> can be used as input for compilation,
[ ]

> When I talked to Leif about this,
> he told me that this indeed had an
> influence on the design of the output
> routine that its result can be
> used as input for the compiler (for
> simple things, at least).
yeah, that's right.

> While this works fine in Mozart 1.1.0,
> it breaks in Mozart 1.2.0, and the
[ ]

> The only place in the sources where
> I could find the string '<optimized>'
> is in
>       platform/emulator/var_opt.hh
as far as I can see, this is the place (just checked it again).

[ ]
> Is this a bug or a feature? Do I
> have to write my own version of
> Value.toVirtualString? Is there
> already some Oz code available
> somewhere for this?
At the time I've written that code I thought it would be beneficial to
know the difference between optimized and non-optimized variables.
But I didn't benefit from that myself, so now I'd consider it to be a
bug. If nobody objects, please feel free to fix it.

>
> Thanks,
> Andreas
>
>
>

Cheers,

 --- Kostja.
-
Please send submissions to hackers at mozart-oz.org
and administriva mail to hackers-request at mozart-oz.org.
The Mozart Oz web site is at http://www.mozart-oz.org/.