Re: [racket-dev] Bug? identifier `make-Int' not included in nested require spec.

2010-10-04 Thread Hari Prashanth
Ok it does work... Thanks Hari - Original Message - From: "Sam Tobin-Hochstadt" To: "Hari Prashanth" Cc: "dev" Sent: Monday, October 4, 2010 7:16:26 PM GMT -05:00 US/Canada Eastern Subject: Re: [racket-dev] Bug? identifier `make-Int' not included in nested require spec. This is a kno

Re: [racket-dev] Bug? identifier `make-Int' not included in nested require spec.

2010-10-04 Thread Sam Tobin-Hochstadt
This is a known bug with the interaction of `struct' and `require/typed'. `define-struct' should work here. On Mon, Oct 4, 2010 at 7:11 PM, Hari Prashanth wrote: > Am I doing some thing wrong or is it a bug? > > #lang racket/load > > (module UNTYPED racket/base >  (struct Int (elem)) > >  (provi

[racket-dev] Bug? identifier `make-Int' not included in nested require spec.

2010-10-04 Thread Hari Prashanth
Am I doing some thing wrong or is it a bug? #lang racket/load (module UNTYPED racket/base (struct Int (elem)) (provide (struct-out Int))) (module TYPED typed/racket (require/typed 'UNTYPED [struct Int ([elem : Integer])])) I get the following error only-in: identifie

Re: [racket-dev] #:namespace

2010-10-04 Thread Jay McCarthy
On Mon, Oct 4, 2010 at 8:17 AM, Eli Barzilay wrote: > 40 minutes ago, Jay McCarthy wrote: >> >> [...] I removed the namespace argument and the request handler >> closure is simply evaluated in the namespace it came from. > > The relevant piece of code: > >  #lang racket/base >  (require ... handin

Re: [racket-dev] #:namespace

2010-10-04 Thread Jay McCarthy
I didn't realize the handin server used it when I removed it. It definitely doesn't need it. The #:namespace argument made it so the closure given as the request handler was called in a different namespace than it was evaluated in, causing a reinstantiation of the module and other weirdness. For

Re: [racket-dev] #:namespace

2010-10-04 Thread Eli Barzilay
40 minutes ago, Jay McCarthy wrote: > > [...] I removed the namespace argument and the request handler > closure is simply evaluated in the namespace it came from. The relevant piece of code: #lang racket/base (require ... handin-server/private/logger ...) (provide run) (define (run)

Re: [racket-dev] thoughts?

2010-10-04 Thread Eli Barzilay
As briefly as I can: 0. I've seen one very big OCaml program. One thing that surprised me is when one day I wanted to follow how a specific piece of functionality was done. I grabbed the relevant file, then the file that it required and so on -- that specific piece of functionality was spread ov

Re: [racket-dev] #:namespace

2010-10-04 Thread Jay McCarthy
That's not how the #:namespace argument ever worked. #:namespace takes a list of module names that are shared between the server and the servlets. In the case of the command-line tool, this is effectively a way to make some modules shared between different servlets, through the common party of th

[racket-dev] thoughts?

2010-10-04 Thread Matthias Felleisen
A recent message on -edu reminded me of a discussion I started with Robby at ICFP and never continued. When you read an ML program, you read the signatures of the modules; you may read the functor compositions, if any. And then you have a pretty good idea of which modules takes on which respo

Re: [racket-dev] #:namespace

2010-10-04 Thread Robby Findler
It sounds like one could work around this by taking whatever was passed to #:namespace and making the servlets move over to that namespace, at least. Robby On Mon, Oct 4, 2010 at 8:28 AM, Jay McCarthy wrote: > I didn't realize the handin server used it when I removed it. > > It definitely doesn'