Re: Non-Printable Characters in Strings

=2D----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Wednesday 28 January 2004 12:51 am, Luke-Jr wrote:
> Is C-style escaping of common characters (\n, \r, \t, \v, \x##, etc) a go=
od
> idea? Including C-style's \### which uses octal or should \### use decimal
> (or hex?)?
Also, if number-based escaping is used, should it be octet-based or=20
character-based?
Character-based would translate the value to UTF-8 and could accept a=20
variable-length number up to a 16-bit value. For example, \xFFFF, \d65535,=
=20
\o200000, \xFF, \xF \x (for a null character). (Using variable-length numbe=
rs=20
would, of course, be discouraged since it could easilly create bugs if the=
=20
character following the escaped one was a valid digit).
=2D----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)

iD8DBQFAJdTnZl/BHdU+lYMRAhehAJ9ACWql1esncEupVjXjtCrU+rInbgCffIKu
8utozoE08zAegJuBJifYvJc=3D
=3D3JQ/
=2D----END PGP SIGNATURE-----


-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn