Hi,
In trying to look up the documentation for some of the new features in the
release it looks like the documentation on http://docs.racket-lang.org is
still for 6.0.1
I was able to just use the local documentation, so it’s not a big deal. I
just wanted to make sure it didn’t fall
In cases where the semantics of constructs are changed, should the
documentation have a margin note stating the version number of the
change?
I am in particular thinking of case:
At Sun, 8 Dec 2013 11:09:39 +0100, Jens Axel Søgaard wrote:
In cases where the semantics of constructs are changed, should the
documentation have a margin note stating the version number of the
change?
Yes, it really should.
Details like this get listed in HISTORY.txt (the `case` form
Should the history.txt files get stuck into the end of the manuals for the
time being?
Robby
On Sun, Dec 8, 2013 at 8:37 AM, Matthew Flatt mfl...@cs.utah.edu wrote:
At Sun, 8 Dec 2013 11:09:39 +0100, Jens Axel Søgaard wrote:
In cases where the semantics of constructs are changed, should the
Documentation hyperlinks are now covered by the package-dependency
checking of `raco setup'.
Dependencies that take the form of `for-label' imports were found by
normal module-dependency checking, already. The new checks cover cases
where a document refers to another document via `other-doc' or
I've pushed this change:
http://git.racket-lang.org/plt/commitdiff/d071dc43873b7e84a59e3c9df47a6c8b3f7c6b1d?hp=7b33298b6654bcd55105e24e99545b98db3206ba
Jay
On Mon, Jan 21, 2013 at 9:57 AM, Norman Gray nor...@astro.gla.ac.uk wrote:
Jay, hello.
On 2013 Jan 21, at 16:12, Jay McCarthy
Greetings.
In the web server, the documentation for RESPONSE and, by implication,
RESPONSE/FULL does not explain how to avoid including a message-body in the
response, as is required for 1xx, 204, 304 statuses (and those alone).
By experiment, giving RESPONSE/FULL a 'body' argument of #
Sorry, an addendum...
On 2013 Jan 21, at 12:23, Norman Gray nor...@astro.gla.ac.uk wrote:
In the web server, the documentation for RESPONSE and, by implication,
RESPONSE/FULL does not explain how to avoid including a message-body in the
response, as is required for 1xx, 204, 304 statuses
Jay, hello.
On 2013 Jan 21, at 16:12, Jay McCarthy jay.mccar...@gmail.com wrote:
I don't understand your concern.
The response structure, which is the only actual structure (everything
else is an interface on it)...
a) Allows #f as the mime type
...but the documentation doesn't say
I will second the idea behind this request. (I thought I had to use
dynamic-require's second argument in the summer, and after studying it for
quite a while, i was happy to figure out a way around it.)
On Sep 14, 2012, at 3:17 PM, Carl Eastlund wrote:
I just tried to figure out what the
Did you use `raco docs' to open the documentation page?
No.
All I did was to access the Help Desk from DrRacket's Help menu.
BTW, this is a fresh install, after uninstalling the previous version.
I can see the wrong links in the file index.html, in
AppData/Roaming/Racket/5.3.0.11/doc/
Hi,
Recent nightly builds (e.g., for 5.3.0.10 or 5.3.0.11) install
documentation files that incorrectly point to 5.3.0.4 files.
This is visible after accessing the Help Desk: the page
says it's for version 5.3.0.4 and clicking on any of the
links will show the problem.
Best,
António.
I think the 'guide' and 'reference' links could use a description of
what they are similar to the tutorial links.
On 07/01/2011 06:45 PM, Ryan Culpepper wrote:
I just pushed a commit intended to improve the usability of the main
documentation page, especially for newcomers to Racket. You can
This looks great to me.
Minor thing: Low-Level APIs = Low-Level API and the last section
actually can have a name other than misc I think.
Robby
On Sat, Jul 2, 2011 at 8:45 AM, Ryan Culpepper r...@cs.utah.edu wrote:
I just pushed a commit intended to improve the usability of the main
Great stuff. This is a big improvement.
Carl Eastlund
On Fri, Jul 1, 2011 at 8:45 PM, Ryan Culpepper r...@cs.utah.edu wrote:
I just pushed a commit intended to improve the usability of the main
documentation page, especially for newcomers to Racket. You can also
see the new version here:
On Sat, Jul 2, 2011 at 9:41 AM, Ryan Culpepper r...@cs.utah.edu wrote:
re Low-Level API: the other category labels are generally plural, and
other manuals might get inserted into this category (eg by planet packages)
The page is regenerated when new manuals are added, no? Just make it
plural
Four minutes ago, Robby Findler wrote:
On Sat, Jul 2, 2011 at 9:41 AM, Ryan Culpepper r...@cs.utah.edu wrote:
re Low-Level API: the other category labels are generally
plural, and other manuals might get inserted into this category
(eg by planet packages)
The page is regenerated when new
On Fri, Jul 1, 2011 at 9:41 PM, Ryan Culpepper r...@cs.utah.edu wrote:
re misc: Do you mean Other? Would you prefer Other Languages and
Libraries or Other Manuals?
I think those should just go under Experimental Languages, since
they're both languages, and at least one is experimental.
--
sam
On Sat, Jul 2, 2011 at 9:53 AM, Eli Barzilay e...@barzilay.org wrote:
Four minutes ago, Robby Findler wrote:
On Sat, Jul 2, 2011 at 9:41 AM, Ryan Culpepper r...@cs.utah.edu wrote:
re Low-Level API: the other category labels are generally
plural, and other manuals might get inserted into this
Three minutes ago, Robby Findler wrote:
On Sat, Jul 2, 2011 at 9:53 AM, Eli Barzilay e...@barzilay.org wrote:
Four minutes ago, Robby Findler wrote:
On Sat, Jul 2, 2011 at 9:41 AM, Ryan Culpepper r...@cs.utah.edu wrote:
re Low-Level API: the other category labels are generally
plural,
Yes, I understood you. I'm observing that making it plural is not helping.
On Fri, Jul 1, 2011 at 9:06 PM, Eli Barzilay e...@barzilay.org wrote:
Three minutes ago, Robby Findler wrote:
On Sat, Jul 2, 2011 at 9:53 AM, Eli Barzilay e...@barzilay.org wrote:
Four minutes ago, Robby Findler wrote:
On Fri, Jul 1, 2011 at 8:45 PM, Ryan Culpepper r...@cs.utah.edu wrote:
I just pushed a commit intended to improve the usability of the main
documentation page, especially for newcomers to Racket. You can also
see the new version here:
This is great.
Heres a few comments that come to mind:
At the end of part 12.6.3 of the docs in
http://docs.racket-lang.org/reference/reader.html, it gives some examples
Examples:
-1
reads equal to
-1
1/2
reads equal to
(/ 1 2)
1.0
reads equal to
(inexact-exact 1)
1+2i
reads equal to
(make-complex 1 2)
1/2+3/4i
reads equal to
On Jul 27, The Configurator wrote:
Shouldn't all the usages of inexact-exact here actually be
exact-inexact ?
Yes, thanks -- fixed in git.
--
((lambda (x) (x x)) (lambda (x) (x x))) Eli Barzilay:
http://barzilay.org/ Maze is Life!
24 matches
Mail list logo
