(Some more thinking-out-loud stuff.) The purpose of constructing the object tree (second stage) is to reform the AST into something more convenient for the execution (third stage).

To that end, function nodes and their opts/args/code child nodes should be "collapsed" into one node somehow.

I can also handle the choosing of functions in the second stage, so that it's not done in the first stage (at parse time).

@El'endiaStarman But. I know it's bad, but only because I do not aim for people to actually use them.

They're pretty much all hobby projects intended to help me learn.

@El'endiaStarman Also, I don't plan to edit the actual files/git repo anyway

@MarsUltor Which is great. I just don't want to risk any adverse impact to the development of Pytek.

@MarsUltor Then you don't need access anyway.

Okay.

Also, I think you broke the c9 linter

I haven't done anything on C9 for a couple weeks. I've been coding locally.

@El'endiaStarman ?

Um

up to base 36?

@El'endiaStarman Possibly 0a00x?

But mostly, I really don't get 'That should work well, up to base 36.'

36bz would be equivalent to 35.

Ah-ha, best way to describe the second stage: converting AST nodes into object nodes, like AST_number to pInteger or pFloat, plus building the symbol table. I think that gets basically all of its purpose. Excellent, that helps me a lot.

pytek_executor.py now has two functions named objectify and execute. Sounds like a recipe for starting wars. >_>

rofl

Newcomers, check this for what's basically a summary of Pytek:

When is Pytek going to be completed?

Is there a GitHub repo?

@Downgoat I haven't even finished the parser yet. :P

@ZachGates Not yet. Gonna finish the parser first, at least.

@El'endiaStarman oh :|

Ok so you're still in planning mode then

No, I'm in development mode.

It's just that the parser is complex.

+1000 for braces

Okay gotcha

I'm aiming to implement all the language-intrinsic features first, and then add the commands (built-in functions) over time.

Good idea. That's what I've been doing with Gogh

Just had a realization as to (part of) why it's so useful to convert from AST to object tree: object nodes can have more methods defined, like a successor function, and there's a good distinction here between what it looks like and what it is/does.

Another thing Pytek should do better than Python: when there's an index-out-of-range error, tell the user which list/sequence!

I mean, I just got that error on this line: currNodes[-2].children[currChild[-1]] = result. There are three lists here.

Alright, AST -> object tree conversion works!

Just need to do the symbol table stuff and that'll complete the second stage!