Javascript naming style

It goes like this: name().occupation(), or they allow structures, name.address. But everything is a variable, everything is looked up and nested. Look up name, and it gives you methods on occupation. We can do the same thing with web bots, only it is more restricted. The entire stepping API is more restrictive then a general Javascript interpreter. But the machine still does nested indexing. Finding an index is step_fetch from the current symbol table. If the result refers to another table, then switch tables and repeat. The machine on start will prepare operators for the known indexing tables, then every index is a simple execution and the results returned. What does an indexing table look like? Dunno, but I am planning to make a square and will likely peruse some other software, like see how Fossil uses indexing tables in sqlite3.

I still worry about when it should do look ups and when not to. There is at least one hidden over loader that tells the machine the current key is immediate. Dunno how and when it is activated from the Json syntax, but I can wing it. But all the indexing tablse will look alike, at least the first few colunms. (The machine can work square tables as variable sized). Probably one of the things I do before too long is implement a nested indexing system. Look around for a B-Tree style, but simple, name space framework, or go for maximum simplicity myself.

Then there are the local look ups, it would be ice to have hidden overloads that identify immediate key, local symbol, or indexed symbol, and a way for Lazy J to pick up on the grammar for that. Hmm... I smell a battle with Quotation marks coming up.

Here at Imagisoft, punctuation marks are a precious commodity, we hat to see them wasted on bland text. But I am thinking of conceding the battle, move on with the show. So, let us say the double quotes means this immediate key value. Now I have a shot, without introducing anything else. If it isn't quoted, if it isn't local, then run the indexer to a conclusion. There, a rule of G grammar, which I will promptly forget.

That means the quotation mark become a standard ugly to the machine, hidden in the link value will be the quotation mark indicator which will stop table look up. It also means I can reproduce the quote marks for Json readers.