A unary plus before X'..' keeps the blob, as SQLite drops the plus. Bare default words take non-ASCII characters and a later dollar sign, as SQLite identifiers do. The comment-after-e fixture uses 0x1e--, which SQLite creates.
SQLite accepts a `CREATE TABLE` with no spaces between its parts, and reading one went wrong in three ways. A constraint written straight after a type (`REAL(8)CHECK(...)`) became part of the type, which changed how the column's values were read (REAL as INTEGER, BLOB as TEXT). A quoted type straight after a column name (`id"INTEGER" PRIMARY KEY`) became part of the name, so the column wasn't seen as the row's key. And `DEFAULT-5`, `STRICT;` or `WITHOUT ROWID;` weren't recognised. Names, types and clauses are now split wherever SQLite splits them, and only its five whitespace characters count as space.
Follow-up to #2080. `nint`, `nuint` and `dynamic` are only keywords when nothing in scope has that name, but a conversion operator to a program's own type called `nint` or `dynamic` was read as the built-in and reported as missing; such a name is now looked up among the program's types first. An explicit `System.IntPtr` keeps meaning the built-in. And a conversion to `List<String>` where `String` is another namespace's type, imported without `using System;`, is matched to that type before `String` is tried as `string`.
- Strip `global::` and convert metadata `/` nested-type separators in `norm_type`
as well as `norm_type_qualified` so method parameters taking nested or
`global::`-qualified types reconcile without mismatch.
- Emit `ref ` only for leading `ref` modifiers followed by whitespace and a type
start, avoiding spurious spaces inside identifiers containing `ref` or on `@ref`
value types.
- Keep non-`System` types named like CLR built-ins (such as `App.String`) distinct
from C# built-in keywords in qualified conversion-target comparisons.
- Collapse multi-dimensional zero-lower-bound CLI array shapes (`[0...,0...]`) to
C# rank commas (`[,]`) while preserving rank-1 `[0...]` and non-zero/sized bounds.
SQLite lets table constraints follow each other without a comma (`UNIQUE(v) PRIMARY KEY(id)`) and lets a key column sit in extra parentheses (`PRIMARY KEY((id))`). Both the rowid-alias check and the WITHOUT ROWID key layout now find the primary key in those forms, so rows from such tables show their key values in the right columns.
Follow-up to #2049. A conversion operator whose target type is named `@checked` was read as a checked operator with no target type, because the `@` was lost before the name was compared with the `checked` keyword. The keyword is now recognised only when it was written without `@`.
In an Apple keyed archive, a string whose bytes were stored as a reference to another object was shown as raw data, and a date stored as a whole number of seconds was not shown as a date. References are now followed, within the existing byte and node limits, and integer times are formatted as dates.
The SquashFS reader ended the inode table at the directory table and the directory table at the fragment or id table. An image with an export or xattr table in between, or with its tables in another order, was read past the table's end and reported as damaged. Each table now ends at the nearest following table of the six, or at the end of the filesystem.
A C# member or parameter named with a verbatim identifier (`@class`, `@namespace`, `@event`, `@operator`) had its `@` dropped and was then read as the keyword, which opened fake scopes and changed member kinds. Verbatim identifiers are now kept as names and never matched as keywords or modifiers.
SQLite accepts a primary key written as PRIMARY KEY((a), b) in a WITHOUT ROWID table. The reader stopped at the first closing parenthesis and could not work out the stored row layout. It now reads to the matching end of the key list, finds the column inside redundant parentheses and uses its outermost collation.
The DOS header report took any "PE" prefix at the extended-header offset for a Windows extension, including a cut-off signature or "PENA" in unrelated bytes. The full four-byte signature is now required. A complete signature that overlaps the DOS header, as hand-packed small executables have, is still reported.
A Java class file that ended partway through a class-level attribute was read with no warning, so source or signature details after the cut were silently missing. The reader now keeps the attributes it could read and warns when the table ends early.
A TAR member with a valid PAX size still stopped the archive walk when its superseded size field held invalid octal, so later members vanished from the listing. The PAX size is now read first for ordinary members, and the old field is read and checked only when no override applies.
An IPv6 packet whose Next Header is 59 (no next header) got an invented "other" transport record that included any bytes after the header. Transport decoding now stops at 59, also when an extension header supplies it; other protocol values are decoded as before.
An indexed source map that also carried a top-level `sources` list reported those names as part of the bundle although no section maps to them, and they could push a real source out of a full inventory. An indexed map now keeps only its file name and takes its sources from its sections.
The Mach-O readers took the whole remainder of a load command as a library name or runpath when its path had no terminating NUL, so a command that never finished its string still supplied dependency evidence. The NUL must now be inside the command, in both summary views.
A ZIP member using the original Zstandard method number, 20, was listed with an unknown method and could not be extracted or found in firmware scans. It now goes through the same name, bounded decoder and archive discovery as the current number, 93.
In a WITHOUT ROWID table whose primary key names one column twice with different collations, SQLite stores a key slot for each. The reader collapsed them into one and so read the next column from the wrong slot. A repeated key term is now dropped only when its column and effective collation are already present.
An Android manifest with a minimum SDK of 23 and no target SDK reported a provider as exported by default. Android takes the minimum SDK as the target when none is given, and from 17 a provider is private by default. Export inference now uses the minimum SDK when the target is omitted; explicit targets and explicit exported values are unchanged.