0 Members and 3 Guests are viewing this topic.
Wow, this is a really dead-close poll! Not sure what I'm going to do yet, I usually only make a change this large if there is overwhelming support for it. And no, it doesn't affect compile time because axe has to figure out where to close the parenthesis (pop the stack) on its own already without them so it would take just as long. This would only be a programmer convenience and wouldn't change anything at all about the compiling process or generated programs. If you are extremely for it or against it, please state your lengthy opinions why this is either a terrible idea or an absolute necessity.
Another new feature I am adding is a new style of pointer referencing. For any variable or static pointer you can now write {__+A} as A(__). and {__*2+A}r as A(__)r. Here, the variable A can also be a ram location like L1, a static pointer like Str1, and possibly a file object like Y1 if I can get that to work. That means things like L1(7) means the same thing as in basic as it does in Axe; the 7th item in L1's memory. I think this form will make pointers easier for beginners to understand and reduce pointer related errors.
That means things like L1(7) means the same thing as in basic as it does in Axe; the 7th item in L1's memory.
Here's one that I think would be pretty useful and easy to implement: custom interrupts that call the OS interrupt handler before starting or upon finishing. This would allow programmers to use commands like getKey or getKeyr with custom interrupts enabled, which could be very useful. Perhaps fnInt(LBL,FREQ)r? If they wanted they could actually use this to speed up arrow key repeats as well.
In other news, Frey continues kicking unprecedented levels of ass.
Wait, even on Ifs and Disps and things like that? Remember Python doesn't even enforce them for those. The commands with a space with them are meant to have a different interface IMO.
Wait, even on Ifs and Disps and things like that? Remember Python doesn't even enforce them for those. The commands with a space with them are meant to have a different interface IMO.EDIT: Unless you make Axe Tokens get rid of the spaces and replace them with (, but I doubt that's practical.
Quote from: Deep Thought on May 08, 2011, 11:40:11 amWait, even on Ifs and Disps and things like that? Remember Python doesn't even enforce them for those. The commands with a space with them are meant to have a different interface IMO.EDIT: Unless you make Axe Tokens get rid of the spaces and replace them with (, but I doubt that's practical.I didn't say Disps, did I?