When I tried to run the first example of the pict3d doc
(require pict3d)
(current-pict3d-legacy? #t)
(sphere origin 1/2)
I get the following error message
get-master-gl-context: could not get at least an OpenGL 30 context (legacy? =
#f)
context...:
/home/csvelayutham/racket/collects/racket
I suppose this is a non-answer, but it shouldn't be hard at all to write a
"with-error-as-exception" form. I generally believe it's idiomatic to
extend the language whenever something inconvenient, or whenever a
boilerplate "design pattern", comes up.
On Fri, Mar 13, 2015 at 4:27 PM, Jack Firth w
I'm using racket/system to make some calls to other processes, which upon
failure write to standard error. What's the proper way to handle this? I've
been using with-output-to-string to get the output, but I don't know how I
can turn an error response from the external system command into something
Sometimes, source locations are missing because the relevant expression
or definition was macro-introduced. Syntax in macro templates currently
does not preserve its source location when compiled to ".zo" format.
That choice was intended to keep bytecode files smaller, but I expect
we'll revisit it
At Mon, 2 Mar 2015 09:25:40 +0300, Sergey Pinaev wrote:
> On Fri, 27 Feb 2015 08:00:34 -0700
> Matthew Flatt wrote:
>
> > That's as far as I've ever gotten with memcheck. Racket manipulates the
> > C stack in ways that are far outside of what is supposed to be allowed,
> > and I think it confuses
5 matches
Mail list logo
