[racket-users] degenerate performance in syntax-parse

Hi all - In the process of putting together a somewhat complex application using syntax-parse, I discovered that when I specified a repeated pattern in a syntax-class (which was incorrect) AND I had a certain usage of the syntax transformer with an error, it would lead to degenerate

[racket-users] Re: opinions on YAML as communication tool

If you'd still like to use yaml, I would like to quietly point out that each of the following is a valid boolean value in yaml: - true - false - yes - no - y - n - True - False - TRUE - FALSE - on - off - YES - NO ... but it's not strictly case-insensitive, as yES is parsed as a string -- You

Re: [racket-users] opinions on YAML as communication tool

> On Oct 21, 2016, at 12:42 PM, Tony Garnock-Jones wrote: > > On 10/21/2016 01:21 AM, 'John Clements' via Racket Users wrote: >> I thought hard about scribble and JSON (and xml, yecch), but I think >> that YAML and sexps are the two viable candidates, and I’m guessing >>

Re: [racket-users] Intro documentation question

On Oct 21, 2016, at 11:39 AM, Doug Edmunds wrote: > > (define series > (lambda (mk) >(hc-append 4 (mk 5) (mk 10) (mk 20 > > (define (rgb-series mk) > (vc-append > (series (lambda (sz) (colorize (mk sz) "red"))) > (series (lambda (sz) (colorize (mk sz)

Re: [racket-users] Unable to track down what is requiring inclusion of tzinfo module - Resolved

This connects to a similar issue I was having with my reorganization of the CLDR libraries (which I'm getting back into): https://groups.google. com/d/msg/racket-dev/MrmxvvKidj8/ASEF22_lBQAJ. It looks like, in the present case, I should do something like this: - The tzdata package includes, in

Re: [racket-users] opinions on YAML as communication tool

On 10/21/2016 01:21 AM, 'John Clements' via Racket Users wrote: > I thought hard about scribble and JSON (and xml, yecch), but I think > that YAML and sexps are the two viable candidates, and I’m guessing > that if non-programmers have to edit it, they’ll be less likely to > botch the YAML one.

[racket-users] Intro documentation question

I am new to Racket and have just started the tutorials. In section 7 "Lexical Scope" of the Quick introduction http://download.racket-lang.org/releases/6.6/doc/quick/index.html there is this code: (define series (lambda (mk) (hc-append 4 (mk 5) (mk 10) (mk 20 (define (rgb-series mk)

Re: [racket-users] Better? or less good?

On Oct 21, 2016, at 7:24 AM, David Raymond Christiansen wrote: > (let ((v #t)) > (if v v fnord)) > > This is not even a program, because "fnord" has no meaning. If you don't like unbound-identifer errors, you can change `#%top`: (define-syntax-rule (#%top . x)

Re: [racket-users] Re: date->seconds complaining about a supposedly non-existent date

On Fri, Oct 21, 2016 at 12:17 AM, Jack Firth wrote: > There's also the Gregor package (https://docs.racket-lang.org/ > gregor/index.html?q=gregor), which gives a much more comprehensive > interface to dates and times. In particular, Gregor allows you to specify > an "offset

Re: [racket-users] opinions on YAML as communication tool

Since we're all just making up stuff, I mostly agree with Ben that if a spreadsheet is the right tool, then use that tool. There are a few spreadsheets that support version control internally, like Google Docs and Microsoft Office Version Tracking. In addition, there are the elite tools of

Re: [racket-users] opinions on YAML as communication tool

I vote that you stick with Excel & change the version control protocol. Maybe: http://stackoverflow.com/a/17106035/5237018 On Fri, Oct 21, 2016 at 9:22 AM, Matthias Felleisen wrote: > > See Claire’s paper on cKanren. Scheduling is one of her examples (though > small

Re: [racket-users] Better? or less good?

Hi again, > The latter has the same meaning as this: > > (let ((v #t)) > (if v v fnord)) > > This is not even a program, because "fnord" has no meaning. Robby pointed out off-list that I should point out that this is a feature of Racket, not programming languages in general. In many other

[racket-users] ACM/SPEC ICPE 2017 - Call for Workshop Proposals

ICPE 2017 8th ACM/SPEC International Conference on Performance Engineering Sponsored by ACM SIGMETRICS, SIGSOFT, and SPEC RG L'Aquila, Italy April 22-26, 2017

Re: [racket-users] Better? or less good?

Hello, I noticed that Racket detects the variables used without any value. But let us consider the expression: (or #t Gor) Since "or" evaluates as few arguments as possible, the result is #t, but this expression is rejected by Racket because "Gor" is unbound. So the rule would become:

Re: [racket-users] Better? or less good?

Hi Jean-Michel: the determination that "Gor" is a free variable happens as part of the compilation of the program, much in the same way that this expression: (or #t (lambda x)) is rejected. Robby On Fri, Oct 21, 2016 at 9:12 AM, Jean-Michel HUFFLEN wrote: >Dear

[racket-users] Better? or less good?

Dear Racket users, I noticed that Racket detects the variables used without any value. But let us consider the expression: (or #t Gor) Since "or" evaluates as few arguments as possible, the result is #t, but this expression is rejected by Racket because "Gor" is unbound. So the

Re: [racket-users] opinions on YAML as communication tool

See Claire’s paper on cKanren. Scheduling is one of her examples (though small scale). > On Oct 21, 2016, at 7:18 AM, Robby Findler > wrote: > > Wh? You're not going to design your own language and implement a > syntax colorer in DrRacket for it so they

Re: [racket-users] opinions on YAML as communication tool

Wh? You're not going to design your own language and implement a syntax colorer in DrRacket for it so they can tell immediately when something goes wrong? ;) Robby On Fri, Oct 21, 2016 at 12:21 AM, 'John Clements' via Racket Users wrote: > Yet another

Re: [racket-users] opinions on YAML as communication tool

'John Clements' via Racket Users (21.10. 01:21): > I thought hard about scribble and JSON (and xml, yecch), but I think > that YAML and sexps are the two viable candidates, and I’m guessing > that if non-programmers have to edit it, they’ll be less likely to > botch the YAML one. My timesheet