When using syntax/parse, is there a good way to do something like this?
(define-splicing-syntax-class options
(pattern (~seq (~or (~optional (~seq (~and #:a a?)))
(~optional (~seq (~and #:b b?)))
(~optional (~seq (~and #:c c?)))
(
I was thinking the parameter could be a handy runtime switch,
defaulting to "safe". However realistically there's probably a lot of
other ground to cover when it comes to "debug" vs. "production"
deployments. Maybe this needs a more comprehensive approach than
nibbling away one switch at a time.
M
Amen
On Tuesday, May 26, 2015, WarGrey Gyoudmon Ju wrote:
> I think user-friendly 500 page should be designed separately just as web
> devs do for 404 page.
> In practice, a user happens to meet an uncaught runtime exception, and
> he's browsing a buggy website,
> perhaps he do not have the will
I think user-friendly 500 page should be designed separately just as web
devs do for 404 page.
In practice, a user happens to meet an uncaught runtime exception, and he's
browsing a buggy website,
perhaps he do not have the will to report the problem, nor the way to
report it.
Finally, devs will fi
Il giorno 26/mag/2015, alle ore 17.11, Matthias Felleisen ha scritto:
>
> On May 26, 2015, at 11:00 AM, Michael Tiedtke
> wrote:
>
>>
>> Il giorno 26/mag/2015, alle ore 14.17, Matthias Felleisen ha scritto:
>>
>>>
>>> On May 26, 2015, at 1:10 AM, Michael Tiedtke wrote:
>>>
Sorry, ut
For the purposes of the Web server, I don't think that's the right
thing to do. The right thing to do if you don't like the error display
is to change the arguments to #:servlet-loading-responder and
#:servlet-responder to print less, or just put with-handlers in your
servlet and do something else.
On 05/25/2015 11:16 AM, Greg Hendershott wrote:
> Should there maybe be a parameter to control whether exn->string
> returns anything interesting? And, should it be #f by default?
That's an interesting idea. I know of examples where Racket error
reports have disclosed sensitive information. Such m
> Alexis, think of a lazy sequence as something that the rest of the program
> will explore. In addition to a GUI-based exploration, I would love to see a
> programmatic one. Imagine
>
> (explore-lazy lazy-sequence:exp strictness-pattern:exp)
>
> where (the value of) strictness-pattern is a f
This is a maintenance release. It's on PLaneT, too. But I can't load it ...
http://planet.racket-lang.org/display.ss?package=Open%20Flowers.plt&owner=mti
--
You received this message because you are subscribed to the Google Groups
"Racket Users" group.
To unsubscribe from this group and stop re
On May 26, 2015, at 1:10 AM, Michael Tiedtke wrote:
> Sorry, ut I call it a workaround.
Please read up on programming language design.
--
You received this message because you are subscribed to the Google Groups
"Racket Users" group.
To unsubscribe from this group and stop receiving emails
10 matches
Mail list logo
