| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
Bit of a weird situation this one, since the rule is from NTriples but serd
doesn't actually use it in the NTriples parser (since it uses a stricter one
instead). Still, I think it makes sense here, and in practice, makes for a
more sensible inlining situation.
|
|
[WIP] Broken on 32-bit
This makes the reader stack manipulations stricter, to make the code more
regular and avoid redundant work and bad cache activity. Now, functions that
push node headers and their bodies are responsible for (more or less)
immediately pushing any trailing null bytes required for termination and
alignment.
This makes the writes to the node in the stack more local, ensures nodes are
terminated as early as possible (to reduce the risk of using non-terminated
strings), and avoids the need to calculate aligned stack allocations.
|
|
|
|
Though potentially useful, I don't think the complexity cost of the old
interface (both to the implementation and to the user) is worth it. A special
tool to transform blank node labels (for example with regular expressions)
would be a better approach to this if it's ever needed in the future.
|
|
|
|
[WIP] Testing?
|
|
|
|
[WIP] Command line option, move later?
This adds a reader flag and serdi option for extending a syntax with support
for SPARQL-like variables, for storing things like patterns or simple queries.
|
|
|
|
|
|
Towards using these in the writer to escape names more precisely.
|
|
|
|
|
