dpc
dpc copied to clipboard
dvanhorn
Designing Programs with Class
This just gives a "bad syntax" error and should do better: ``` #lang class/0 (define-class a% (check-expect 5)) ```
This gives a bad syntax error: ``` #lang class/0 (define-class a% (define/asdf (m) 1)) ``` which is ``` define-class: There were multiple syntax errors. The first error follows: expected the...
We've moved away from the `(field f)` form of referencing fields and instead have used automatically generated accessor methods: `(send this f)`. We should do the same for `(set-field! f...
As in [Chapter 17](https://github.com/dvanhorn/dpc/blob/cb800dbb3b1017f789ac717082c76c8bc47a4e08/book/chapter/17.scrbl#L493): > The functional style is slow, but easy. > The structural style is fast, but hard. 1. Slow/fast and easy/hard are vague terms here, aren't they?...
The paragraph at [line 386-388 of Chapter 17](https://github.com/dvanhorn/dpc/blob/cb800dbb3b1017f789ac717082c76c8bc47a4e08/book/chapter/17.scrbl#L386) is unclear.
Kill function application syntax for method calls within method definitions and bring back only after inheritance.
Allow students to use mechanisms they understand with `universe`/`big-bang`, once we have overrriding.
Right now, it's all horribly duplicated.
`class/0` supports `define/public` and `define/private`. We can't take them out until after the semester, but then they should go.