Non-Printable Characters in Strings

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

How should non-printable characters be represented in strings?
Is C-style escaping of common characters (\n, \r, \t, \v, \x##, etc) a good=
=20
idea? Including C-style's \### which uses octal or should \### use decimal=
=20
(or hex?)?
Should the following string be permitted (it is currently not)? "this is a \
multiline string" or require the programmer to use \n?
Would it be a good or bad idea to parse \^A through \^Z into character 0x01=
 to=20
0x1A? What about parsing \e to 0x1B and \s1 to \s4 and \sf \sg \sr \su=20
(seperator characters) to 0x1C to 0x1F?
Anything else?

Comments please.
=2D----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)

iD8DBQFAFweNZl/BHdU+lYMRAt1XAKCWyf/N5U/tro37qvmRgXJPTjFgGQCgmK9y
=46cTTf+zmtu8A4iOs1CmOX/o=3D
=3DcxE5
=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