headers
Robby Findler | 1 Apr 2012 05:48
Gravatar

Re: [plt] Push #24496: master branch updated

On Sat, Mar 31, 2012 at 4:49 PM, Eli Barzilay <eli <at> barzilay.org> wrote:
> Yesterday, Robby Findler wrote:
>> On Fri, Mar 30, 2012 at 9:28 AM, Eli Barzilay <eli <at> barzilay.org> wrote:
>> > It's cute that it's running `main' and `test' -- but I can see
>> > uses for disabling either, or wanting to run something
>> > else.  Maybe turn it from an option to control running `test' to a
>> > field with names of submodules that should be run instead?
>>
>> Okay, I've done that (using a popup menu).
>
> Very nice.  Two minor points: the first thing I did was to add a
> "foo", but that just adds the option and doesn't select it; the second
> one is that once it's added, there's no way to remove it.  Both not
> too important.

Thanks. I've fixed the former (I meant to do that, actually, but
forgot), and the second I intentionally left out for now, since it
seems to clutter the GUI without too much value.

>
>> > (Even cuter would be to add some dropdown menu with checkboxes for
>> > each of the submodules that are found in the current definitions.)
>>
>> In principle, I could use the online expansion stuff to do this.
>> Maybe some day.
>
> Something that I thought about earlier is that choosing a new
> submodule name would actually run it -- but that has a problem since
> it doesn't correspond to the main run button.  Another possibility: if
> you find submodules in the definitions, you show a button for each
(Continue reading)

Permalink | Reply | 0 comments |
headers
Ryan Culpepper | 2 Apr 2012 21:00
Picon
Favicon

Release for v5.3 is about to begin

The release process for v5.3 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.
--

-- 
Ryan Culpepper
_________________________
  Racket Developers list:
  http://lists.racket-lang.org/dev
Permalink | Reply | 2 comments |
headers
Danny Yoo | 2 Apr 2012 21:26
Gravatar

Re: Release for v5.3 is about to begin



On Monday, April 2, 2012, Ryan Culpepper wrote:
The release process for v5.3 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.


Is submodule support going to be a part of 5.3? 
_________________________
  Racket Developers list:
  http://lists.racket-lang.org/dev
Permalink | Reply | 1 comment |
headers
Ryan Culpepper | 2 Apr 2012 22:28
Picon
Favicon

Re: Release for v5.3 is about to begin

On 04/02/2012 01:26 PM, Danny Yoo wrote:
>
>
> On Monday, April 2, 2012, Ryan Culpepper wrote:
>
>     The release process for v5.3 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.
>
> Is submodule support going to be a part of 5.3?

Yes.

Ryan
_________________________
  Racket Developers list:
  http://lists.racket-lang.org/dev
Permalink | Reply | 0 comments |
headers
Matthew Flatt | 2 Apr 2012 23:34
Picon
Favicon
Gravatar

Re: question on scribble/eval's do-plain-eval on bytes and strings

At Thu, 29 Mar 2012 11:25:37 -0400, Danny Yoo wrote:
> I've traced the source of this "begin" down to the do-plain-eval
> function in scribble/eval.rkt.
> 
>              ;; within do-plain-eval:
>              (cond [(syntax? s)
>                     (syntax-case s (module)
>                       [(module . _rest) (syntax->datum s)]
>                       [_else s])]
>                    [(bytes? s) `(begin ,s)]
>                    [(string? s) `(begin ,s)]
>                    [else s]))))
> 
> I assume it's trying to make sure than an evaluator defined by
> racket/sandbox doesn't treat it as program source rather than as data,
> since the sandbox treats strings and bytes in a special way.
> 
> Would it be equivalent behavior to turn the datum into a syntax object
> instead?  That is:
> 
>              ;; within do-plain-eval:
>              (cond [(syntax? s)
>                     (syntax-case s (module)
>                       [(module . _rest) (syntax->datum s)]
>                       [_else s])]
>                    [(bytes? s) (datum->syntax #f s)]
>                    [(string? s) (datum->syntax #f s)]
>                    [else s]))))
> 
> If this looks right, I can send as a patch.

I'm not completely certain, but that looks ok to me.

_________________________
  Racket Developers list:
  http://lists.racket-lang.org/dev
Permalink | Reply | 1 comment |
headers
Matthew Flatt | 2 Apr 2012 23:36
Picon
Favicon
Gravatar

Re: confusing doc for "in-directory"

I pushed a doc update, but forgot to reply. The documentation now
clarifies that `in-directory' recursively traverses subdirectories, and
it suggests `directory-list' for just the immediate content of a
directory.

At Wed, 28 Mar 2012 17:21:57 -0700, Eric Hanchrow wrote:
> http://docs.racket-lang.org/reference/sequences.html?q=read-directory#(def._((li
> b._racket/private/base..rkt)._in-directory))
>  says that the form will ``Return a sequence that produces all of the
> paths for files, directories, and links with dir. ''  That's
> ungrammatical, but worse, it gave me no clue that it will return all
> files _at any depth_, similar to the Unix comand "find dir".  I'd
> expected it to return only immediate children of dir, similarly to
> "find dir -mindepth 1 -maxdepth 1"; I was surprised when (in-directory
> "/tmp") complained about not being able to open
> "/tmp/some-subdirectory/" due to permissions problems.
> _________________________
>   Racket Developers list:
>   http://lists.racket-lang.org/dev
_________________________
  Racket Developers list:
  http://lists.racket-lang.org/dev
Permalink | Reply | 0 comments |
headers
Danny Yoo | 2 Apr 2012 23:40
Gravatar

Re: question on scribble/eval's do-plain-eval on bytes and strings

>> Would it be equivalent behavior to turn the datum into a syntax object
>> instead?  That is:
>>
>>              ;; within do-plain-eval:
>>              (cond [(syntax? s)
>>                     (syntax-case s (module)
>>                       [(module . _rest) (syntax->datum s)]
>>                       [_else s])]
>>                    [(bytes? s) (datum->syntax #f s)]
>>                    [(string? s) (datum->syntax #f s)]
>>                    [else s]))))
>>
>> If this looks right, I can send as a patch.
>
> I'm not completely certain, but that looks ok to me.

Ok, good.  I ran into this when starting to scribble my April Fools
joke, as Arctangent doesn't provide a "begin" form.  I'll send a patch
shortly.

I'm running into another issue with  <at> interactions where it does not
preserve the square-bracketness of an expression before passing it to
the evaluator.  Fixing the bug looks more involved.  I'll send a bug
report.

_________________________
  Racket Developers list:
  http://lists.racket-lang.org/dev
Permalink | Reply | 0 comments |
headers
Nadeem Abdul Hamid | 3 Apr 2012 02:09
Picon
Favicon

provide specs in eopl in repository use (all-defined-out) instead of (all-defined)

How come when building Racket from the latest source of the repository
(at least as of 3 days ago), #lang eopl doesn't recognize
(all-defined) as a valid provide spec and wants (all-defined-out)
instead?
--- nadeem
_________________________
  Racket Developers list:
  http://lists.racket-lang.org/dev
Permalink | Reply | 3 comments |
headers
Robby Findler | 3 Apr 2012 02:22
Gravatar

Re: provide specs in eopl in repository use (all-defined-out) instead of (all-defined)

Because it was changed to be based on "#lang racket" instead of the
(old) "#lang mzscheme" not too long ago. I think there was a post here
(or on the users's list) about this, but I'm not sure that this
particular point was mentioned there, so I can see how you'd be
surprised.

Is this causing you trouble with classes or similar? Would a "#lang
eopl/mzscheme" or something like that be useful for backwards
compatibility? (You'd still need to use that #lang line, tho, since
the regular eopl language is now changed for good.)

Robby

On Mon, Apr 2, 2012 at 7:09 PM, Nadeem Abdul Hamid <nadeem <at> acm.org> wrote:
> How come when building Racket from the latest source of the repository
> (at least as of 3 days ago), #lang eopl doesn't recognize
> (all-defined) as a valid provide spec and wants (all-defined-out)
> instead?
> --- nadeem
> _________________________
>  Racket Developers list:
>  http://lists.racket-lang.org/dev

_________________________
  Racket Developers list:
  http://lists.racket-lang.org/dev
Permalink | Reply | 2 comments |
headers
Nadeem Abdul Hamid | 3 Apr 2012 02:42
Picon
Favicon

Re: provide specs in eopl in repository use (all-defined-out) instead of (all-defined)

OK, thanks. Just wanted to make sure something wasn't broken. It's
only a minor inconvenience - my students are using the version from
the download page, while I usually use one built from source, but I've
just been using the regular 5.2.1 version to run their programs. In
any event, perhaps the documentation needs to be updated: the entry:
  http://pre.racket-lang.org/docs/html/eopl/index.html#(form._((lib._eopl/eopl..rkt)._provide))
points to the mzscheme version of provide.

--- nadeem

On Mon, Apr 2, 2012 at 8:22 PM, Robby Findler
<robby <at> eecs.northwestern.edu> wrote:
> Because it was changed to be based on "#lang racket" instead of the
> (old) "#lang mzscheme" not too long ago. I think there was a post here
> (or on the users's list) about this, but I'm not sure that this
> particular point was mentioned there, so I can see how you'd be
> surprised.
>
> Is this causing you trouble with classes or similar? Would a "#lang
> eopl/mzscheme" or something like that be useful for backwards
> compatibility? (You'd still need to use that #lang line, tho, since
> the regular eopl language is now changed for good.)
>
> Robby
>
> On Mon, Apr 2, 2012 at 7:09 PM, Nadeem Abdul Hamid <nadeem <at> acm.org> wrote:
>> How come when building Racket from the latest source of the repository
>> (at least as of 3 days ago), #lang eopl doesn't recognize
>> (all-defined) as a valid provide spec and wants (all-defined-out)
>> instead?
>> --- nadeem
>> _________________________
>>  Racket Developers list:
>>  http://lists.racket-lang.org/dev

_________________________
  Racket Developers list:
  http://lists.racket-lang.org/dev
Permalink | Reply | 1 comment |

Gmane