0 Members and 2 Guests are viewing this topic.
I found a bug!PRGM:NAME.CAKEDisp t sub( >DecDisp {GetCalc("prgmTOK")}r >DecPRGM:TOKsub(The t before sub( is the token character.The two values are not the same.The t doesn't get two byte tokens correctly. (I think this is a bug... maybe I'm missing something)
There is still the app too large error with huge data files.I got one when I tried to include a 18000b file in a program.
Nope I am still using 1.2.2Is 1.3 stable enough to use now? (Last time I looked it still had several nasty bugs that made 1.2.2 the only viable option)
Quote from: E37 on May 21, 2016, 04:15:04 pmNope I am still using 1.2.2Is 1.3 stable enough to use now? (Last time I looked it still had several nasty bugs that made 1.2.2 the only viable option)Oh... not really, it still has those particualrly bad bugs... I think? I keep losing track of my progress because I don't revisit it very often, so I never get particulary far. I should really finish it off.
I (think) I found another bug!I am still using 1.2.2. The command, inData(byte,data,size) won't always work.inData(byte,data) works fine though.Here is some code...GetCalc("prgmNAME",100) sto AFor(X,0,99X to {X+A}:EndinData(3,A,1000) sto BDisp B >DecPause 1500Outputs 891 as the answer.Changing the 1000 to 100 makes the program work correctly.It seems that the command won't take a two byte number as an argument.
Ohhhhh! Ok! Could add a way to search backward (such as inData(byte,data)r)?It seems odd that you can search forward but not back (when you change it).Will fixing the "bug" break compatibility with programs that use the backwards searching?
If you don't would like to continue Axe Parser, I can do for you
You can program ask?!? Can you teach me? I just know the basics.