diff options
author | Guy Harris <guy@alum.mit.edu> | 2009-06-15 16:54:07 +0000 |
---|---|---|
committer | Guy Harris <guy@alum.mit.edu> | 2009-06-15 16:54:07 +0000 |
commit | ec5dbeca716fdf01465a59b4994c66fe5a8e72cf (patch) | |
tree | fb3d617876a8f9a416a2074dfcff977d0b22014e | |
parent | a61e285004e96f330774870a417008f2597a4151 (diff) |
Note that non-ASCII characters in source files cause problems.
svn path=/trunk/; revision=28742
-rw-r--r-- | doc/README.developer | 11 |
1 files changed, 11 insertions, 0 deletions
diff --git a/doc/README.developer b/doc/README.developer index 11f513c2a9..357d64fc5d 100644 --- a/doc/README.developer +++ b/doc/README.developer @@ -497,6 +497,17 @@ automatically free()d when the dissection of the current packet ends so you don't have to worry about free()ing them explicitly in order to not leak memory. Please read README.malloc. +Don't use non-ASCII characters in source files; not all compiler +environments will be using the same encoding for non-ASCII characters, +and at least one compiler (Microsoft's Visual C) will, in environments +with double-byte character encodings, such as many Asian environments, +fail if it sees a byte sequence in a source file that doesn't correspond +to a valid character. This causes source files using either an ISO +8859/n single-byte character encoding or UTF-8 to fail to compile. Even +if the compiler doesn't fail, there is no guarantee that the compiler, +or a developer's text editor, will interpret the characters the way you +intend them to be interpreted. + 1.1.3 Robustness. Wireshark is not guaranteed to read only network traces that contain correctly- |