Re: [MOO-Discuss] Non-Printable Characters in Strings

[Luke-Jr <lu...@ar...>]

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

Attached is a patch for a vanilla LambdaMOO server to add support for C-sty=
le=20
escape codes, \### (octal), \^@ through \^_ (see ASCII chart for details on=
=20
range), \e, \s1 to \s4, \sf, \sg, \sr, and \su. Octet-based, but VBR length=
=20
numbers for \x##, \o###, and \d### are supported.
This patch does not address \<newline>, and such a sequence will continue t=
o=20
error. It has the potential for memory leaking since character 0x00 can be=
=20
used and the LambdaMOO server cannot properly handle it in strings (yet).
\### can easilly be changed to use decimal, but unless there are any=20
objections, I think octal is more logical. Note that hex is not an option,=
=20
since it would conflict with things such as \a or \b, which are C-style=20
escape codes.
As before, comments are more than welcome. :)

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?)?
> 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 0x=
01
> to 0x1A? What about parsing \e to 0x1B and \s1 to \s4 and \sf \sg \sr \su
> (seperator characters) to 0x1C to 0x1F?
=2D----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)

iD8DBQFAKEQsZl/BHdU+lYMRAuVRAJ4yHURT+Dz5HCwffbuc5jUS4vay6wCdHXLr
Y7dP1hFXts9RBbYJwaTDWYY=3D
=3DyNH5
=2D----END PGP SIGNATURE-----