Re: [racket-dev] problem with require and frtime

2012-01-19 Thread Marijn
On 18-01-12 17:47, Matthew Flatt wrote: At Wed, 18 Jan 2012 12:02:10 +0100, Marijn wrote: I would expect both forms to work. This is a reduction of a different problem possibly caused by these issues here. So I tried to cut down my program to a reasonably sized test-case which is attached to

Re: [racket-dev] problem with require and frtime

2012-01-19 Thread Matthew Flatt
The `frtime' language exports an `=' that isn't the same as `=' in `racket', so that's why the pattern doesn't match. (This seems like a further weakness of the `frtime' docs to specify the exports precisely.) You could avoid bound names like `=' as literals in the macro. Normally, it works best

Re: [racket-dev] problem with require and frtime

2012-01-19 Thread Matthias Felleisen
Greg, how difficult would it be to migrate frtime to #lang racket? -- Matthias On Jan 19, 2012, at 8:13 AM, Matthew Flatt wrote: The `frtime' language exports an `=' that isn't the same as `=' in `racket', so that's why the pattern doesn't match. (This seems like a further weakness of the

Re: [racket-dev] problem with require and frtime

2012-01-19 Thread Matthew Flatt
(Just to be clear, that wouldn't solve the problem this time. The `=' from `scheme' and `racket' are the same, but `frtime' has its own `='.) At Thu, 19 Jan 2012 08:19:59 -0500, Matthias Felleisen wrote: Greg, how difficult would it be to migrate frtime to #lang racket? -- Matthias On

Re: [racket-dev] problem with require and frtime

2012-01-19 Thread Gregory Cooper
I assume it wouldn't be too difficult, and that it's worth doing even if it doesn't solve this particular problem. Can someone grant me commit privileges? On Thu, Jan 19, 2012 at 5:18 AM, Matthew Flatt mfl...@cs.utah.edu wrote: (Just to be clear, that wouldn't solve the problem this time. The

Re: [racket-dev] problem with require and frtime

2012-01-18 Thread Matthew Flatt
At Wed, 18 Jan 2012 12:02:10 +0100, Marijn wrote: the following fragment: #lang frtime (require (only-in srfi/1 every)) leads to ```only-in: bad module path in: (only-in srfi/1 every)''' error. The `frtime' language builds on (the older) `scheme' language instead of `racket', so