#craftinginterpreters — Public Fediverse posts

First actual programming chapter of #CraftingInterpreters done. Had to do it over the course of several seasons but I’ve now got a working lexer: I can type in some code and the program will recognise it as code. Baby steps! Actually doing anything with the code is several chapters away.

An interesting thing is that I can already see ways I could do things differently. (Store the content of comments. Treat ints and floats separately. And so on.) Don’t want to get sidetracked by implementing that yet but looking ahead to how I might implement a language of my own.

First actual programming chapter of #CraftingInterpreters done. Had to do it over the course of several seasons but I’ve now got a working lexer: I can type in some code and the program will recognise it as code. Baby steps! Actually doing anything with the code is several chapters away.

An interesting thing is that I can already see ways I could do things differently. (Store the content of comments. Treat ints and floats separately. And so on.) Don’t want to get sidetracked by implementing that yet but looking ahead to how I might implement a language of my own.

First actual programming chapter of #CraftingInterpreters done. Had to do it over the course of several seasons but I’ve now got a working lexer: I can type in some code and the program will recognise it as code. Baby steps! Actually doing anything with the code is several chapters away.

An interesting thing is that I can already see ways I could do things differently. (Store the content of comments. Treat ints and floats separately. And so on.) Don’t want to get sidetracked by implementing that yet but looking ahead to how I might implement a language of my own.

First actual programming chapter of #CraftingInterpreters done. Had to do it over the course of several seasons but I’ve now got a working lexer: I can type in some code and the program will recognise it as code. Baby steps! Actually doing anything with the code is several chapters away.

An interesting thing is that I can already see ways I could do things differently. (Store the content of comments. Treat ints and floats separately. And so on.) Don’t want to get sidetracked by implementing that yet but looking ahead to how I might implement a language of my own.

My current thinking is to do the first half in both Java and Go, but chapter by chapter. Hopefully that way I can avoid getting sidetracked by any Go-specific problems. #CraftingInterpreters

My current thinking is to do the first half in both Java and Go, but chapter by chapter. Hopefully that way I can avoid getting sidetracked by any Go-specific problems. #CraftingInterpreters

My current thinking is to do the first half in both Java and Go, but chapter by chapter. Hopefully that way I can avoid getting sidetracked by any Go-specific problems. #CraftingInterpreters

My current thinking is to do the first half in both Java and Go, but chapter by chapter. Hopefully that way I can avoid getting sidetracked by any Go-specific problems. #CraftingInterpreters

My current thinking is to do the first half in both Java and Go, but chapter by chapter. Hopefully that way I can avoid getting sidetracked by any Go-specific problems. #CraftingInterpreters

first time writing actual java in ... 16+ years?

this is quite longwinded isn't it. not sure how much i want to deviate from the book — using type inference where the book writes explicit types should be fine, i assume?

or maybe i'll just go wild and try implementing it in go instead

#CraftingInterpreters

first time writing actual java in ... 16+ years?

this is quite longwinded isn't it. not sure how much i want to deviate from the book — using type inference where the book writes explicit types should be fine, i assume?

or maybe i'll just go wild and try implementing it in go instead

#CraftingInterpreters

first time writing actual java in ... 16+ years?

this is quite longwinded isn't it. not sure how much i want to deviate from the book — using type inference where the book writes explicit types should be fine, i assume?

or maybe i'll just go wild and try implementing it in go instead

#CraftingInterpreters

first time writing actual java in ... 16+ years?

this is quite longwinded isn't it. not sure how much i want to deviate from the book — using type inference where the book writes explicit types should be fine, i assume?

or maybe i'll just go wild and try implementing it in go instead

#CraftingInterpreters

first time writing actual java in ... 16+ years?

this is quite longwinded isn't it. not sure how much i want to deviate from the book — using type inference where the book writes explicit types should be fine, i assume?

or maybe i'll just go wild and try implementing it in go instead

#CraftingInterpreters

Big thanks to @munificent — Crafting Interpreters inspired me to build my own programming language, Piscript (pixel Script)! 🚀
Just published it on GitHub: https://github.com/rolandbrake/piscript
#programming #interpreters #langdev #CraftingInterpreters

Big thanks to @munificent — Crafting Interpreters inspired me to build my own programming language, Piscript (pixel Script)! 🚀
Just published it on GitHub: https://github.com/rolandbrake/piscript
#programming #interpreters #langdev #CraftingInterpreters

Big thanks to @munificent — Crafting Interpreters inspired me to build my own programming language, Piscript (pixel Script)! 🚀
Just published it on GitHub: https://github.com/rolandbrake/piscript
#programming #interpreters #langdev #CraftingInterpreters

Big thanks to @munificent — Crafting Interpreters inspired me to build my own programming language, Piscript (pixel Script)! 🚀
Just published it on GitHub: https://github.com/rolandbrake/piscript
#programming #interpreters #langdev #CraftingInterpreters

Big thanks to @munificent — Crafting Interpreters inspired me to build my own programming language, Piscript (pixel Script)! 🚀
Just published it on GitHub: https://github.com/rolandbrake/piscript
#programming #interpreters #langdev #CraftingInterpreters

(Yet Another) implementation of the Lox scripting language from the book Crafting Interpreters (★★★★★).
It's not complete, but can run a range of interesting programs.
Hope it's useful to anyone else trying to translate the book into #zig
https://github.com/ringtailsoftware/zlox #craftinginterpreters

(Yet Another) implementation of the Lox scripting language from the book Crafting Interpreters (★★★★★).
It's not complete, but can run a range of interesting programs.
Hope it's useful to anyone else trying to translate the book into #zig
https://github.com/ringtailsoftware/zlox #craftinginterpreters

(Yet Another) implementation of the Lox scripting language from the book Crafting Interpreters (★★★★★).
It's not complete, but can run a range of interesting programs.
Hope it's useful to anyone else trying to translate the book into #zig
https://github.com/ringtailsoftware/zlox #craftinginterpreters

(Yet Another) implementation of the Lox scripting language from the book Crafting Interpreters (★★★★★).
It's not complete, but can run a range of interesting programs.
Hope it's useful to anyone else trying to translate the book into #zig
https://github.com/ringtailsoftware/zlox #craftinginterpreters

(Yet Another) implementation of the Lox scripting language from the book Crafting Interpreters (★★★★★).
It's not complete, but can run a range of interesting programs.
Hope it's useful to anyone else trying to translate the book into #zig
https://github.com/ringtailsoftware/zlox #craftinginterpreters

Picked up this book; it came highly recommended 😄
#CraftingInterpreters

Picked up this book; it came highly recommended 😄
#CraftingInterpreters

Picked up this book; it came highly recommended 😄
#CraftingInterpreters

Picked up this book; it came highly recommended 😄
#CraftingInterpreters

Picked up this book; it came highly recommended 😄
#CraftingInterpreters

@studiop It sounds like you're trying to represent the associativity and precedence of the syntax of these expressions as you build on them. I think the appropriate way to model this is as a tree.

From "Crafting Interpreters" [1] :

"One way to visualize that precedence is using a tree. Leaf nodes are numbers, and interior nodes are operators with branches for each of their operands."

[1] https://craftinginterpreters.com/representing-code.html

#CraftingInterpreters

@studiop It sounds like you're trying to represent the associativity and precedence of the syntax of these expressions as you build on them. I think the appropriate way to model this is as a tree.

From "Crafting Interpreters" [1] :

"One way to visualize that precedence is using a tree. Leaf nodes are numbers, and interior nodes are operators with branches for each of their operands."

[1] https://craftinginterpreters.com/representing-code.html

#CraftingInterpreters

@studiop It sounds like you're trying to represent the associativity and precedence of the syntax of these expressions as you build on them. I think the appropriate way to model this is as a tree.

From "Crafting Interpreters" [1] :

"One way to visualize that precedence is using a tree. Leaf nodes are numbers, and interior nodes are operators with branches for each of their operands."

[1] https://craftinginterpreters.com/representing-code.html

#CraftingInterpreters

@studiop It sounds like you're trying to represent the associativity and precedence of the syntax of these expressions as you build on them. I think the appropriate way to model this is as a tree.

From "Crafting Interpreters" [1] :

"One way to visualize that precedence is using a tree. Leaf nodes are numbers, and interior nodes are operators with branches for each of their operands."

[1] https://craftinginterpreters.com/representing-code.html

#CraftingInterpreters

Attention pyparsing users: I just pushed release 3.2.0b1 which mostly just drops support for Python 3.6-3.8, but also changes some exception messages. Please give this release a try before I push the final release in early October.

Also includes:
- some nice enhancements to mongodb_query_expression.py
- a parser for the Lox language defined in Robert Nystrom's "Crafting Interpreters"

Full release notes here: https://github.com/pyparsing/pyparsing/releases/tag/3.2.0b1

#python #pyparsing #mongodb #pymongo #craftinginterpreters

Attention pyparsing users: I just pushed release 3.2.0b1 which mostly just drops support for Python 3.6-3.8, but also changes some exception messages. Please give this release a try before I push the final release in early October.

Also includes:
- some nice enhancements to mongodb_query_expression.py
- a parser for the Lox language defined in Robert Nystrom's "Crafting Interpreters"

Full release notes here: https://github.com/pyparsing/pyparsing/releases/tag/3.2.0b1

#python #pyparsing #mongodb #pymongo #craftinginterpreters

Attention pyparsing users: I just pushed release 3.2.0b1 which mostly just drops support for Python 3.6-3.8, but also changes some exception messages. Please give this release a try before I push the final release in early October.

Also includes:
- some nice enhancements to mongodb_query_expression.py
- a parser for the Lox language defined in Robert Nystrom's "Crafting Interpreters"

Full release notes here: https://github.com/pyparsing/pyparsing/releases/tag/3.2.0b1

#python #pyparsing #mongodb #pymongo #craftinginterpreters

Attention pyparsing users: I just pushed release 3.2.0b1 which mostly just drops support for Python 3.6-3.8, but also changes some exception messages. Please give this release a try before I push the final release in early October.

Also includes:
- some nice enhancements to mongodb_query_expression.py
- a parser for the Lox language defined in Robert Nystrom's "Crafting Interpreters"

Full release notes here: https://github.com/pyparsing/pyparsing/releases/tag/3.2.0b1

#python #pyparsing #mongodb #pymongo #craftinginterpreters

Attention pyparsing users: I just pushed release 3.2.0b1 which mostly just drops support for Python 3.6-3.8, but also changes some exception messages. Please give this release a try before I push the final release in early October.

Also includes:
- some nice enhancements to mongodb_query_expression.py
- a parser for the Lox language defined in Robert Nystrom's "Crafting Interpreters"

Full release notes here: https://github.com/pyparsing/pyparsing/releases/tag/3.2.0b1

#python #pyparsing #mongodb #pymongo #craftinginterpreters

"all i know is impl Iterator, eat hot chip, and lie"

my implementation of Lox has a scanner! it doesn't allocate, since it shouldn't #CraftingInterpreters

https://github.com/ryleelyman/lox

"all i know is impl Iterator, eat hot chip, and lie"

my implementation of Lox has a scanner! it doesn't allocate, since it shouldn't #CraftingInterpreters

https://github.com/ryleelyman/lox

10 months and 99 commits later, I finished the first part of #CraftingInterpreters and I have a fully functioning language written in #Swift 🥳

It took longer than what I expected, but I've not been the most consistent with it tbh

Now it's time to go back to my toy engine for a while. I'm trying to stick to only one personal project at a time to increase the chances of actually finishing them 😅

When I get back for the 2nd part, I think I'll implement it in #Zig rather than C.

10 months and 99 commits later, I finished the first part of #CraftingInterpreters and I have a fully functioning language written in #Swift 🥳

It took longer than what I expected, but I've not been the most consistent with it tbh

Now it's time to go back to my toy engine for a while. I'm trying to stick to only one personal project at a time to increase the chances of actually finishing them 😅

When I get back for the 2nd part, I think I'll implement it in #Zig rather than C.

#TIL @munificent wrote a #book on interpreters named #CraftingInterpreters. It is illustrated by (his own) hand and I think that’s beautiful.

https://journal.stuffwithstuff.com/2020/04/05/crafting-crafting-interpreters/#:~:text=Illustrating%20by%20hand

#TIL @munificent wrote a #book on interpreters named #CraftingInterpreters. It is illustrated by (his own) hand and I think that’s beautiful.

https://journal.stuffwithstuff.com/2020/04/05/crafting-crafting-interpreters/#:~:text=Illustrating%20by%20hand

#TIL @munificent wrote a #book on interpreters named #CraftingInterpreters. It is illustrated by (his own) hand and I think that’s beautiful.

https://journal.stuffwithstuff.com/2020/04/05/crafting-crafting-interpreters/#:~:text=Illustrating%20by%20hand

#TIL @munificent wrote a #book on interpreters named #CraftingInterpreters. It is illustrated by (his own) hand and I think that’s beautiful.

https://journal.stuffwithstuff.com/2020/04/05/crafting-crafting-interpreters/#:~:text=Illustrating%20by%20hand

And now regular user-defined functions!
This is fun! :D

#CraftingInterpreters #Swift :mac:

And now regular user-defined functions!
This is fun! :D

#CraftingInterpreters #Swift :mac:

And now regular user-defined functions!
This is fun! :D

#CraftingInterpreters #Swift :mac:

That side note really got me 🤣

#CraftingInterpreters