Re: [racket] #lang racket vs. racket/base

2014-02-26 Thread Yuhao Dong
> My impression is that `raco exe` predates the rise of "scripting > languages" like Python and Ruby, in which it's common to tell users, > "Make sure you have version X of Python or Ruby, then install my app". I would say that "raco exe" is rather useless, and I don't see the point really. It st

Re: [racket] #lang racket vs. racket/base

2014-02-14 Thread Manfred Lotz
On Thu, 13 Feb 2014 16:12:44 -0600 Robby Findler wrote: > Oh, apparently the difference you're seeing is indeed racket/match. I > see that the contract system is already pulled in with those requires > -- it is bigger than racket/match. (You can see what libraries are > indirectly loaded by using

Re: [racket] #lang racket vs. racket/base

2014-02-13 Thread Robby Findler
Oh, apparently the difference you're seeing is indeed racket/match. I see that the contract system is already pulled in with those requires -- it is bigger than racket/match. (You can see what libraries are indirectly loaded by using DrRacket's View|Show Module Browser.) Anyway, in the current git

Re: [racket] #lang racket vs. racket/base

2014-02-13 Thread Manfred Lotz
On Wed, 12 Feb 2014 09:55:16 -0600 Robby Findler wrote: > Looks like most of the size increase from racket/date is that you're > pulling in the contract system. No quite sure about this. I have #lang racket/base (require racket/cmdline racket/string racket/format

Re: [racket] #lang racket vs. racket/base

2014-02-12 Thread Robby Findler
Looks like most of the size increase from racket/date is that you're pulling in the contract system. Still, there was some dead code in that file whose removal let me remove a few requires from it (eliminating a dependency on racket/match, since none of the things racket/date requires require it).

Re: [racket] #lang racket vs. racket/base

2014-02-12 Thread Manfred Lotz
On Wed, 12 Feb 2014 06:07:17 -0700 Matthew Flatt wrote: > At Wed, 12 Feb 2014 06:02:30 +0100, Manfred Lotz wrote: > > I just read Neil van Dyke's statement: > > > > < "#lang racket" is for demos, IMHO; I *always* use "#lang > > racket/base" < for any code that's not a demo. > > > > Question: Wh

Re: [racket] #lang racket vs. racket/base

2014-02-12 Thread Greg Hendershott
Although I could be mistaken about any/all of the following, I'll go out on a limb -- and once there, jump up and down. > < "#lang racket" is for demos, IMHO; I *always* use "#lang racket/base" > < for any code that's not a demo. > > Question: What are the advantages of doing requires explicitly?

Re: [racket] #lang racket vs. racket/base

2014-02-12 Thread Matthew Flatt
At Wed, 12 Feb 2014 06:02:30 +0100, Manfred Lotz wrote: > I just read Neil van Dyke's statement: > > < "#lang racket" is for demos, IMHO; I *always* use "#lang racket/base" > < for any code that's not a demo. > > Question: What are the advantages of doing requires explicitly? > > In a program o

[racket] #lang racket vs. racket/base

2014-02-11 Thread Manfred Lotz
I just read Neil van Dyke's statement: < "#lang racket" is for demos, IMHO; I *always* use "#lang racket/base" < for any code that's not a demo. Question: What are the advantages of doing requires explicitly? In a program of mine I changed #lang racket to #lang racket/base and added: (require