about summary refs log tree commit diff stats
path: root/subx/apps/dquotes.subx
Commit message (Collapse)AuthorAgeFilesLines
* .Kartik Agaram2019-05-251-6/+0
| | | | | hoist 'Heap' variable into the std library in anticipation of the parse-array-of-ints primitive.
* another phase that supports the new segment syntaxKartik Agaram2019-05-171-18/+18
| | | | | | | | | | Current state: ✓ hex.subx (no changes required) survey.subx ✓ pack.subx (fixed here) assort.subx ✓ dquotes.subx (has failing tests for other reasons)
* 5181Kartik Agaram2019-05-171-0/+20
| | | | Test for the bugfix of commit 2f49a27504.
* 5180Kartik Agaram2019-05-161-22/+12
| | | | | | | Clean up some old TODOs related to our pre-mmap limitations. Also caught another case of using the wrong comparison. When comparing addresses, one must always use unsigned rather than signed jump instructions.
* complete the skeleton of dquotes.subxKartik Agaram2019-05-151-42/+98
| | | | | | | | | | | | | | | | Still some failing tests: - emit-string-literal-data doesn't ignore metadata when computing the length of literal strings - emit-string-literal-data doesn't handle escape sequences One issue doesn't have a failing test: - emit-metadata doesn't handle string literals containing '/' All these open issues involve a common design question: how to parse a 'word' that includes a string literal that may include spaces. For everything else I know words can't contain spaces and datums can't contain slashes. But for string literals things are tougher.
* .Kartik Agaram2019-05-141-9/+9
|
* fix a stale register value in dquotes.subxKartik Agaram2019-05-141-1/+2
| | | | | | | | | | | | | How did things seem to be working until now? - We were saving an address from the stack to stream.read - When we read this address in skip-chars-matching:loop, we used to stop early But now we've moved the stack to a larger address, one where the most significant byte is set. When the stack address now gets to skip-chars-matching:loop, it's treated as a negative number and we proceed through the loop. At which point we try to index into the array using it. No real test to be written to protect against this :(
* Merge branch 'dquotes' into dquotes-1Kartik Agaram2019-05-131-1/+230
|\ | | | | | | | | dquotes.subx is now segfaulting after this merge. Seems to be trying to use addresses from the old stack.
| * Merge branch 'master' into dquotesKartik Agaram2019-05-101-0/+24
| |\ | | | | | | | | | apps/dquotes still segfaulting on native run.
| * | implemented emit-metadatanc2019-05-041-1/+57
| | |
| * | failing tests for part 2/2 of dquotesKartik Agaram2019-04-291-0/+173
| | | | | | | | | | | | Emitting the metadata for literal strings.
* | | Merge branch 'master' into dquotes-1Kartik Agaram2019-05-101-0/+24
|\ \ \ | | |/ | |/| | | | Segfault in this branch is now fixed.
| * | 5151 - use mmap everywhere we need a heapKartik Agaram2019-05-101-0/+24
| | | | | | | | | | | | | | | All tests passing now. Things are very explicit; before a program can `allocate` memory, it has to first obtain a segment from the OS using `new-segment`.
* | | dquotes - emit data segment - no escapesKartik Agaram2019-05-031-1/+138
| | | | | | | | | | | | Convert raw literal strings (no escape sequences) to the data segment.
* | | standardize function namesKartik Agaram2019-05-021-6/+6
| | | | | | | | | | | | | | | Operations on buffered-file now always include the word 'buffered'. More verbose, but hopefully this highlights holes in the library.
* | | failing tests for part 1/2 of dquotesKartik Agaram2019-04-291-1/+274
| |/ |/| | | | | Converting literal strings into bytes in the data segment.
* | new failing test in dquotes phaseKartik Agaram2019-04-281-1/+259
|/ | | | | | | | | | | | | | | I'm switching to a more exposed working dynamic after chatting with Charles Saternos (https://github.com/akkartik/mu/pull/19). From now on I'll start a new branch for big features. Branches won't always pass all their tests. Phases have gone weeks in the past before being committed all at once. Developing in a branch gives others the opportunity to see more current progress and jump in more easily. Some 'kata' branches for new contributors to start at: * add two numbers: https://github.com/akkartik/mu/pull/21 * write a string to a byte stram: https://github.com/akkartik/mu/pull/22 * print a number in decimal to a byte stream: https://github.com/akkartik/mu/pull/20
* 5127Kartik Agaram2019-04-261-1/+1
|
* 5124Kartik Agaram2019-04-231-1/+1
|
* 5123Kartik Agaram2019-04-231-4/+0
|
* 5112Kartik Agaram2019-04-191-1/+63
|
* 5108Kartik Agaram2019-04-181-10/+10
|
* 5107Kartik Agaram2019-04-181-4/+281
|
* 5106Kartik Agaram2019-04-171-1/+145
|
* 5105Kartik Agaram2019-04-161-28/+2
| | | | | Pull in a _different_ function than `next-word` (commit 5092) into a shared file between phases. Let's see how this goes.
* 5104Kartik Agaram2019-04-161-18/+13
| | | | Don't forget metadata for string literals.
* 5103Kartik Agaram2019-04-161-61/+88
|
* 5102 - tokenize string literalsKartik Agaram2019-04-161-0/+582
Current plan: $ cat files.subx ... |dquotes |assort |pack |survey |hex > a.out