From f1aed94cc88c0cdeb60f1e799492663566a0cd0b Mon Sep 17 00:00:00 2001 From: Kartik Agaram Date: Tue, 27 Nov 2018 13:31:48 -0800 Subject: 4789 --- subx/Readme.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) (limited to 'subx/Readme.md') diff --git a/subx/Readme.md b/subx/Readme.md index 37e666b5..15e17219 100644 --- a/subx/Readme.md +++ b/subx/Readme.md @@ -360,9 +360,9 @@ Here's what I've built so far: never accidentally go out of array bounds. * `read`: takes two arguments, `f` and `s`. - - `s` is an address to a _stream_ to save the read data to. We read as much - data as can fit in `s`, and no more. - - `f` is either a file descriptor to write `s` to, or (in tests) a _stream_. + - `f` is either a file descriptor to read from, or (in tests) a stream. + - `s` is an address to a stream to save the read data to. We read as much + data as can fit in (the free space of) `s`, and no more. Like with `write()`, this wrapper around the Unix `read()` syscall adds the ability to handle 'fake' file descriptors in tests, and reduces the chances @@ -374,7 +374,7 @@ Here's what I've built so far: * `stop`: takes two arguments: - `ed` is an address to an _exit descriptor_. Exit descriptors allow us to - `exit()` the program normally, but return to the test harness within + `exit()` the program in production, but return to the test harness within tests. That allows tests to make assertions about when `exit()` is called. - `value` is the status code to `exit()` with. -- cgit 1.4.1-2-gfad0