Varargs-like doesn't exist in Axe ? What about all the text commands ?

Not really varargs. Something like Disp A,B,C is parsed like Disp A : Disp B : Disp C. A proper varargs function collects all arguments and then executes one function, to which all arguments are exposed at once.

Great
I am not sure I'll use it in any of my releases, but this could still be very helpful in unfinished projects to have functionnal code faster (and then only have beautiful interfaces).

Great
I am not sure I'll use it in any of my releases, but this could still be very helpful in unfinished projects to have functionnal code faster (and then only have beautiful interfaces).

*Yes ! My very first +1 ! I love you !*
Thanks ! Personally, I think I'll use it in some projects which have a TI-design...
I'm happy to have finished this Axiom ! Finished debugging !

Thanks for helping to demonstrate for me how this stuff works. I'll try to implement those kind of simple menus into native Axe. I haven't been able to think of an easy/elegant way to allow for inclusion of the mode menu style selections or window menu style numerical inputs, so those may be left out.

I had an idea of syntax to implement it in Axe Parser. But you can decide to implement it like in TI-Basic (I'll give you the source code), and change it later (in Axe 2.0 ?). Additionally, numerical inputs returns floating point numbers... (it might be possible to change the parsing method, but... it would be some work too).

This is awesome Zemmargorp, but as a future advice I would recommend avoiding reposting the same message multiple times in different topic, as this could be considered spam. The two other messages (in the axiom thread and your new topic should be enough)

Thank you ! I know three messages is a lot, but as I posted earlier information about this axiom in this topic, I wanted to write I finished it, in case somebody here saw the other messages and wondered if the project was made or not. But you're right : the way I posted it looks a bit like an ad !

A token to ignore the next token doesn't sound like a good idea from a language design standpoint. However, an escape sequence token does. But I have one issue with this: what token do I use? Axe has already used up all the viable symbol tokens that I can think of.

They're not used, but I can't say I particularly like them as escape tokens because they're not really symbols. Unfortunately, there aren't many other choices, apart from some clever idea to do it some other way.


EDIT: One "clever idea" I thought of was changing the primary method of displaying a new line on the homescreen to Disp n and claiming i for this. Disp i can be kept as allowed syntax for backwards compatibility, but I like the switch overall. n makes much more sense as a newline character, as the letter is used in many other instances to denote a newline. And although it's still a letter and not a symbol, I'm more comfortable making i the escape token, because it's normal meaning is sort of like a modifier. I'm still not overly keen on this idea, though, as it still isn't an actual symbol and would muddy things up a bit if a future version of Axe called for complex numbers, which isn't that unfathomable if floats were added.

Well I never use Disp so I never use i, so I don't really care if it is renamed n
Plus the fact you said n is more logical for a newline.

I also like Zemmargorp's idea about the "!", which not only lets Disp untouched but also lets you an open door for your complexes