Carl Gay

[OD 2023.1 on x86_64-linux] Running into (what looks to me like) this again today with the protocol-buffers library. ``` cd $PB && dylan build protocol-buffers-test-suite Open Dylan 2023.1 Opened project...

``` (lldb) run Process 567215 launched: '/home/cgay/dylan/workspaces/pb/_build/bin/protocol-buffers-test-suite' (x86_64) Running suite protocol-buffers-test-suite: Running benchmark benchmark-encode-varint-max-uint64: PASSED in 0.206712s and 4KiB Running test test-encode/decode-varint:Process 567215 stopped * thread #1, name = 'Main...

[wire-format.dfm.txt](https://github.com/dylan-lang/opendylan/files/12051836/wire-format.dfm.txt)

Maybe the bitcode is also useful...here's the whole _build/build/protocol-buffers directory: [protocol-buffers-build-dir.tgz](https://github.com/dylan-lang/opendylan/files/12051955/protocol-buffers-build-dir.tgz)

Even though I'm logged into Matrix, following the link to it is pretty painful, so I'm copying the comments here: It seems that https://github.com/dylan-lang/opendylan/issues/1377 happens when you try to call...

Pinging @cgay ... why haven't you fixed this yet?

The main relevant doc is here: https://opendylan.org/library-reference/system/file-system.html#options-when-creating-file-streams `open-file-stream` returns a `` or signals an error. This seems right and good. Returning `#f` the way Common Lisp's `open` function returns `nil`...

(1) sort of makes sense in CL because nil is a synonym for stdin/stdout but less so in Dylan. (2) has the problem that it changes the semantics if the...

The above link doesn't work for me (anymore). This link seems to work for me, to find where the discussion started: https://app.element.io/#/room/#dylan-lang_general:gitter.im/$ersG93YXlTKMgFYkA62O-Jg5eqTY4uxyOQDmbKDsSDs

I believe this is done.