Releases: rail5/polonius
Releases · rail5/polonius
v0.5.15
v0.5.14
- Added -f option to polonius-editor
The -f option allows the user to specify a FILE which contains our
instruction sequences, rather than specifying those instructions
via the command line.
E.g.: polonius-editor ./text.txt -f ./instructions.txt - Patched another bug found by the test suite in which Polonius
couldn't handle blank lines in instruction sequences
v0.5.13
- Polonius can now accept single-line 'delimited' instructions
Multiple instructions of the same type can now be given on a single
line in the format: INSERT 0 abc; 10 def; 20 ghi
Or: REPLACE 0 abc; 10 def; 20 ghi
Or: REMOVE 0 2; 10 12; 20 22
Literal semicolons can also be inserted by escaping the semicolon
with a backslash, as in:
INSERT 10 along the wall to keep\; and slept - 'Instruction sets' have been renamed to the more appropriate
'Instruction sequences'
This gives a clearer idea of what they are - Added loads more tests
- Patched another small bug found by the tests
v0.5.12
v0.5.11
- Use the program_name variable instead of hard-coding the name into
error messages - Make sure that the user provides instructions to execute
- Refuse to create a new file if the instruction sequence is invalid.
If we're creating a new file, the first instruction should be an
INSERT - Immediately write a newline char when creating a new file
v0.5.10
v0.5.9
v0.5.8
- More sanity checks on block size inputs
Block sizes are now stored as 64-bit integers, and there are more
checks in place to ensure valid input. This closes #30 - Fixed problem with stack overflows in regex searches
The standard library's regex search function is recursive and has
potential to overflow the stack, particularly when searching very
large documents (in fact the point of polonius) This was documented
before it was fully understood in Github issue #29
To fix it, polonius-reader is now compiled with -fsplit-stack.
This option allows a discontiguous stack which grows automatically
as needed