So i was inspired by SourceCoders' broken Basic Optimizer function, and i thought about making one on the calculator, so you could optimize your Basic Programs without having to transfer them to the computer for any utility.  I quickly wrote up some code in Axe, and the optimizations have started  Currently it has support for:

Ending Parenthasis
Ending Quotes
Devlar
Powers of 10
Squared and Cubed optimizations

And there is plans and psedocode for

Implied multiplication
=0 into Not(
Negative/Positive cancellation

any other ideas of simple find and replace optimizations that i could put into the optimizer?  Obviously i cant do some of the complicated stuff, but there are some good simple replacements that can make a big difference.  And note that it ignores Strings completely Strings Should not be changed ^^.  And there also might be an option on whether to erase empty lines or not.  Some people like to keep them for readability during development, and then maybe want to take them out later.

what do you mean sub(.? And what do you mean by a logic simplifier?

Wow i didnt know about that Sounds good

And i'll have to see if i can get the logic simplifier to work, it might be tricky but i think i *might* be able to get it working.  i will have to do some research

Thats really cool!  Hmm it might be very tricky to implement tho, since it would have to do some pretty weird calculations to determine A and B, and if 1 expression is equivalent to another.  And it only works if there are 2 expressions present in the logic line.

For now i think im going to stick to simple find and replace, then go into more detailed optimizations.  Maybe things like reordering expressions so that expressions with more parenthesis are at the end of the line.  Like optimizing

Dim(L1)+1

to

1+Dim(L1

Another good one would be to auto-expand calculations if they are factored (ex. 5(B+3)+A-(5+W)=5B+15+A-5-W=5B+A-W+10).

But this is a cool idea Will really help some people.

@Deep Thought
I've noticed lately that when you're posting code that there appears an empty code box and then the code itself below the box. Is there any reason for that or am I the only one experiencing it?

Yeah, it's on purpose since I occasionally need to use something like ₁₀^(, which wouldn't show up well in code tags.

Another good one would be to auto-expand calculations if they are factored (ex. 5(B+3)+A-(5+W)=5B+15+A-5-W=5B+A-W+10).

Thats also a good idea, i will have to see if its doable.  Sometimes it wont actually result in less tokens tho, so i will have to remember that.  Also i would need to write a number to token converter, working with all these tokens is tough business

Quote from: meishe91 on September 01, 2010, 06:23:25 pm

Another good one would be to auto-expand calculations if they are factored (ex. 5(B+3)+A-(5+W)=5B+15+A-5-W=5B+A-W+10).

Thats also a good idea, i will have to see if its doable.  Sometimes it wont actually result in less tokens tho, so i will have to remember that.  Also i would need to write a number to token converter, working with all these tokens is tough business

For the num>token thing, I think you can first display it on the screen (with >Dec), then get the tokens from TextShadow (I think it's L5).

Yeah, auto-expansion might not be a good idea, since most factored expressions are shorter than their expanded forms

Something like 99(99+A would distribute into 9801+99A which is 1 more token And thats a really clever idea with the Screen trick!  Im going to go put that in my subroutine

Remember to change the screen immediately afterward, or else the user's gonna get confused by random numbers on the screen