about summary refs log tree commit diff stats
Commit message (Collapse)AuthorAgeFilesLines
* 7260Kartik Agaram2020-11-172-15/+11
| | | | This seems to preserve the intent of commit 6555.
* 7259Kartik Agaram2020-11-172-5/+6
|
* 7258Kartik Agaram2020-11-172-9/+9
|
* 7257 - partially undo commit 7253Kartik Agaram2020-11-172-8/+8
| | | | I don't need to pass the function pointer quite so low. I think..
* 7256Kartik Agaram2020-11-171-6/+6
|
* 7255Kartik Agaram2020-11-171-1/+1
|
* 7254Kartik Agaram2020-11-173-3/+5
|
* 7253 - mu.subx: starting to bounds-check 'index'Kartik Agaram2020-11-162-50/+51
| | | | | First step: start passing the function name into code-generation functions. We're going to need it for the error message.
* 7252Kartik Agaram2020-11-1619-1445/+1445
|
* 7251Kartik Agaram2020-11-164-50/+53
|
* 7250Kartik Agaram2020-11-166-25/+17
|
* 7249Kartik Agaram2020-11-1515-35694/+36870
|
* 7248 - mu.subx: new primitive 'clear-object'Kartik Agaram2020-11-155-17/+155
|
* 7247Kartik Agaram2020-11-152-11/+64
|
* 7246 - tile: segment each function's areaKartik Agaram2020-11-151-2/+14
|
* 7245 - tile: right-align functionsKartik Agaram2020-11-153-13/+102
|
* 7244 - tile: new layout for primitivesKartik Agaram2020-11-151-16/+48
|
* 7243 - tile: starting to make functions editableKartik Agaram2020-11-151-14/+24
|
* 7242Kartik Agaram2020-11-151-1/+1
|
* 7241 - mu.subx: check float registersKartik Agaram2020-11-152-0/+148
|
* 7240Kartik Agaram2020-11-152-20/+34
|
* 7239Kartik Agaram2020-11-153-63/+170
|
* 7238 - mu.subx: final restrictions on 'addr'Kartik Agaram2020-11-1516-14/+354
| | | | I had to tweak one app that wasn't following the rules.
* 7237Kartik Agaram2020-11-142-2/+3
| | | | | | | Minor tweaks to get Mu shell running nicely on a Linux console atop Qemu. We also need to switch a few 256-color codes to 8-color mode. I'm not sure whether/how to patch the repo for those.
* 7236Kartik Agaram2020-11-141-1/+1
|
* 7235 - belatedly add spiritual forksKartik Agaram2020-11-141-0/+6
|
* 7234Kartik Agaram2020-11-141-1/+1
|
* 7233 - fix some warnings from gcc 9Kartik Agaram2020-11-131-3/+3
| | | | | | Make strncpy a little less error-prone. Just use memcpy where that suffices: https://stackoverflow.com/questions/56782248/gcc-specified-bound-depends-on-the-length-of-the-source-argument/56782476#56782476
* 7232 - mu.subx: more checks for byte typesKartik Agaram2020-11-122-11/+149
|
* 7231Kartik Agaram2020-11-123-3/+47
|
* 7230 - mu.subx: some more checks for stmt outputsKartik Agaram2020-11-122-10/+153
|
* 7229 - tile: fix ctrl-eKartik Agaram2020-11-122-7/+20
|
* 7228Kartik Agaram2020-11-121-3/+7
|
* 7227Kartik Agaram2020-11-1140-36171/+37727
|
* 7226Kartik Agaram2020-11-114-81/+0
|
* 7225Kartik Agaram2020-11-1136-60/+293
| | | | | | | Both manual tests described in commit 7222 now work. To make them work I had to figure out how to copy a file. It requires a dependency on a new syscall: lseek.
* 7224Kartik Agaram2020-11-111-19/+32
|
* 7223Kartik Agaram2020-11-111-2/+0
|
* 7222Kartik Agaram2020-11-103-43/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Ok, I found a failing manual test for files as well. Here are the two steelman tests, one for screens and one for files: 1. 5 5 fake-screen =s s 1 down 1 right ctrl-d foo expand final state: s foo foo s 1 down 1 right ⇗ ┌─────┐ ┌─────┐ ┌─────┐ 1 ┌─────┐ 1 ┌─────┐ │ ┌─────┐ │ ┌─────┐ │ ─ │ │ │ │ ─ └─────┘ └─────┘ └─────┘ └─────┘ └─────┘ └─────┘ └─────┘ 2. "x" open =f f read f read ctrl-d read2 expand final state: f read2 read2 f read f read ⇗ FILE ❝def❞ FILE ❝abc❞ FILE ❝❞ ❝def❞ ❝ghi❞ In both cases there are 3 levels of issues: - getting a single-line expression to work - getting a single-line expression to work when operating on a binding defined in a previous line - getting an expanded function call to work The third is where the rub is right now. And what both examples above share is that the function performs 2 mutations to the screen/file. So we need a deep copy after all. And it's not very clear how to copy a file descriptor including the seek location. Linux's dup() syscall creates an alias to the file descriptor. And opening /proc seems awfully Linux-specific: https://stackoverflow.com/questions/54727231/duplicating-file-descriptor-and-seeking-through-both-of-them-independently/54727424#54727424
* 7221Kartik Agaram2020-11-091-62/+0
| | | | | I can't get file values to exhibit the same problem. Why are fake screens special?
* 7220Kartik Agaram2020-11-091-5/+12
| | | | | | | | | Even this isn't enough. While shallow copies keep us from transferring new bindings to callers, the screen object is still the same, so mutations to bindings are contagious. Basically I'm losing IQ points from programming in a language that encourages mutation over copying.
* 7219Kartik Agaram2020-11-093-69/+69
| | | | We're still busted, but on the right track.
* 7218Kartik Agaram2020-11-095-11/+139
| | | | | | | | | | | | | | | This bug was incredibly painful to track down: the one-line fix is to replace 'line' with 'first-line' in the call to 'evaluate' in render-line before recursing. Things that made it challenging: - A high degree of coiling with recursive calls and multiple places of evaluation. - An accidental aliasing in bindings (when rendering the main column in render-line) that masked the underlying bug and made things seem to work most of the time. - Too many fucking arguments to render-line, a maze of twisty line objects all alike.
* 7217Kartik Agaram2020-11-082-6/+24
|
* 7216Kartik Agaram2020-11-082-2/+63
| | | | | In addition to fixing a segfault, the realization here is that we don't always have a type name. Error messages need to take that into account.
* 7215Kartik Agaram2020-11-072-2/+31
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Attempt #3: always create a copy of the bindings before each column/evaluate. The details are fuzzy in my head, but it seemed worth trying. I figured I'd either see the old duplication behavior or everything will work. Instead I'm seeing new problems. commit 7208: 5 5 fake-screen =s s 1 down 1 right expected: | - observed: | | - commit 7210-7212: 5 5 fake-screen =s s 1 down 1 right [define foo] s foo [expand foo] observed: no bindings available when rendering foo expanded commit 7213: 5 5 fake-screen =s s 1 down 1 right [define foo] s foo [expand foo] expected within foo: | - observed within foo: | | - commit 7215: 5 5 fake-screen =s s 1 down 1 right [define foo] s foo [expand foo] observed: no bindings available when rendering foo expanded
* 7214 - undo 7213Kartik Agaram2020-11-072-5/+7
| | | | | | | | | | Turns out even that doesn't work. There are two distinct use cases here: 1. Keeping columns from infecting each other. 2. Expanding function calls. Perhaps ping-ponging between them is a sign I need tests.
* 7213 - redo the bugfix of 7210Kartik Agaram2020-11-072-7/+5
| | | | | | | | It turns out deciding when to initialize the table of bindings is quite a thorny problem in the presence of function calls (since they need their args bound). In time I should probably support a linked list of tables. For now I'll just continue to reuse tables, but perform lookups in reverse order so that the correct binding is always returned.
* 7212Kartik Agaram2020-11-071-1/+1
|
* 7211Kartik Agaram2020-11-071-0/+24
|
generated by cgit-pink 1.4.1-2-gfad0 (git 2.36.2.497.gbbea4dcf42) at 2024-07-06 06:21:14 +0000