okay so I wanted to make an update of my old refraction program in hybrid-basic, because the old one was just ewh, so I did that and well it is working as it should, but it's soooo slow (mostly the input thing), I don't think it's worth uploading to the archives at that speed even though it's much prettier than the one that I currently have up there. I was wondering if anybody could think of ways to make it better/faster? Anyways here's the code for the whole thing
edit: Okay, I fixed the places where there were two branches that converged to the same place, and added all the ends to the if conditions that were lacking one (that I could find) updated the code below too (already looks much better)

Code:

Okay okay okay.

This code.. Not going to work.

1: If you use an If:Then, you need an End.
2: If you use an If:Then, you never use a Goto to escape it
3: If you only need to do one thing after a conditional check, you don't need Then



Code:


to


Code:


No need for a goto, as the code is going that way anyways.

Any time the calculator comes across a Goto, it starts the program over from the top and scans the program until it finds the corresponding Lbl.

Let us know what you have after you make some of these changes.

In cases like that where the two branches of a conditional simply assign different values to the same variable, you can use something like this:

Code:


But yeah, at the very least, the conditionals definitely need cleaning up to use End's. Right now, your program is leaking tons of memory and should slow down over time and eventually crash.

I am going through the code fixing these and I am wondering, if there are more than two branches of a conditional that assign different values to the same variable, like this

Code:

could the same technique be used, and if so, how?

This is how I'd do it:

Code:

Return is better than stop in most cases, because it will bring you back to the shell you ran the program in.
If K=13, then it does 5-4, which is 1. If K=12, it does 5+8, which is 13. If K=11, it does 5+4, which is 9. If K doesn't equal any of those, then it just stores 5 to theta.

All of the Thens and Elses can be omitted because there are only one line codes after the conditionals. Plus, the Lbl/Goto can be omitted by moving the 5->θ higher. So,

Code:

can be

Code:


However, if you want to combine all of these statements into one expression, you can use the following:


Code:


This can be optimized further by factoring out a 4.


Code:

Exactly what does this program do? I have a feeling you can get this under 250 bytes if you rewrite it.

this program just solves the refraction formula (finds the missing variable, once 3 are entered) and yeah i'm sure it could be very small, but I also want it to display whats happening to a beam of light Under these circumstances... and it also check for the crit angle, if it finds one it will indicate what it is, and if your incident angle is bigger than this angle, it will bounce off as it would irl... its basically a very complete program for a fairly simple thing, besides, by the time these people are done looking at it, it will be optimised down to 0.5 bytes

I did that, It's not in the new code, but it's done

Bump, changed a few things in the code and updated the code in the first post, if anyone thinks of any optimizations that could be brought to the prog, please tell me so I can make these changes and make the prog better

It looks like you're using the LinReg method to convert numbers to strings; since you're using libraries anyway you may as well use the built-in det(1,num) command to convert a float to a string.

hmmm I thought this feature was only available to monochrome calcs, I'll try it out, what string will it be stored in, since it isn't in the args...

I actually don't know if it works with color calcs, since I don't own one myself; I just assumed all monochrome features were also available in color. Sorry about that...

There is no reason why any non-graphical-oriented command from monochrome calcs should have been removed on color ones. If anything, it's the opposite.

I know, maybe it is available, its because there is no mention of storing vars to strings in the sdk, but either way, idk how to use it xD

DJ_O, lirtosiast, mr womp womp: The NumString function was not carried over from Doors CS to Doors CSE, because the former offers the Celtic III libraries (among others), while the latter offers a fixed and optimized version of the Celtic 2 libraries.

mr womp womp: Further optimization: none of these statements requires the Then and End, because they're conditionals with a single conditionally-executed statement:
Code:

Fixed this, there used to be more statements in between those conditions, when those were removed, I didn't notice the thens and ends were no longer needed.

Code:

In this code, I believe the Gotos cause a memory leak since they leave an if statement before the end, just wondering if this can be fixed using a while loop like this, to have a loop in a loop basically.

Code: