• Grammer Feature Requests 5 1
Currently:

### Author Topic: Grammer Feature Requests  (Read 20305 times)

0 Members and 1 Guest are viewing this topic.

#### Sorunome

• Fox Fox Fox Fox Fox Fox Fox!
• Support Staff
• LV13 Extreme Addict (Next: 9001)
• Posts: 7917
• Rating: +373/-13
• Derpy Hooves
##### Re: Grammer Feature Requests
« Reply #75 on: February 13, 2013, 08:10:59 pm »
That is awesome to hear!
At least some language will be available on the 84pcse
* Sorunome glares at axe
 THE GAMEAlso, check out my websiteIf OmnomIRC is screwed up, blame me!Click here to give me an internet!

#### Xeda112358

• they/them
• Project Author
• LV12 Extreme Poster (Next: 5000)
• Posts: 4595
• Rating: +716/-6
• Calc-u-lator, do doo doo do do do.
##### Re: Grammer Feature Requests
« Reply #76 on: February 13, 2013, 08:47:27 pm »
Yeah, I will need to rewrite the graphics commands, but so long as it can run z80 code, the rest shouldn't be tough to convert.

#### Soulthym

• LV1 Newcomer (Next: 20)
• Posts: 17
• Rating: +1/-0
##### Re: Grammer Feature Requests
« Reply #77 on: April 26, 2013, 02:04:04 am »
Why not making a compiler that compiles only a part of the code from a label in the source to another. I believe it'd be awesome and maybe faster!

#### Xeda112358

• they/them
• Project Author
• LV12 Extreme Poster (Next: 5000)
• Posts: 4595
• Rating: +716/-6
• Calc-u-lator, do doo doo do do do.
##### Re: Grammer Feature Requests
« Reply #78 on: April 26, 2013, 06:20:20 am »
I am not exactly sure of what you mean, sorry Grammer 2 doesn't compile anything, so I am not sure where that would help out at the moment (but compiling is in the plans for Grammer 3). However, there are tricks for working with labels to make them faster, such as precomputing their location and storing them to point variables. This way, you don't need to constantly look up labels.

#### Soulthym

• LV1 Newcomer (Next: 20)
• Posts: 17
• Rating: +1/-0
##### Re: Grammer Feature Requests
« Reply #79 on: April 26, 2013, 01:06:43 pm »
Sorry, I meant making a way to pre-interpret a part of the code (like loading a part of the code interpreted in a temporary programm).
I think it would have to be done while lauching the programm.
With ".Token" as your way to locate what I call the Label, the structure may look like that:

Code: [Select]
.0:"name";Your code.Token ;It has to compile from the beginnig and until it reaches this point.;another code.Token ;It has to compile from the last token and until it reaches this point.[...]; End of the code.
I think this would improve the speed (comparing to interpreting) of the programms and use less of memory than compiling.

Sorry for my English, I'm a French student

#### persalteas

• Posts: 231
• Rating: +44/-4
• z80 poweeer
##### Re: Grammer Feature Requests
« Reply #80 on: April 26, 2013, 02:10:16 pm »
Sorry for interrupting the conversation (Soulthym ? Un étudiant français qui fait du Grammer ? Serions-nous deux ? ), but I have an idea...

I saw what you have done with your app 'Tutor' Xeda, and I thought it could be very useful in Grammer.

I explain:
Imagine the user sets a list of keycodes that would be automatically pressed the next time the calculator will be waiting for a signal from the keyboard, we could make:
• cheatcodes in games to control automatically the player/object-to-move
• We could use this to allow the player to make tiny macros in a game, without modifying the source code
In the same way, but much less useful because it can be easily done yet with getkey, create a function that records what key are pressed to make an history.

With this two functions, the user could record a manipulation and re-do it many times automatically.

#### Xeda112358

• they/them
• Project Author
• LV12 Extreme Poster (Next: 5000)
• Posts: 4595
• Rating: +716/-6
• Calc-u-lator, do doo doo do do do.
##### Re: Grammer Feature Requests
« Reply #81 on: April 26, 2013, 07:37:23 pm »
Okay, I think I see what you mean, soulthym. I don't have much code space left in the app for something that complicate.

EDIT: I accidentally clicked 'post' before finishing

@persalteas: Unfortunately, the OS doesn't parse key hooks during program execution unless you are at an 'Input ' command, Pause, or Menu(
« Last Edit: April 26, 2013, 07:39:00 pm by Xeda112358 »

#### Soulthym

• LV1 Newcomer (Next: 20)
• Posts: 17
• Rating: +1/-0
##### Re: Grammer Feature Requests
« Reply #82 on: April 27, 2013, 06:31:11 am »
No matter, maybe I'll be working on that during holydays^^(is it possible to have the grammer source in asm?)
Edit:Maybe it could be implemented in an alternative version of Grammer 3(like Grammer 3 precompiling version)
« Last Edit: April 27, 2013, 06:34:47 am by Soulthym »

#### Xeda112358

• they/them
• Project Author
• LV12 Extreme Poster (Next: 5000)
• Posts: 4595
• Rating: +716/-6
• Calc-u-lator, do doo doo do do do.
##### Re: Grammer Feature Requests
« Reply #83 on: April 27, 2013, 07:19:53 am »
I could probably make an alternate, unofficial version. It would probably have features removed, though, o make room.

The source is typically included with the download, but here is the current code that I have (attached). I am not sure if it works because it has been a while since I last looked at it.

#### Soulthym

• LV1 Newcomer (Next: 20)
• Posts: 17
• Rating: +1/-0
##### Re: Grammer Feature Requests
« Reply #84 on: April 27, 2013, 09:42:51 am »
Thank you a lot!
Edit: I just thought: Why not including plugins( like mimas does for example)?
« Last Edit: April 28, 2013, 02:57:24 pm by Soulthym »

#### Xeda112358

• they/them
• Project Author
• LV12 Extreme Poster (Next: 5000)
• Posts: 4595
• Rating: +716/-6
• Calc-u-lator, do doo doo do do do.
##### Re: Grammer Feature Requests
« Reply #85 on: May 08, 2013, 06:26:33 am »
I just thought: Why not including plugins( like mimas does for example)?
Sorry, I did not see this for a while. I was thinking of doing that, but I thought it would be too difficult. It would be really easy if the plugin was an app.

#### mdr1

• LV6 Super Member (Next: 500)
• Posts: 303
• Rating: +21/-2
##### Re: Grammer Feature Requests
« Reply #86 on: May 12, 2013, 02:15:23 pm »
@persalteas : et moi, je compte peut-être pour du beurre ? Certes, je n'ai absolument rien fait et ne connais ce langage que très partiellement... Mais je soutiens totalement le projet et développerai peut-être des trucs lorsque j'en aurai le temps !

@Xeda:
When we call a label, it needs time to find it. We can put the address in a variable, but it needs memory and a new name for each label. So why not add a new type of label being automatically parsed at the start of the program so that the application doesn't have anymore to parse it each time it is called ? For example, such a label could be declared as :

Code: [Select]
..LABEL
And when we do "call LABEL" or "Goto LABEL", the address will be stored for all the program execution.

PS : why not include to your .zip persalteas' tutorial ?
« Last Edit: May 12, 2013, 02:22:16 pm by mdr1 »

#### Xeda112358

• they/them
• Project Author
• LV12 Extreme Poster (Next: 5000)
• Posts: 4595
• Rating: +716/-6
• Calc-u-lator, do doo doo do do do.
##### Re: Grammer Feature Requests
« Reply #87 on: May 12, 2013, 02:29:47 pm »
@Xeda:
When we call a label, it needs time to find it. We can put the address in a variable, but it needs memory and a new name for each label. So why not add a new type of label being automatically parsed at the start of the program so that the application doesn't have anymore to parse it each time it is called ? For example, such a label could be declared as :

Code: [Select]
..LABEL
And when we do "call LABEL" or "Goto LABEL", the address will be stored for all the program execution.
Hehe, that is something that I am already working on (I even have had code for almost a 10 months in Grammer for this).
PS : why not include to your .zip persalteas' tutorial ?
I include a link to it in the readme, but I should remember to put the actual PDF in there.

#### mdr1

• LV6 Super Member (Next: 500)
• Posts: 303
• Rating: +21/-2
##### Re: Grammer Feature Requests
« Reply #88 on: May 12, 2013, 02:33:45 pm »
Hehe, that is something that I am already working on (I even have had code for almost a 10 months in Grammer for this).
Ans why not do so that this function is enabled for "." and disabled for ".." instead ? Labels which location doesn't have to be stored are rare and are used only when there's lots of SMC.
« Last Edit: May 12, 2013, 02:34:11 pm by mdr1 »

#### Xeda112358

• they/them
• Project Author
• LV12 Extreme Poster (Next: 5000)
• Posts: 4595
• Rating: +716/-6
• Calc-u-lator, do doo doo do do do.
##### Re: Grammer Feature Requests
« Reply #89 on: May 12, 2013, 02:36:50 pm »
Well, the code currently replaces the data with data not usable in the TI-BASIC editor (which is why I haven't officially added it). Otherwise, all labels would get replaced