On Wed, 6 Feb 2019 16:25:47 +, Stephen De Gabrielle
wrote:
>Dave Herman recently tweeted[1] that consulting a PL specialist was a
>good idea for little languages to avoid common foundational mistakes,
>specifically mentioning templating systems and configuration files.
>
>So when designing(or
On Wed, 6 Feb 2019 12:50:21 -0500, Matthias Felleisen
wrote:
>> On Feb 6, 2019, at 12:30 PM, 'Paulo Matos' via Racket Users
>> wrote:
>>
>> I was quite surprised to read these nanopass ideas have been around for
>> so long.
>
>
>1. The educational idea came first:
>
>A Nanopass framework for
George Neuner wrote on 2/7/19 12:43 PM:
No offense to Herman, but I think the problem with consulting experts
is that there are relatively few language experts who are available to
consult.
I suspect there's so very little *market* for such little language
experts. Some non-exhaustive sugges
For what it's worth, I like having the Guide and the Reference be
separate things. They have different purposes and trying to mash them
together is likely to make them worse at both.
The Guide is designed to introduce new concepts, give the reader basic
familiarity, and clarify edge cases.
The R
This is a repost of a message sent through Gmane that seems to have
gotten lost. The original may show up at some point - apologies if you
see this twice.
On Wed, 6 Feb 2019 16:25:47 +, Stephen De Gabrielle
wrote:
>Dave Herman recently tweeted[1] that consulting a PL specialist was
I should add that the changes are things that likely won't affect most
code. For example, removing the deprecated functions and getting rid
of a number of places where a function "helpfully" flattens its
arguments, which often means changing the '*' version of the function
to be the primary versio
tl;dr If no one is then I'm going to make a couple of breaking
changes. If someone is, I won't.
Secondarily, is there a way to install a specific version of a package?
Long: handy is a collection of utilities that I've accumulated since
I started working with Racket. Due to lack of experience
Ok
So there is no need to add #lang before I am writing the code.
Thanks,
Or
On Thursday, February 7, 2019 at 7:00:52 PM UTC+2, Matthias Felleisen wrote:
>
>
> As several people have mentioned in the past, you go into DrRacket and use
> the Language menu to choose Pretty Big.
>
>
>
> > On Fe
As several people have mentioned in the past, you go into DrRacket and use the
Language menu to choose Pretty Big.
> On Feb 7, 2019, at 11:57 AM, orenpa11 wrote:
>
> Hi,
> If I would like to write a code in pretty big what is the first line that
> need to be written ?
> Can I use #lang
Hi,
If I would like to write a code in pretty big what is the first line that
need to be written ?
Can I use #lang ?
Thanks,
Or
--
You received this message because you are subscribed to the Google Groups
"Racket Users" group.
To unsubscribe from this group and stop receiving emails from it
On 06/02/2019 21:09, Shu-Hung You wrote:
>
>
> On Wed, Feb 6, 2019 at 9:42 AM 'Paulo Matos' via Racket Users
> mailto:racket-users@googlegroups.com>>
> wrote:
>>
>>
>>
>> On 06/02/2019 16:00, Shu-Hung You wrote:
>> > print-values is a normal identifier introduced by the racket/base's
>> > macr
aha, here it is!
The closest form is then `(call-with-input-string str (λ(in)(port->list
read in)))'.
Thanks Sam and Alex!
On Wed, Feb 6, 2019 at 10:01 PM Sam Tobin-Hochstadt
wrote:
> Also, almost that `read-all` function is provided as `port->list` from
> `racket/port`.
>
> Sam
>
> On Wed, Feb
12 matches
Mail list logo
