Re: [racket-dev] Attempted clarification for planet2 docs

2013-01-03 Thread John Clements
On Jan 3, 2013, at 6:36 AM, Matthew Flatt wrote: > I went to fix a typo (`tech' to `racket') and ended up moving and > tweaking the text. I hope the changes are ok. > > I like the way the example distinguishes the package name, collection > name, and library name, and so I added a sentence to ex

Re: [racket-dev] Attempted clarification for planet2 docs

2013-01-03 Thread Jay McCarthy
Looks great to me. On Thu, Jan 3, 2013 at 7:36 AM, Matthew Flatt wrote: > I went to fix a typo (`tech' to `racket') and ended up moving and > tweaking the text. I hope the changes are ok. > > I like the way the example distinguishes the package name, collection > name, and library name, and so

Re: [racket-dev] Attempted clarification for planet2 docs

2013-01-03 Thread Matthew Flatt
I went to fix a typo (`tech' to `racket') and ended up moving and tweaking the text. I hope the changes are ok. I like the way the example distinguishes the package name, collection name, and library name, and so I added a sentence to explicitly note that `require' lines don't refer to packages. T

Re: [racket-dev] Attempted clarification for planet2 docs

2013-01-02 Thread John Clements
On Jan 2, 2013, at 1:03 PM, Jay McCarthy wrote: > Sounds fine. John's original language seems like that and is good to me. Pushed, thanks. John > > > On Wed, Jan 2, 2013 at 1:59 PM, Carl Eastlund wrote: > It doesn't need to be phrased as a comparison to Planet1, but it can be given > as a

Re: [racket-dev] Attempted clarification for planet2 docs

2013-01-02 Thread Jay McCarthy
Sounds fine. John's original language seems like that and is good to me. On Wed, Jan 2, 2013 at 1:59 PM, Carl Eastlund wrote: > It doesn't need to be phrased as a comparison to Planet1, but it can be > given as a reassurance that this "package system" thingy does not add any > baggage to requir

Re: [racket-dev] Attempted clarification for planet2 docs

2013-01-02 Thread Carl Eastlund
It doesn't need to be phrased as a comparison to Planet1, but it can be given as a reassurance that this "package system" thingy does not add any baggage to require lines. Carl Eastlund On Wed, Jan 2, 2013 at 3:49 PM, Jay McCarthy wrote: > I agree in that context that it is useful as a part of

Re: [racket-dev] Attempted clarification for planet2 docs

2013-01-02 Thread Jay McCarthy
I agree in that context that it is useful as a part of the "What's different about Planet 2?" And it's there (question 6). But, in the context of a new Racket user learning about packages, I don't see a reason to add the baggage of how it's different than some system they've never used. Jay On

Re: [racket-dev] Attempted clarification for planet2 docs

2013-01-02 Thread Carl Eastlund
There _is_ reason to think these modules are different, because they were different in Planet1. I've had to remind myself several times that Planet2 packages don't have special require forms, and that's just during discussions -- I haven't even been writing code with them yet. Clarifying that Pla

Re: [racket-dev] Attempted clarification for planet2 docs

2013-01-02 Thread Jay McCarthy
The documentation already says "A package is a set of modules for some number of collections." And there's no reason to think that these modules are different from other modules, so I don't see why we need to point out that they are required like all other modules are. If you think it's very confu

[racket-dev] Attempted clarification for planet2 docs

2013-01-02 Thread John Clements
As I was trying to assembly my first planet2 package, I found myself wondering how exactly to 'require' modules associated with planet2 packages. My initial assumption (require them like any other collection containing modules) turned out to be correct, but there was a period when I doubted this