| Age | Commit message (Collapse) | Author |
|---|
|
Now you can use command line arguments to list a set of input files
for the interpreter to use.
Currently outputs the data parsed per file.
|
|
Apparently you can't just `fseek` because it's "not portable" and
"deeply offensive" or whatever, so here's a really dirty chunk based
allocator which uses `fread` to just read chunks of data at a time and
basically runs around this issue.
While it's slower than an fseek solution for general files, this
solution allows pipes and other _weird_ things that count as "files"
to just werk.
|
|
Using a buffer structure allows me to pass more information to
callers and a bit more discretion over how data is passed.
Better error reporting via having a file handle and reporting it
Emacs/GCC style.
|
|
Simple parser, took like an hour.
Not very smart but at least it's like O(n).
|
