Ryan, thank you very much for refocusing the discussion
about testing on the essence and away from the superficial
syntactic issues. Syntax, as we all know, is just a macro
[which some people may get backwards and conclude that
testing is just a macro. Nothing could be further from
the truth,
Three minutes ago, Matthias Felleisen wrote:
Ryan, thank you very much for refocusing the discussion about
testing on the essence and away from the superficial syntactic
issues.
These are two completely unrelated issues, very concretely: one is the
representation layer that would allow
50 minutes ago, Ryan Culpepper wrote:
On 02/15/2011 07:28 AM, Eli Barzilay wrote:
And finaly, there's the litmus test for existing code:
* Ryan: is something like this enough to implement the GUI layer?
Not well, I think. The Test-Result type in Noel's racktest code is
too simple and
To anyone who commits code to the plt repository: please be careful
when you commit code from elsewhere into the tree, to avoid future
problems wrt copyrights.
--
((lambda (x) (x x)) (lambda (x) (x x))) Eli Barzilay:
http://barzilay.org/
There are problematic latex files in collects/scribble/jfp/jfp.cls
and sigplan/sigplanconf.cls. The latter has a copyright line but no
license specified, and the first is much worse, since it explicitly
states:
%% This software may only be used in the preparation of journal
%% articles or
Can we pull the Wine trick of having a script that runs during
compilation that downloads the file from a well-known location?
Jay
2011/2/18 Eli Barzilay e...@barzilay.org:
There are problematic latex files in collects/scribble/jfp/jfp.cls
and sigplan/sigplanconf.cls. The latter has a
About a minute ago, Jay McCarthy wrote:
Can we pull the Wine trick of having a script that runs during
compilation that downloads the file from a well-known location?
That sounds like a headache... and won't help with distribution (which
will have the compiled file). Probably easier to do it
On 02/18/2011 07:30 AM, Eli Barzilay wrote:
50 minutes ago, Ryan Culpepper wrote:
On 02/15/2011 07:28 AM, Eli Barzilay wrote:
And finaly, there's the litmus test for existing code:
* Ryan: is something like this enough to implement the GUI layer?
Not well, I think. The Test-Result type in
You may recall from the meeting over the summer that I promised a
packaging Christmas present to Racket. I'm over a month late, but here
it is:
http://faculty.cs.byu.edu/~jay/tmp/pkgs/spec.html
I lay out some goals for the new packaging system and make a concrete proposal.
Please share your
Minor comment: why encourage names like libgtk and libgtk2 instead
of a major and minor version number (ala PLaneT)? Don't we want those
two libraries to be associated somehow (at least loosely)?
Also, it also isn't clear which of the complaints with PLaneT you're
actually dealing with. I don't
I read your contribution with great interest. One problem that is not
addressed, as far as I have seen, is that any idiot, like me, can install
his/her contributions (modules/collections/packages or whatever)
For a simple windows 7 user as I it is rather difficult to use command line
Jay -
1. Thanks for having this out - this is a great start and a very
important problem to solve
2. Is it correct that *heap* maps to the account name in planet? Such as
jaymccarthy, schematics, or bzlib?
There is always tension between the naming by capability or author in
One more comment: one of PLaneT's design goals what that if you have a
working system and you install a new planet package, then you didn't
break any of the working parts from before. The new system doesn't
seem to have that as a design goal anymore (I noticed automatic
upgrades and freezing being
Sorry.
I think we should remove the .cls files and say that users have to put
them somewhere that Latex will find them (e.g., set `TEXINPUTS').
_
For list-related administrative tasks:
http://lists.racket-lang.org/listinfo/dev
It wouldn't hurt to include a little script that downloads the correct
versions of the files from racket-lang.org somewhere and puts them
where they are currently, tho, no?
Robby
On Fri, Feb 18, 2011 at 7:56 PM, Matthew Flatt mfl...@cs.utah.edu wrote:
Sorry.
I think we should remove the .cls
On Fri, Feb 18, 2011 at 9:42 PM, Robby Findler
ro...@eecs.northwestern.edu wrote:
It wouldn't hurt to include a little script that downloads the correct
versions of the files from racket-lang.org somewhere and puts them
where they are currently, tho, no?
At least for the JFP file, it's pretty
On Fri, Feb 18, 2011 at 8:17 PM, Robby Findler
ro...@eecs.northwestern.edu wrote:
One more comment: one of PLaneT's design goals what that if you have a
working system and you install a new planet package, then you didn't
break any of the working parts from before. The new system doesn't
seem
If you do this, please at least make installing the full documentation an
option. Not everyone can ensure that they will always be online when working
with Racket.
Sent from my iPad
On Feb 18, 2011, at 5:56 PM, dev-requ...@racket-lang.org wrote:
4. Agreed that the installation/compilation
18 matches
Mail list logo
