[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

odd behaviour writeq and write_to_codes

From: Jasper Taylor
Subject: odd behaviour writeq and write_to_codes
Date: Mon, 30 Jun 2003 17:36:40 +0100
User-agent: KMail/1.4.3

Hello folks -- not sure if this counts as a bug...if I have an atom
that contains a wide character, say é (that should be e acute), 
then if I write that atom it
comes out correctly, but if I writeq it it is replaced by a special
format such as '\xc3\\xa9\'. The manual does not describe this
behaviour. Example:

?- name(P, [195,169]), write(P).

P = '\xc3\\xa9\'


(note that the é is produced by write(P), but the answer to the query
is displayed using an internal call to writeq).

Another issue: If I call write_to_codes as part of a portray
procedure, it can occasionally cause a get_print_stream request later
on in portray to return the wrong stream id, though I can't yet
reproduce this problem reliably.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]