[racket-dev] Release for v6.0 is about to begin

2013-11-04 Thread Ryan Culpepper
The release process for v6.0 will begin in about a week. If you have any new features that you want in and are relatively close to being done, now is a good time to do that. _ Racket Developers list: http://lists.racket-lang.org/dev

[racket-dev] `collection-path' Considered Brittle

2013-11-04 Thread Vincent St-Amour
While looking at Asumu's `raco-find-collection' package, Asumu and I noticed something about the `collection-path' function that made us uncomfortable. `collection-path' returns *a* path where the given collection is located. With the package system, there can now be *multiple* such paths.

Re: [racket-dev] `collection-path' Considered Brittle

2013-11-04 Thread Robby Findler
collection-path is legacy and should generally be removed when you find it (I think I fixed two uses of it Saturday in fact). But hopefully you could use collection-file-path in most cases instead of a collections-path function. Robby On Mon, Nov 4, 2013 at 11:45 AM, Vincent St-Amour

Re: [racket-dev] `collection-path' Considered Brittle

2013-11-04 Thread Asumu Takikawa
On 2013-11-04 11:49:44 -0600, Robby Findler wrote: collection-path is legacy and should generally be removed when you find it (I think I fixed two uses of it Saturday in fact). But hopefully you could use collection-file-path in most cases instead of a collections-path function.

Re: [racket-dev] `collection-path' Considered Brittle

2013-11-04 Thread Vincent St-Amour
At Mon, 4 Nov 2013 11:49:44 -0600, Robby Findler wrote: collection-path is legacy and should generally be removed when you find it (I think I fixed two uses of it Saturday in fact). The documentation does mention that `collection-file-path' is usually preferred, but it doesn't make it clear

Re: [racket-dev] `collection-path' Considered Brittle

2013-11-04 Thread Jay McCarthy
You should check out raco test for collection-paths: https://github.com/plt/racket/blob/master/pkgs/compiler-pkgs/compiler-lib/compiler/commands/test.rkt#L168 On Mon, Nov 4, 2013 at 12:56 PM, Vincent St-Amour stamo...@ccs.neu.edu wrote: At Mon, 4 Nov 2013 11:49:44 -0600, Robby Findler wrote:

Re: [racket-dev] `collection-path' Considered Brittle

2013-11-04 Thread Robby Findler
On Mon, Nov 4, 2013 at 1:56 PM, Vincent St-Amour stamo...@ccs.neu.eduwrote: At Mon, 4 Nov 2013 11:49:44 -0600, Robby Findler wrote: collection-path is legacy and should generally be removed when you find it (I think I fixed two uses of it Saturday in fact). The documentation does mention

[racket-dev] Slideshow package needs more splitting

2013-11-04 Thread J. Ian Johnson
I've been working on a package of different pict transformers/constructors I've made while giving slideshow presentations, with some pain. In particular, slideshow-lib pulls in the gui dependency, making documentation impossible. I had to just copy the code for slide-pict and fast-start from

Re: [racket-dev] Slideshow package needs more splitting

2013-11-04 Thread Robby Findler
I think there might be some collection/pkg confusion here. Are you having trouble with a package level dependency or a collection level one? (The latter is the only kind that can lead to the documentation error you're talking about I believe.) Robby On Mon, Nov 4, 2013 at 4:51 PM, J. Ian

Re: [racket-dev] Slideshow package needs more splitting

2013-11-04 Thread J. Ian Johnson
Mm, I believe it's collection-level. Perhaps if play.rkt were split into anim.rkt and play.rkt, where anim.rkt has all the non-gui code, and play.rkt has the gui code. Requiring slideshow/play in my library caused the doc failure. -Ian - Original Message - From: Robby Findler

Re: [racket-dev] Slideshow package needs more splitting

2013-11-04 Thread Robby Findler
I guess probably everything except play, play-n, and animate-slide could be split out. Would that have helped you? Robby On Mon, Nov 4, 2013 at 5:14 PM, J. Ian Johnson i...@ccs.neu.edu wrote: Mm, I believe it's collection-level. Perhaps if play.rkt were split into anim.rkt and play.rkt,

Re: [racket-dev] Release for v6.0 is about to begin

2013-11-04 Thread WarGrey Gyoudmon Ju
Could you please make the regular expression syntax more elegant? To replace the with // or any other character as its boundary. Here is the example: #px/^\s*\/([^\/])\/\s*$/ === #px@^\s*/([^/])/\s*$@ === #px^\\s*/([^/])/\\s*$ Thank you in advance. On Tue, Nov 5, 2013 at 12:51 AM, Ryan