Yep, using lexer/c from syntax-color/lexer-contract, was documented and
should have been obvious, especially with the big fat hint to look at
text:color<%> which talks about how the coloring function is used. Got it
working now! Thanks again! Next stop...proper indentation.
On Wed, Feb 13, 2019 at
The lexers can be tricky to get right. I struggled with them a lot. Good
luck!
Robby
On Wed, Feb 13, 2019 at 6:29 PM Chris GauthierDickey
wrote:
> Yes, indeed, it's my own #lang I'm having issues with. I hadn't written a
> colorizing function before for a #lang so I tried it out on a very simpl
Yes, indeed, it's my own #lang I'm having issues with. I hadn't written a
colorizing function before for a #lang so I tried it out on a very simple
language to make sure I understood it. I'm not using the lexer-contract,
I'll give that a shot and see if I can narrow it down. Thanks for the
advice!
Am I right in inferring this is a lang you made and not a lang that
you'd like to report a bug about?
The symptoms you're seeing are generally bugs in the results of the
lexing function. It can be hard to get those right and the colorer
calls into your lang's reader in ways that you might not have
Thanks
I should note that anyone with a GitHub account can edit
https://github.com/racket/racket/wiki/Python-to-Racket
S.
On Wed, 13 Feb 2019 at 21:26, Matthias Felleisen
wrote:
>
> Not until there’s demand. I think we do see demand for Python transfers.
>
>
>
> > On Feb 13, 2019, at 3:11 PM,
On Wed, 13 Feb 2019 at 21:36, Matthias Felleisen
wrote:
> [...]
> I don’t think this is a linear order. It’s more like a landscape with dots
> and connections and hyper-edges and such. In particular,
>
Thanks. I feel like I need to do a ‘topic map’ (like my niece does in
school) to get my head a
> On Feb 13, 2019, at 10:24 AM, Stephen De Gabrielle
> wrote:
>
> • programmer (without compilers course)
> • did compilers at degree level (can still remember it and it covered
> design decisions, as opposed to algorithms and data structures)
> • Beautiful Racket and/or/ h
Not until there’s demand. I think we do see demand for Python transfers.
> On Feb 13, 2019, at 3:11 PM, Stephen De Gabrielle
> wrote:
>
> Should there be similar pages for Javascript, Java,C#, C/C++, Ruby, PHP,
> Visual Basic, Scratch and Haskell?
>
> S.
>
> On Wed, Feb 13, 2019 at 8:03
Should there be similar pages for Javascript, Java,C#, C/C++, Ruby, PHP,
Visual Basic, Scratch and Haskell?
S.
On Wed, Feb 13, 2019 at 8:03 PM Stephen De Gabrielle <
spdegabrie...@gmail.com> wrote:
> I created a DRAFT page on the Racket GitHub wiki:
> https://github.com/racket/racket/wiki/
I created a DRAFT page on the Racket GitHub wiki:
https://github.com/racket/racket/wiki/Python-to-Racket
It links to a 'Choosing a data structure' page
https://github.com/racket/racket/wiki/Choosing-a-data-structure
- this just as copy of the table created by Jens Axel Søgaard at:
https://sta
ICFP 2019 Student Research Competition
Call for Submissions
ICFP invites students to participate in the Student Research
Competition in order to present their research and get feedback from
prominent members of the programming language research
community. Please submit you
PACMPL Volume 3, Issue ICFP 2019
Call for Papers
accepted papers to be invited for presentation at
The 24th ACM SIGPLAN International Conference on Functional Programming
Berlin, Germany
Thank you Neil, George and Matthias.
I'm interested in the HCI advice, where they impact both the language
developer and the language user(s):
- [avoid]* "Lack of abstraction mechanisms" [DH]*
- *"figuring out what your composable primitives are." [DH]*
- [avoid] *"Reinventing lexical sc
13 matches
Mail list logo