On Mon, Sep 26, 2016 at 9:40 AM, Matthew Butterick wrote:
>
> T as in "text":
>
> @-form => T-form
> @-expression = > T-expression (or t-exp in shorthand)
(Or "Texprs"...)
> #lang at-exp racket => #lang t-exp racket
>
> #lang scribble/text => #lang t-exp/text
>
> #lang
IMHO the "text expression" does precisely the same as current use of scribble
-> pigeonholing the syntax for one use: in the case of scribble it is
"documentation" in the case of text - "text processing".
I actually find "at-exp" to be quite fitting but would keep using this form
everywhere
On Mon, Sep 26, 2016 at 01:54:35AM -0400, Eli Barzilay wrote:
But I'm guessing that I lost you again, so none of this would move you.
All I can do at this point is sigh and hope that you'll end up at the
best case of re-implementing @-expressions with the slightly more
verbose syntax that you
On Sep 25, 2016, at 10:53 PM, Eli Barzilay wrote:
> When we realized that this is going
> to be confusing, it was already clear that the latter meaning is already
> "winning", so the syntax turned into @-forms, @-expressions etc -- I'm
> probably the only one who still uses
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
>>
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
>>
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
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
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
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
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
>
> 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
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
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
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
On Sat, Sep 24, 2016 at 12:46 PM, William G Hatch wrote:
>
> First, nestable strings are nice for other things as well. For
> instance, since they don't escape backslashes, they are nice for
> constructing regexps, which famously explode into mountains of
> backslashes due to
> On Sep 24, 2016, at 12:46 PM, William G Hatch wrote:
> Additionally, I've long wanted more types of parens in Racket. I
> haven't really known what I would do with them -- I use Racket's
> conventions for () and [], and have my own loose convention for {}. But
> after
Hello everybody,
I'm announcing another little package I've written to get comments on
it: udelim.
Udelim is a library for adding extra parens and string delimiters to
your language.
For many years, before ever coming to racket, I've wanted nestable
string delimiters. Especially when working
18 matches
Mail list logo