I hear you. If I used any parameters except the plot ones, I'd have a
problem, and write macros as you suggest. (Or save and restore the
exceptions instead.) For now, I'm trying Matthew's suggestion, and using
this:
(define (parameterize-procedure t)
(define parameterization (current
On Fri, Sep 9, 2011 at 3:36 PM, Carl Eastlund wrote:
> On Fri, Sep 9, 2011 at 3:30 PM, Neil Van Dyke wrote:
>>
>> I would like for the *displayed* form in the formatted documentation to be
>> ":MAJOR:MINOR", and the form that Scribble uses for "require" to be
>> ":MAJOR:=MINOR".
>
> Aha. Yes, th
On Tue, Oct 18, 2011 at 1:09 PM, Robby Findler
wrote:
>
> As to why requiring racket/base causes an error: I believe that what
> is happneing is you are getting the racket/base version of require for
> the second require (it is shadowing the mzscheme-based require that
> #lang eopl introduces) and
There are parameterizations, but they pick up all parameters and that
may make other things go wrong (or you have to be more careful how you
look up your parameter values but I think you might object to that on
similar grounds to the below).
I would probably use the solution you have below, but wi
It wouldn't work well to have a "plot context" object, perhaps stored in
"current-plot-context" parameter?
--
http://www.neilvandyke.org/
_
For list-related administrative tasks:
http://lists.racket-lang.org/listinfo/users
At Tue, 18 Oct 2011 13:40:12 -0600, Neil Toronto wrote:
> Executive summary: Is there a good way to save a large set of parameter
> values, or *all* the parameter values, and then restore them when needed?
`current-parameterization' and `call-with-parameterization'?
_
At Tue, 18 Oct 2011 13:40:12 -0600,
Neil Toronto wrote:
> Executive summary: Is there a good way to save a large set of parameter
> values, or *all* the parameter values, and then restore them when needed?
Would parameterizations help?
Vincent
_
Executive summary: Is there a good way to save a large set of parameter
values, or *all* the parameter values, and then restore them when needed?
In the new PLoT, much of a plot's appearance is controlled by
parameters. I use parameters because there are so many
appearance-controlling values t
On Tue, Oct 18, 2011 at 12:00 PM, Marco Morazan wrote:
> On Tue, Oct 18, 2011 at 11:28 AM, Eli Barzilay wrote:
>>
>> `build-vector' is in the core `racket/base'. To require just it in
>> the `eopl' language, you need to use the "raw" require forms, because
>> it's based on mzscheme:
>>
>> #lang
On Tue, Oct 18, 2011 at 11:28 AM, Eli Barzilay wrote:
>
> `build-vector' is in the core `racket/base'. To require just it in
> the `eopl' language, you need to use the "raw" require forms, because
> it's based on mzscheme:
>
> #lang eopl
> (require (only racket/base build-vector))
> (require "
A few minutes ago, Marco Morazan wrote:
> Here is my experiment:
>
> green.rkt:
> (module green eopl
> (provide numfuncts)
> (provide dummy)
> (define numfuncts -1)
> (define dummy 10))
>
> File1.rkt:
> #lang eopl
> (require racket/vector)
> (require "green.rkt")
>
> (define numfs numfun
Just now, Eli Barzilay wrote:
> A few minutes ago, Marco Morazan wrote:
> > Throws the following error: #%module-begin: bad syntax in:
> > (#%module-begin (#%require racket/base) (#%require "green.rkt")
> > (define-values (numfs) numfuncts) (define-values (crazy) (lambda
> > (x) (#%app * dummy x)))
Here is my experiment:
green.rkt:
(module green eopl
(provide numfuncts)
(provide dummy)
(define numfuncts -1)
(define dummy 10))
File1.rkt:
#lang eopl
(require racket/vector)
(require "green.rkt")
(define numfs numfuncts)
(define (crazy x) (* dummy x))
(define (f x) (build-vector 10 (la
10 minutes ago, Robby Findler wrote:
> [adding back the list again].
>
> I'm not sure what is going on exactly, but it looks like it might be
> a bad interaction between racket/base and eopl. Here's a smaller
> pair of files that illustrates the problem:
>
> green.rkt:
> (module green eopl)
>
>
[adding back the list again].
I'm not sure what is going on exactly, but it looks like it might be a
bad interaction between racket/base and eopl. Here's a smaller pair of
files that illustrates the problem:
green.rkt:
(module green eopl)
Another file (any file):
#lang eopl
(require racket/base
This sounds like a bug in #lang eopl (at least in the error message
reporting), but this program is still not enough to actually reproduce
the problem. For me, for example, this works fine:
#lang eopl
(require racket/base)
(require racket/list)
So it isn't just having two requires.
Robby
On Tue
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/18/11 14:14, Matthew Flatt wrote:
> Just to be clear (hopefully!), the direct `on-focus' call that I
> described happens only at the window layer, while there is an
> explicit downward chaining as you described at the
> `editor<%>'/`snip%' layer
I think we'll probably need some more context to say what is going on.
Can you post a complete program that has that symptom?
Robby
On Tue, Oct 18, 2011 at 8:16 AM, Marco Morazan wrote:
> I'm at a loss with this error. Can anyone provide some insight?
>
> So, I have the following (in a file name
I'm at a loss with this error. Can anyone provide some insight?
So, I have the following (in a file named green.rkt):
(module green ...
(provide expr)
(provide program)
...
;(provide num-functs)
)
In a different file I have:
(require "green.rkt")
If as above, I comment out (provide
At Tue, 18 Oct 2011 10:53:36 +0200, Marijn wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 10/18/11 01:39, Matthew Flatt wrote:
> > At Mon, 17 Oct 2011 16:33:26 +0200, Marijn wrote:
> >> Is it correct, that when you click the title bar of a window
> >> frame to select it, this caus
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/18/11 01:39, Matthew Flatt wrote:
> At Mon, 17 Oct 2011 16:33:26 +0200, Marijn wrote:
>> Is it correct, that when you click the title bar of a window
>> frame to select it, this causes the on-focus method of that frame
>> to be called.
>
> That'
21 matches
Mail list logo
