about summary refs log tree commit diff stats
path: root/088file.mu
Commit message (Collapse)AuthorAgeFilesLines
* 3693Kartik K. Agaram2016-11-251-1/+5
|
* 3656Kartik K. Agaram2016-11-101-2/+2
| | | | | | | | | | | | | | Periodic cleanup to replace 'reply' with 'return' everywhere in the repo. I use 'reply' for students to help reinforce the metaphor of function calls as being like messages through a pipe. But that causes 'reply' to get into my muscle memory when writing Mu code for myself, and I worry that that makes Mu seem unnecessarily alien to anybody reading on Github. Perhaps I should just give it up? I'll try using 'return' with my next student.
* 3608 - concurrent writes to fake file systemKartik K. Agaram2016-10-291-1/+5
|
* 3574Kartik K. Agaram2016-10-231-16/+16
| | | | Shorter branches above longer ones.
* 3573 - client socket testsKartik K. Agaram2016-10-231-2/+8
| | | | This is just the same as tests for a fake file-system.
* 3507Kartik K. Agaram2016-10-161-4/+4
|
* 3504Kartik K. Agaram2016-10-151-21/+21
|
* 3390Kartik K. Agaram2016-09-171-4/+4
|
* 3389Kartik K. Agaram2016-09-171-14/+14
|
* 3388Kartik K. Agaram2016-09-171-9/+9
|
* 3385Kartik K. Agaram2016-09-171-13/+13
|
* 3379Kartik K. Agaram2016-09-171-13/+13
| | | | Can't use type abbreviations inside 'memory-should-contain'.
* 3341Kartik K. Agaram2016-09-121-4/+4
| | | | | | | Process type abbreviations in function headers. Still a couple of places where doing this causes strange errors. We'll track those down next.
* 3338Kartik K. Agaram2016-09-121-2/+2
| | | | Process type abbreviations in container definitions.
* 3337 - first use of type abbreviations: textKartik K. Agaram2016-09-121-4/+4
| | | | | In the process I've uncover a couple of situations we don't support type abbreviations yet. They're next.
* 3256Kartik K. Agaram2016-08-261-0/+12
| | | | | Bugfix in filesystem creation. I'm sure there are other fake-filesystem bugs.
* 3254Kartik K. Agaram2016-08-261-0/+1
|
* 3253 - writing to fake files in scenariosKartik K. Agaram2016-08-251-3/+45
| | | | High time I committed the part that works.
* 3243Kartik K. Agaram2016-08-221-2/+2
|
* 3238Kartik K. Agaram2016-08-211-2/+2
| | | | | | Clean up primitive for reading from file. Never return EOF character. Stop using null character to indicate EOF as well. Instead, always use a second product to indicate EOF, and require calls to use it.
* 3237Kartik K. Agaram2016-08-211-2/+2
| | | | | | | | More checks for unsafe filesystem primitives. Most important, make sure the product of any $close-file instruction is never ignored, and that it's the same variable as the ingredient. (No way to indicate that in Mu code yet, but then Mu code should always be safe and not require such checks.)
* 3231 - reading from fake files in scenariosKartik K. Agaram2016-08-201-4/+43
|
* 3229 - fake file systems using 'assume-filesystem'Kartik K. Agaram2016-08-201-1/+6
| | | | Built with Stephen Malina.
* 3225 - testable interface for writing filesKartik K. Agaram2016-08-181-3/+24
| | | | | | | | For example usage of file operations, see filesystem.mu. Is it ugly that we don't actually write to disk unless we wait for the writing routine to exit? Maybe there's a nice way to wrap it. At any rate, all buffering is explicit, which seems a win compared to *nix.
* 3224Kartik K. Agaram2016-08-181-5/+0
|
* 3203 - testable interface for reading a fileKartik K. Agaram2016-08-161-0/+31
This commit was written by Stephen Malina. Thanks also to Stephen for running into the bug of commit 3202.
generated by cgit-pink 1.4.1-2-gfad0 (git 2.36.2.497.gbbea4dcf42) at 2024-12-01 10:39:16 +0000