Re: [racket-dev] gui responsiveness

2014-04-17 Thread Laurent
As a side note, I remember having stumbled on the same issue some while back, and the way I dealt with it was to refresh based on a random outcome. Not clean, but it works pretty well as long as the refresh calls are still close enough. Laurent On Thu, Apr 17, 2014 at 12:11 AM, David Vanderson

Re: [racket-dev] gui responsiveness

2014-04-17 Thread Neil Van Dyke
Matthew Flatt wrote at 04/16/2014 01:56 PM: (set! needed? #t) (queue-callback (lambda () (when needed? (set! needed? #f) (send this refresh))) #f) ; = low priority This is what I'd try first. If it works well

[racket-dev] Fwd: [racket] canonical index of Racket courses? [was: Summer programs learning Racket for a student]

2014-04-17 Thread Matthias Felleisen
Would someone volunteer please to create and maintain such a page for Racket? Thanks -- Matthias Begin forwarded message: From: j...@math.brown.edu Subject: [racket] canonical index of Racket courses? [was: Summer programs learning Racket for a student] Date: April 16, 2014

[racket-dev] class implementation and make-primitive-class

2014-04-17 Thread dfeltey
For a course project I've been working on adding generators to contracts for use with contract-random-generate, and I've been trying to construct classes and objects from simple object/c contracts. When trying to find a way to functionally create a class at runtime, I came across the

Re: [racket-dev] class implementation and make-primitive-class

2014-04-17 Thread Matthew Flatt
The `make-primitive-class` function is a leftover from pre-v5.1 days, where the problem was to turn a C++ object into a Racket object. I'm not surprised that it has rotted away, it should be removed entirely, and I doubt that it's what you would want even if it worked. At Thu, 17 Apr 2014

Re: [racket-dev] class implementation and make-primitive-class

2014-04-17 Thread Neil Van Dyke
For purposes of your course project, couldn't you make your own class-instance object system, atop structs or hashes, that gives you whatever dynamic programming features you want? It's very-very easy to do a basic one (with single inheritance and single dispatch), until you get into speed

Re: [racket-dev] class implementation and make-primitive-class

2014-04-17 Thread Daniel Feltey
That wouldn't work for this project because I need to be able to generate an object that satisfies a given Racket contract and can be passed to user functions that expect such an object so I need to use Racket's class system. I have a working prototype that builds class syntax then calls

[racket-dev] Pre-Release Checklist for v6.0.1

2014-04-17 Thread Ryan Culpepper
Checklist items for the v6.0.1 release (using the v6.0.0.900 release candidate build) Search for your name to find relevant items, reply when you finish an item (please indicate which item/s is/are done). Also, if you have any commits that should have been picked, make sure that the changes

[racket-dev] Adding flvector to match

2014-04-17 Thread Neil Toronto
It would be really handy for me right now to be able to match on flvectors, and I think it's useful enough for minimal Racket. I've already tried this option: 1. Export flvector as a match expander from racket/flonum but racket/match depends on racket/flonum somehow. So I looked through the

Re: [racket-dev] Adding flvector to match

2014-04-17 Thread Sam Tobin-Hochstadt
I think you should do 2': Change racket/match to recognize patterns with #'flvector heads -- ie, use the binding for flvector from `racket/flonum` to determine if something matches. The use of symbolic names in match, rather than bindings, is a leftover rather than something we should keep adding

Re: [racket-dev] Adding flvector to match

2014-04-17 Thread Neil Toronto
Great idea! Neil ⊥ On 04/17/2014 05:00 PM, Sam Tobin-Hochstadt wrote: I think you should do 2': Change racket/match to recognize patterns with #'flvector heads -- ie, use the binding for flvector from `racket/flonum` to determine if something matches. The use of symbolic names in match,

Re: [racket-dev] Pre-Release Checklist for v6.0.1

2014-04-17 Thread David Van Horn
On 4/17/14, 6:44 PM, Ryan Culpepper wrote: * David Van Horn dvanh...@ccs.neu.edu - EoPL Tests Done. _ Racket Developers list: http://lists.racket-lang.org/dev

Re: [racket-dev] Using `git submodule` vs. `git pull --ff-only upstream master`

2014-04-17 Thread Greg Hendershott
For whoever else might find this useful building on OS X. Building HEAD today I got this new error: raco setup: --- creating launchers --- raco setup: launcher: console-bin/raco raco setup: --- installing man pages --- raco setup: --- installing collections --- raco setup: --- post-installing

Re: [racket-dev] Using `git submodule` vs. `git pull --ff-only upstream master`

2014-04-17 Thread Spencer Florence
stale git submodules show up on a status. What I've found helpful is to add a bit in my prompt that tells me if the current git repository has a non up to date status (And the current branch). If you're running Zsh this is a good place to start for that: git_prompt_info() { ref=$(git

Re: [racket-dev] Pre-Release Checklist for v6.0.1

2014-04-17 Thread Matthew Flatt
At Thu, 17 Apr 2014 18:44:20 -0400, Ryan Culpepper wrote: * Matthew Flatt mfl...@cs.utah.edu - Racket Tests - Languages Tests - GRacket Tests (Also check that `gracket -z' and `gracket-text' still works in Windows and Mac OS X) - mzc --exe tests - .plt-packing Tests

Re: [racket-dev] Using `git submodule` vs. `git pull --ff-only upstream master`

2014-04-17 Thread Greg Hendershott
Yes. FWIW I do: function parse_git_dirty() { [[ $(git status 2 /dev/null | tail -n1) != *working directory clean* ]] echo * } function parse_git_branch() { git branch --no-color 2 /dev/null | sed -e '/^[^*]/d' -e s/* \(.*\)/\1$(parse_git_dirty)/ } Which goes into the the end of:

Re: [racket-dev] Pre-Release Checklist for v6.0.1

2014-04-17 Thread Robby Findler
On Thu, Apr 17, 2014 at 5:44 PM, Ryan Culpepper ry...@ccs.neu.edu wrote: * Robby Findler ro...@eecs.northwestern.edu - DrRacket Tests All but populate-compiled.rkt, which uncovered the need for commit fe2c796c41154. Can you please include it in the release branch? - Framework Tests -

Re: [racket-dev] Pre-Release Checklist for v6.0.1

2014-04-17 Thread Jon Rafkind
* Jon Rafkind rafk...@cs.utah.edu Release tests for (one of the) linux releases: - Test that the `racket' and `racket-textual' source releases compile fine (note that they're still called `plt' and `mz' at this stage). - Test that the binary installers for both work, try each