Carl Gay
Carl Gay
`define constant foo = make();` should be able to infer that `foo` is of type `` but instead it currently gives it type ``.
This drives me crazy and it's not just cosmetic. I just spent a(nother) half hour debugging why my print-object method wasn't being used only to find that it's because format...
It should be trivial to run a single-file Dylan program via the command-line without even knowing how to invoke the compiler. "dylan foo.dylan" should work. First step, determine the state...
In general, the file-system docs don't seem to say what errors are signaled when functions like do-directory and directory-contents are called. There is an entry for `` that say it's...
``` Module: my-app define function main (name :: , arguments :: ) local method usage() format-out("foo\n"); end; arguments.size = 1 | usage; format-out("Hello, world!\n"); end; main(application-name(), application-arguments()); ``` Above I...
I just found a bunch of dead code. If the compiler had warned about unused local variables I would've seen it long ago because I would've gotten warning about definitions...
Given this code, ``` define function main (name :: , arguments :: ) let name = "foo" format-out("Hello, world!\n"); end; ``` I get this error: ``` /home/cgay/dylan/my-app/my-app.dylan:5: Serious warning -...
``` .../main.dylan:162: Serious warning - Reference to undefined binding { in dylan-tool}. --------- define function library-from-lid (path :: ) => (library-name :: ) --------- .../main.dylan:162: Serious warning - Reference to...
Can we do a better job of printing methods than this? i.e., can we print the method name, if it wasn't anonymous? (Actually even then it could be "outer-function-foo#method-n".) ```...
The `system:operating-system:run-application` documentation is very outdated and doesn't mention any of the new arguments.