Re: [racket-users] udelim package -- more parens than you can shake a stick at

On Sun, Sep 25, 2016 at 4:21 PM, William G Hatch wrote: > >> Yes, and you can do all of that with just a string, which you can >> still get from an @-form -- just throw a syntax error if it's not all >> strings. And with just that you get the *benefit* of ignoring >>

Re: [racket-users] udelim package -- more parens than you can shake a stick at

On Sun, Sep 25, 2016 at 2:19 PM, Matthew Butterick wrote: > > On Sep 25, 2016, at 2:10 AM, Eli Barzilay wrote: >> *Don't* confuse scribble-the-documentation-system with the syntax -- >> the syntax is useful for many other cases, and designed to make sense >>

Re: [racket-users] udelim package -- more parens than you can shake a stick at

On Sun, Sep 25, 2016 at 01:50:51PM -0700, Dupéron Georges wrote: If I understand you well, the intended use of your nested delimiters can be more or less described as syntactic sugar for #reader, with auto-detection of where the string ends: (filter foo? (python-ish-list-comprehend

Re: [racket-users] udelim package -- more parens than you can shake a stick at

I second the idea that the documentation could be clearer on the difference between "#lang scribble/base" and friends and what can be done with the at-reader in general, as shown in languages like "scribble/text" and "scribble/html". Despite having used both "scribble/base"-family languages and

Re: [racket-users] udelim package -- more parens than you can shake a stick at

If I understand you well, the intended use of your nested delimiters can be more or less described as syntactic sugar for #reader, with auto-detection of where the string ends: (filter foo? (python-ish-list-comprehend «thing for x in sqlish(«select * from foo») where

Re: [racket-users] udelim package -- more parens than you can shake a stick at

On Sun, Sep 25, 2016 at 05:10:27AM -0400, Eli Barzilay wrote: To be clear, no offense taken That's good. After I read "Eli bait" my mind took the rest as having an annoyed tone, probably from reading too many online flame wars. It's hard to tell people's emotions in text. I think ultimately

Re: [racket-users] A Racket talk in Rubyconf Brazil

I agree! Nice overview. Vincent On Sun, 25 Sep 2016 13:31:59 -0400, Matthias Felleisen wrote: > > Looks like a cool talk. Thanks for sharing. > > On Sep 25, 2016, at 11:53 AM, Ronie Uliana > wrote: > > > > > Hi, there! > > >

[racket-users] Adding libraries to the student language search

When the current language is one of the student languages searching the documentation from DrRacket limits the search to a subset libraries installed. Is there any way to add a new library to this subset? --Spencer -- You received this message because you are subscribed to the Google Groups

[racket-users] Re: [ANN] New package: live-free-or-die

let its spirit live on, for jay's big heart ^^ On Thursday, 22 September 2016 04:33:32 UTC+2, Jay McCarthy wrote: > I've just put a new package on the server: live-free-or-die > > This package lets you escape from Typed Racket's contracts. > > -- > > Here's a little example: > > Suppose that

[racket-users] post racketcon '16: simulation of population playing PD game in Racket

Hello everyone, So I thank again Matthias for the opportunity and everyone for the incredible hospitality. I write down the script of my presentation, add notes, add the extra parts (that i said i didnt have time to show), link to code parts on github, and append a final part to answer Ben's

Re: [racket-users] udelim package -- more parens than you can shake a stick at

On Sep 25, 2016, at 2:10 AM, Eli Barzilay wrote: > *Don't* confuse scribble-the-documentation-system with the syntax -- the > syntax is useful for many other cases, and designed to make sense in > other cases. See my description (specifically section 4, which is very >

Re: [racket-users] A Racket talk in Rubyconf Brazil

Looks like a cool talk. Thanks for sharing. > On Sep 25, 2016, at 11:53 AM, Ronie Uliana wrote: > > Hi, there! > > I gave a talk about Racket in Rubyconf Brazil yesterday (saturday 24). > > Here are the slides >

[racket-users] A Racket talk in Rubyconf Brazil

Hi, there! I gave a talk about Racket in Rubyconf Brazil yesterday (saturday 24). Here are the slides translated to English and here the original in Portuguese :) Not sure I gave the right

Re: [racket-users] udelim package -- more parens than you can shake a stick at

> On Sep 25, 2016, at 3:55 AM, William G Hatch wrote: > > On Sat, Sep 24, 2016 at 05:33:18PM -0400, Alex Knauth wrote: >> The way racket already does this is with a 'paren-shape syntax property, >> which you can ignore if you want to use ｢｣ as a normal visually distinctive

Re: [racket-users] udelim package -- more parens than you can shake a stick at

On Sun, Sep 25, 2016 at 3:34 AM, William G Hatch wrote: > First of all, I really didn't mean any offense. I think the at-reader > and my nestable string delimiters are trying to solve slightly > different problems, and I didn't really convey that well. I didn't > mean for it

Re: [racket-users] udelim package -- more parens than you can shake a stick at

On Sat, Sep 24, 2016 at 05:33:18PM -0400, Alex Knauth wrote: The way racket already does this is with a 'paren-shape syntax property, which you can ignore if you want to use ｢｣ as a normal visually distinctive paren type *without* needing a special macro with a weird name. I hadn't thought

Re: [racket-users] Re: udelim package -- more parens than you can shake a stick at

One note about the docs: when you write: (open-input-string "«this is a string with nested «string delimiters.» No \n escape interpreting.»") the "\n" is already escaped by the "…" fed into open-input-string I think, so what udelim parses in that example is a raw newline, not the \

Re: [racket-users] udelim package -- more parens than you can shake a stick at

First of all, I really didn't mean any offense. I think the at-reader and my nestable string delimiters are trying to solve slightly different problems, and I didn't really convey that well. I didn't mean for it to be "Eli bait". Let me explain my use case a little, and maybe my earlier mail