about summary refs log tree commit diff stats
path: root/subx/apps/dquotes
Commit message (Collapse)AuthorAgeFilesLines
...
* fix a stale register value in dquotes.subxKartik Agaram2019-05-141-0/+0
| | | | | | | | | | | | | 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-0/+0
|\ | | | | | | | | 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/+0
| |\ | | | | | | | | | apps/dquotes still segfaulting on native run.
| | * 5151 - use mmap everywhere we need a heapKartik Agaram2019-05-101-0/+0
| | | | | | | | | | | | | | | 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-0/+0
| | | | | | | | | | | | Convert raw literal strings (no escape sequences) to the data segment.
* | | standardize function namesKartik Agaram2019-05-021-0/+0
|/ / | | | | | | | | Operations on buffered-file now always include the word 'buffered'. More verbose, but hopefully this highlights holes in the library.
* / new failing test in dquotes phaseKartik Agaram2019-04-281-0/+0
|/ | | | | | | | | | | | | | | 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
* 5118 - convert int to stringKartik Agaram2019-04-231-0/+0
|
* 5112Kartik Agaram2019-04-191-0/+0
|
* 5108Kartik Agaram2019-04-181-0/+0
|
* 5107Kartik Agaram2019-04-181-0/+0
|
* 5106Kartik Agaram2019-04-171-0/+0
|
* 5105Kartik Agaram2019-04-161-0/+0
| | | | | 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-0/+0
| | | | Don't forget metadata for string literals.
* 5103Kartik Agaram2019-04-161-0/+0
|
* 5102 - tokenize string literalsKartik Agaram2019-04-161-0/+0
Current plan: $ cat files.subx ... |dquotes |assort |pack |survey |hex > a.out