[m-dev.] Re: io__write_bytes vs Unicode

[Fergus Henderson]

On 21-Oct-2002, Simon Taylor <stayl at cs.mu.OZ.AU> wrote:
> On 21-Oct-2002, Fergus Henderson <fjh at cs.mu.OZ.AU> wrote:
> > On 19-Oct-2002, Fergus Henderson <fjh at cs.mu.oz.au> wrote:
> > > Zoltan, what is the intended semantics of io__write_bytes?
> > ...
> > > Currently the only use of io__write_bytes in the system is in
> > > compiler/bytecode.m.
> > 
> > I talked in person with Zoltan, and he said that he'd be happy
> > to just get rid of io__write_bytes.
> > 
> > But I just realized that this is used for Aditi bytecode, as well as
> > for Mercury bytecode.  So I can't just remove io__write_bytes without
> > breaking the Aditi back-end.
> > 
> > Simon, any comments on this issue?
> 
> The Aditi back-end doesn't use bytecode_data__output_string,
> which is the only caller of io__write_bytes.

Ah.  True.

The Aditi back-end is still going to be broken if the compiler is built in
.NET or Java grades, because it calls bytecode_data__string_to_byte_list.
But I guess that is not such a big deal, and anyway it doesn't prevent
removing or deprecating io__write_bytes.

-- 
Fergus Henderson <fjh at cs.mu.oz.au>  |  "I have always known that the pursuit
The University of Melbourne         |  of excellence is a lethal habit"
WWW: <http://www.cs.mu.oz.au/~fjh>  |     -- the last words of T. S. Garp.
--------------------------------------------------------------------------
mercury-developers mailing list
Post messages to:       mercury-developers at cs.mu.oz.au
Administrative Queries: owner-mercury-developers at cs.mu.oz.au
Subscriptions:          mercury-developers-request at cs.mu.oz.au
--------------------------------------------------------------------------