Laurent wrote at 11/23/2013 10:45 AM:
I think what is missing is a complete example as a tutorial, like
"You've written a module? Here is what to do, step by step, to
document it and make it a package. Here is the example module file,
here is the corresponding scribble file (with defproc, def
At Sat, 23 Nov 2013 22:58:35 +0800, Yu Yang wrote:
> when racket get an exception, it will show an error message like this
> > procedure application: expected procedure, given: '(1 2 3) (no arguments)
> but this message seems too simple to figure out where the bug is. so I wan
> to know if there is
On Nov 23, 2013, at 10:45 AM, Laurent wrote:
> On Sat, Nov 23, 2013 at 4:04 PM, Greg Hendershott
> wrote:
>
> Let me see if I can find time to review the current docs for Planet
> and the new package system, and see where more examples/tips -- or at
> least links to examples -- could go, and
On Sat, Nov 23, 2013 at 4:04 PM, Greg Hendershott wrote:
>
> Let me see if I can find time to review the current docs for Planet
> and the new package system, and see where more examples/tips -- or at
> least links to examples -- could go, and submit a PR.
>
My 2 cents: I think what is missing i
Bonjour,
For having the stack trace you need to use the errortrace library
http://docs.racket-lang.org/errortrace/.
If you run drracket you can activate it or not when you choose the language.
If you run geiser you can put "(require errortrace)" in ~/.racket-geiser.
If you run from the command
We need a bit more information to help you because Racket provides precisely
the information that you're looking for in DrRacket. Take this program:
#lang racket
(sin
(cos
(tan
(abs
(add1
(sub1
((list 1 2 3
Run it and you get
> . . application: not a procedure
On Fri, Nov 22, 2013 at 6:41 PM, Sam Tobin-Hochstadt
wrote:
> On Fri, Nov 22, 2013 at 8:46 AM, Eli Barzilay wrote:
>>
>>> Later I finally grokked why. I can translate the at-exp to the s-exp
>>> on the fly.
>>
>> It's probably good to make this an important goal when learning the
>> system, even
when racket get an exception, it will show an error message like this
> procedure application: expected procedure, given: '(1 2 3) (no arguments)
but this message seems too simple to figure out where the bug is. so I wan
to know if there is any way to make racket show call stack, when it get an
exc
On Nov 23, 2013, at 1:46 AM, John Clements wrote:
> I'm preparing a 10-minute lightning talk on hygienic macros in rust (preview:
> I'm barely going to *mention* hygiene), and in the process, I've been
> surveying some of the Rust macros, and roughly categorizing them in terms of
> the "three
9 matches
Mail list logo
