• Features Wishlist 5 1
Currently:

### Author Topic: Features Wishlist  (Read 529918 times)

0 Members and 2 Guests are viewing this topic.

#### Runer112

• Project Author
• LV11 Super Veteran (Next: 3000)
• Posts: 2289
• Rating: +639/-31
##### Re: Features Wishlist
« Reply #3210 on: July 28, 2013, 02:52:49 pm »
That idea has crossed my mind before, but I never really thought about how it could be implemented. Now that I think about it, it's definitely a useful feature, one that I've wanted myself sometimes. After a bit of pondering, I came up with a syntax that I believe should work well from both the appearance and underlying implementation standpoints. To specify a target, you would put a store arrow immediately after the name in the header, followed by a letter, like this:

• :.THING      (Default target)
• :.THING→N    (No shell program)
• :.THING→I    (Ion program)
• :.THING→M    (MirageOS program)
• :.THING→D    (DoorsCS program)
• :.THING→A    (Application)
• :.THING→F    (Axe Fusion)
• :.THING→V    (Appvar)

How do you guys feel about that syntax? Also, note the additional Appvar shell. I thought that was a good idea as well. It's another thing I've wanted in the past but for some reason never thought about actually adding.

#### Hayleia

• Programming Absol
• Coder Of Tomorrow
• LV12 Extreme Poster (Next: 5000)
• Posts: 3367
• Rating: +393/-7
##### Re: Features Wishlist
« Reply #3211 on: July 28, 2013, 02:55:29 pm »
How do you guys feel about that syntax?
I like the idea of having one token for everyone and using letters to see who is who, but the → is a bit confusing according to me. Why not parentheses instead, like .THING() for default, .THING(I) for Ion, etc ? Or if you want to use the →, why not .M→THING instead of .THING→M ?
« Last Edit: July 28, 2013, 02:57:00 pm by Hayleia »
I own: 83+ ; 84+SE ; 76.fr ; CX CAS ; Prizm ; 84+CSE
Sorry if I answer with something that seems unrelated, English is not my primary language and I might not have understood well. Sorry if I make English mistakes too.

#### Streetwalrus

• LV12 Extreme Poster (Next: 5000)
• Posts: 3821
• Rating: +80/-8
##### Re: Features Wishlist
« Reply #3212 on: July 28, 2013, 03:30:00 pm »
I was hoping for something like on line 2 :
Code: [Select]
.Shell <whatever>
Also what about the other features I suggested (build constants) ?

#### Runer112

• Project Author
• LV11 Super Veteran (Next: 3000)
• Posts: 2289
• Rating: +639/-31
##### Re: Features Wishlist
« Reply #3213 on: July 28, 2013, 04:24:07 pm »
How do you guys feel about that syntax?
I like the idea of having one token for everyone and using letters to see who is who, but the → is a bit confusing according to me. Why not parentheses instead, like .THING() for default, .THING(I) for Ion, etc ? Or if you want to use the →, why not .M→THING instead of .THING→M ?

The idea was that you're "storing" the compiled data into the target variable type. Does that win you over at all? I find the parentheses method confusing myself because it suggests to me that the file is some massive routine with input arguments, and I mentioned why I like the store approach in the order first suggested.

If you still aren't a big fan of the original syntax suggestion, it can certainly be changed. It would be good to hear input from a few others before any kind of decisions are made.

I was hoping for something like on line 2 :
Code: [Select]
.Shell <whatever>
Also what about the other features I suggested (build constants) ?

I was steering away from a syntax like this because the target variable type needs to be known before compilation even starts, and having it in the header means no need for lookahead parsing. I'm not sure if you intended this, but this syntax does have the advantage of being backwards compatible (older versions of Axe would ignore the target and use the default target). Whether or not this behavior or good, I'm not sure.

And I'm not sure what the purpose of the "build constants" would be. The calculator model and related hardware information aren't constant, they depend on whatever calculator runs the program. Unless you meant including the specs of the actual calculator building the program, but I can't think of how that would be useful. The compiled code should be the same regardless of which model calculator compiled it.
« Last Edit: July 28, 2013, 04:25:54 pm by Runer112 »

#### Streetwalrus

• LV12 Extreme Poster (Next: 5000)
• Posts: 3821
• Rating: +80/-8
##### Re: Features Wishlist
« Reply #3214 on: July 28, 2013, 04:53:51 pm »
And I'm not sure what the purpose of the "build constants" would be. The calculator model and related hardware information aren't constant, they depend on whatever calculator runs the program. Unless you meant including the specs of the actual calculator building the program, but I can't think of how that would be useful. The compiled code should be the same regardless of which model calculator compiled it.
This could be useful in some rare cases but I think the most useful one would be to know what shell you're compiling for. This way you could make shell specific code.
« Last Edit: July 29, 2013, 04:56:28 am by Streetwalker »

#### Hayleia

• Programming Absol
• Coder Of Tomorrow
• LV12 Extreme Poster (Next: 5000)
• Posts: 3367
• Rating: +393/-7
##### Re: Features Wishlist
« Reply #3215 on: July 29, 2013, 02:08:29 am »
How do you guys feel about that syntax?
I like the idea of having one token for everyone and using letters to see who is who, but the → is a bit confusing according to me. Why not parentheses instead, like .THING() for default, .THING(I) for Ion, etc ? Or if you want to use the →, why not .M→THING instead of .THING→M ?

The idea was that you're "storing" the compiled data into the target variable type. Does that win you over at all? I find the parentheses method confusing myself because it suggests to me that the file is some massive routine with input arguments, and I mentioned why I like the store approach in the order first suggested.

If you still aren't a big fan of the original syntax suggestion, it can certainly be changed. It would be good to hear input from a few others before any kind of decisions are made.
In fact, reading your post again makes me think that your syntax is the best. It stores the THING program into a M(irageOS) program, so it is basically THING→M.
I own: 83+ ; 84+SE ; 76.fr ; CX CAS ; Prizm ; 84+CSE
Sorry if I answer with something that seems unrelated, English is not my primary language and I might not have understood well. Sorry if I make English mistakes too.

#### TIfanx1999

• ಠ_ಠ ( ͡° ͜ʖ ͡°)
• CoT Emeritus
• LV13 Extreme Addict (Next: 9001)
• Posts: 6173
• Rating: +191/-9
##### Re: Features Wishlist
« Reply #3216 on: July 29, 2013, 03:42:32 am »
I think the original suggested syntax is fine. It seems very clear to me.

#### Sorunome

• Fox Fox Fox Fox Fox Fox Fox!
• Support Staff
• LV13 Extreme Addict (Next: 9001)
• Posts: 7920
• Rating: +374/-13
• Derpy Hooves
##### Re: Features Wishlist
« Reply #3217 on: July 29, 2013, 05:03:43 am »
The syntax also is fine for me It IS pretty clear
 THE GAMEAlso, check out my websiteIf OmnomIRC is screwed up, blame me!Click here to give me an internet!

#### Hayleia

• Programming Absol
• Coder Of Tomorrow
• LV12 Extreme Poster (Next: 5000)
• Posts: 3367
• Rating: +393/-7
##### Re: Features Wishlist
« Reply #3218 on: July 29, 2013, 06:19:33 am »
Yeah, same for me. I don't know why I didn't find it clear at first but now I like it.
And if we need a MirageOS description, that would be ".NAME→M Description" ?
I own: 83+ ; 84+SE ; 76.fr ; CX CAS ; Prizm ; 84+CSE
Sorry if I answer with something that seems unrelated, English is not my primary language and I might not have understood well. Sorry if I make English mistakes too.

#### Streetwalrus

• LV12 Extreme Poster (Next: 5000)
• Posts: 3821
• Rating: +80/-8
##### Re: Features Wishlist
« Reply #3219 on: July 29, 2013, 06:26:06 am »
I guess so.

#### ISSOtm

• LV3 Member (Next: 100)
• Posts: 56
• Rating: +4/-0
• Programming or playing games I've programmed
##### Re: Features Wishlist
« Reply #3220 on: August 02, 2013, 09:16:57 am »
Something nice would be an option to get the hexa code created by Axe after compilation ; I already created a program (using Axe ) to "decompile", but if Axe could do this it would be REALLY cool... Thanks...

I'm thinking to this because sometimes we can try to optimise the hexa by ourselves, and if Axe lets us edit the compiled code, we could do...
« Last Edit: August 02, 2013, 11:53:34 am by ISSOtm »
Programmer ("always start, never finish")

Currently owning :
- TI 84+SE (crashed by zStart )
- Computer for life

Voir aussi la version française.

Puzzle Master (if you hate mathemathics...)

Also on codewalr.us !

#### Streetwalrus

• LV12 Extreme Poster (Next: 5000)
• Posts: 3821
• Rating: +80/-8
##### Re: Features Wishlist
« Reply #3221 on: August 02, 2013, 09:20:49 am »
Just use the Asm( command, it's here for a reason.

#### ISSOtm

• LV3 Member (Next: 100)
• Posts: 56
• Rating: +4/-0
• Programming or playing games I've programmed
##### Re: Features Wishlist
« Reply #3222 on: August 02, 2013, 11:51:05 am »
No, I meant that it would be nice to EDIT the code generated by Axe
Programmer ("always start, never finish")

Currently owning :
- TI 84+SE (crashed by zStart )
- Computer for life

Voir aussi la version française.

Puzzle Master (if you hate mathemathics...)

Also on codewalr.us !

#### Sorunome

• Fox Fox Fox Fox Fox Fox Fox!
• Support Staff
• LV13 Extreme Addict (Next: 9001)
• Posts: 7920
• Rating: +374/-13
• Derpy Hooves
##### Re: Features Wishlist
« Reply #3223 on: August 02, 2013, 11:52:40 am »
you could use a hex-editor like calcsys
 THE GAMEAlso, check out my websiteIf OmnomIRC is screwed up, blame me!Click here to give me an internet!

#### ISSOtm

• LV3 Member (Next: 100)
• Posts: 56
• Rating: +4/-0
• Programming or playing games I've programmed
##### Re: Features Wishlist
« Reply #3224 on: August 02, 2013, 12:00:05 pm »
Ok, another app on my calculator ; but my archive is *nearly* full...
I mean, something included into Axe, because CalcSys does much more and then takes much more ARC than what my calculator can save...

Anyway, thanks for your suggestion, I'll try to download it (if not enough ARC I'll delete my new bank program )
Programmer ("always start, never finish")

Currently owning :
- TI 84+SE (crashed by zStart )
- Computer for life

Voir aussi la version française.

Puzzle Master (if you hate mathemathics...)

Also on codewalr.us !