August 14, 2020, 05:48:24 am

The shoutbox is currently out of service. Join us on Discord instead.
You can help CodeWalrus stay online by donating here.

WARNING: DO NOT UPGRADE your TI-83 Premium CE or TI-84 Plus CE to OS 5.5.1 and higher. It removes all compatibility with most games and removes ASM/C programming! DOWNGRADING IS IMPOSSIBLE. BE WARNED! Likewise, do NOT update your TI-Nspire CX past OS 4.5.0, else using Ndless and ASM/C programs will be impossible.

[TI-84+CE] ICE Compiler

Started by PT_, March 25, 2016, 08:14:17 am

Previous topic - Next topic

0 Members and 2 Guests are viewing this topic.

DJ Omnimaga

I'm happy to see SourceCoder support ICE. I liked SourceCoder since it seemed easier with it to work with the Minus symbol (as in, the smaller -, not the substraction one)


May 01, 2017, 09:24:59 pm #346 Last Edit: May 01, 2017, 09:27:57 pm by PT_
So well, yeah, time for some updates, or whatever you call it. As you might already know, I'm recreating ICE in C to make development faster, and easy add new features. This is coming along very well, I need to say. Currently numbers, variables, operators and parenthesis are supported (still need code for every operator), and more are coming soon. However, I'm running into a huge problem, and that are C functions. They are not like 'normal functions', such as not( and remainder( and so on. For the last type of tokens, I just add code for every possible argument type(s), rather than using the stack, like C functions need. However, this method simply doesn't apply to C functions, as they are supposed to take the input (arguments) from the stack, not registers etc. Thus, with the Shunting Yard Algorithm I'm doing, it is VERY hard to add C functions, and I'm not sure yet how to solve this. Let's take a look at some example:
det(2,det(15,X+2->X                 2 15 X 2 + det( det( X ->

det(2,det(15,X)+2->X                2 15 X det( 2 + det( X ->

det(2,det(15),X+2->X                2 15 det( X 2 + det( X ->

det(2,X+det(15),2->X             2 X 15 det( + 2 det( X ->

det(2,X,2*det(15))+3->X             2 X 2 15 det( * det( 3 + X ->

2*det(15,X)+3->X             2 15 X det( * 3 + X ->

det(2,X+2,1,2,3     2 X 2 + 1 2 3 det(

Left is the input, right is the input in infix notation.

Now let's take my last example. If I just parse them as normal, first the "+" is parsed, so X+2, but since the output isn't used in the next 2 elements (as an operator or function), the output is pushed to the stack, and that is where problems arise, it should not even parse the +. First 3, then 2, then 1 should be pushed, afterwards X+2 parsed and pushed, then the det( function will be called.

Again, I've no idea how to solve this, and I'm open for any ideas! :)

Progress: I've added icon and description support:


Very fancy!
What does the det( command do? (in ICE)
I've never finished a project, there is always a way to improve!
What's my calc's name? Convert $37 to decimal. Look up that element in the periodic table. Then take the abbreviation of that element and you have it!
Look! A slime!    <(^.^)>


I don't associate with associations


det( is the start of a C function, for example det(0 is "Begin", det(5 is "FillScreen" etc.


I've added SetBASICVar( which... sets a BASIC variable! :D


DJ Omnimaga

OMG does this mean external saves are now supported? O.O Also does it set to real vars?


Quote from: DJ Omnimaga on May 08, 2017, 06:40:33 pm
OMG does this mean external saves are now supported? O.O Also does it set to real vars?

You can now store integers to the real BASIC variables A-theta :)


May 08, 2017, 07:43:57 pm #353 Last Edit: May 08, 2017, 07:50:19 pm by _iPhoenix_
That's great, but is the progress bar through the "Successfully compiled" a gif glitch?

EDIT: Perhaps add the ability to edit/read BASIC programs or AppVars (i.e. files), token by token.
EX: editFile(*file*, *token number, from start*, *token to change to*)
EX: readFile(*file*, *token number, from start*)
EX: checkFile(*file*, *token number, from start*, *token to check for*
The last one would return 1 if the token indicated in the specified file was the same as the token to check for.

Perhaps make 'token' byte, even, that would be easier to handle, I'd think (but take what I think with a grain of salt)

Please spam here:

"walruses are better than tuxedo chickens, all hail the great :walrii:" ~ me
Evolution of my avatar:


May 08, 2017, 11:24:36 pm #354 Last Edit: May 08, 2017, 11:29:52 pm by PT_
I'm SUUUUUPPEERRRRR excited to announce this very great news:

It redirects you to a page at Cemetech Learn, where I will put all the needed information, and Tips and Tricks! :D

DJ Omnimaga

Nice :D. Also I'm happy to see real vars supported. Are their content preserved when entering or exiting an ICE program, though (unlike Pic4)? :P


As long as other BASIC programs don't overwrite them ;) I'm working on GetBASICVar( as well, to eventually get the highscore :D

DJ Omnimaga

Yeah I was mainly wondering, so that using BASIC code, people can do things like this:



I saw that the program you used had the "getBasicVar()" as a token. Is that due to the fact that you are programming it in C?
Please spam here:

"walruses are better than tuxedo chickens, all hail the great :walrii:" ~ me
Evolution of my avatar:


No, that is because ICE didn't had the possibility to interact with BASIC programs, but now you can.

Time for some quick updates about my C version: I've implemented all the operators, and added code for functions, which work fine, I only need to add them :P Chaining things also work, so the only thing I need to do is doing weird stuff with C functions and get that working :)

Powered by EzPortal