> That sounds great, and I'm sure one of the Pict
> experts could write better examples than mine.
Yes, but still, upload your code to the cookbook.
> But please look at the
> slideshow & the keybinding dox in 3.3.8 Defining Custom Shortcuts.
> See if you think if there's enough examples. I know
Thanks, Shriram! That sounds great, and I'm sure one of the Pict
experts could write better examples than mine. But please look at the
slideshow & the keybinding dox in 3.3.8 Defining Custom Shortcuts.
See if you think if there's enough examples. I know I floundered.
Bill,
I agree with you that docs can always be improved with some choice
examples. Thanks for thinking to contribute. In this regard, Horace
is being perhaps a bit too defensive.
However, your particular example strikes me as far too verbose for
inclusion in documentation, which needs to also b
There is a mistake in your example, I've copied below a working
one. (renamed variable P to ph)
Thanks, Horace. I wonder how I stuck that mistake in my post: it's
correct in my code, and it won't run with that busted P instead of ph.
I think racket has excellent documentation. There se
[The early registration deadline is only 2 days from now. Please register
ASAP!]
CALL FOR PARTICIPATION
2010 Workshop on Scheme and Functional Programming
Montreal, Quebec, Canada
Saturday and Sunday August 21-22, 2010
There is a mistake in your example, I've copied below a working one.
(renamed variable P to ph)
I think racket has excellent documentation. There seems to be a very
fine line between overly verbose documentation and concise
documentation.
Horace.
#lang slideshow
;; Digit = 1 | 2 | 3 | 4 | 5 | 6
Here's a better example for slideshow/pict, a new version of
`print-sudoku'. Racket sounds like a very interesting ambition
attempt to ``to fuse cutting-edge programming-language research with
everyday programming.'' I don't know how far along the project is,
but eventually you'll need good docum
Matthias Felleisen writes:
> 2. Could drracket reindent all every time a programmer hits {return | run |
> submission server request }?
I think it would be enough to pop up a dialogue box when the user tries
to save if the code isn't indented properly. That would send a clear
message, cannot
8 matches
Mail list logo