I use parameters a lot when designing a library which provides customizable
behaviors.
Instead of having an (init) procedure in which users can setup stuff for
the library, I provide parameters, which are way more flexible.
For example, I'm designing an emulator in which you can have memory
My hot take is parameters and threads are equivalent-ish to
environment variables and processes -- with similar behavior, pros,
and cons.
The `parameterize` form ~= the env save/set/restore of fork without
the overhead of actually launching a process?
~~~
I've been doing a lot of work on
If you're a Racketeer on a GNU/Linux, BSD, Solaris, etc., and like to do
cool nerdy things like try a custom tiling window manager... you might
want to join me in using Laurent Orseau's RWind window manager, which is
written in Racket.
You can install RWind from the Racket package repository,
make a keyword useable as the parameter-expr in a parameterize expression.
for example, If I need a similar #:unless cause for a bunch of for
expressions
It's not a current issue, but would be good to have in the toolbox for
next time.
On Thursday, August 2, 2018 at 8:25:31 PM UTC-4,
What do you think about this simple convention for multiple installed
Racket versions on a Unix-ish OS, when key parts of userland are
implemented in Racket, and when you also might be working on custom
versions of core Racket itself on the device while you are using the device?
* Directory
Hello everyone,
Thanks for all the responses, they have been very clarifying.
I'd like to add the following for your consideration of using parameters.
When using the plot package, I really like to setup common parameters using
parameterize and then tweak others using the named parameters in
Maybe this isn’t really a direct response to the direction this thread
has taken, but given the question proposed in the original message, I
think it’s relevant to share a particular design pattern for parameters
that seems to work well. In a number of different APIs provided by
Racket, a
On 8/3/2018 11:52 AM, Sanjeev Sharma wrote:
make a keyword useable as the parameter-expr in a parameterize
expression.
for example, If I need a similar #:unless cause for a bunch of for
expressions
It's not a current issue, but would be good to have in the toolbox
for next time.
If I'm
I'm still not sure that I understand what the original questioner is trying
to do. It might help to see an example in code to be clear that we're all
talking about the same thing.
A few points for the list, though:
On Fri, Aug 3, 2018 at 10:53 PM, George Neuner wrote:
> (define mykey
9 matches
Mail list logo