failed to take the encoding of character

strings into account, so identical byte patterns are not

necessarily identical strings, and similarly Latin-1 and UTF-8

versions of the same string differ in byte pattern.

which had been created based on an existing S3

The check for consistent ordering of superclasses was not

ignoring all conditional relations (the symptom was usually

Trying to assign into a raw vector with an index vector

s could cause a segfault.  Reported by Hervé

filename argument was missing.  Reported by Martin Morgan.

(and functions that use it, including argument

completion in the console) did not handle special built-in

functions.  Reported by Romain Francois.

could segfault when called on character data under certain (rare)

circumstances involving marked non-native encodings.

appending to it (as documented and intended).

Unserializing a pre-2.8 workspace containing pure ASCII

character objects with a Latin-1 or UTF-8 encoding would corrupt

2.9.2 patched and earlier can be found in files