This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Messages - nemo
Pages: 1 ... 32 33 [34] 35 36 ... 82
496
« on: November 16, 2010, 05:24:59 pm »
oh, i just realized there *is* a save state. it just didn't save for me due to the Basic error.
edit: disregard my bug error for non-DCS users. if you do use DCS, i recommend disabling hooks because that seems to be the problem.
497
« on: November 16, 2010, 05:17:44 pm »
i hate to do this, but i found a bug  if you press mode without having already earned a secret bonus, you get an error. also, i wish there was a save state
498
« on: November 16, 2010, 05:02:47 pm »
it's all programmer's choice, here. personally, i don't understand why you would even indent on calculator source code. i don't even comment on my source for calculators.
499
« on: November 16, 2010, 04:59:36 pm »
yesss!
500
« on: November 16, 2010, 04:58:13 pm »
i guess it's a programmer's choice.
regardless, the string bug could easily be handled with this pseudocode:
if read_byte == quotation_token
repeat read_byte == quotation_token
read_byte = next_byte
end
end
that way, it ignores everything within quotations.
501
« on: November 14, 2010, 04:42:27 pm »
If those 7 programs must be in RAM, compiled, you can always use a group 
Anyway, for KnightOS, Sir plans to have no RAM-based file system anyway, so RAM clears are less of a problem.
RAM clears won't even be a problem, they'll be standard. i remember Sir saying RAM will be cleared everytime you turn off the calculator.
502
« on: November 14, 2010, 03:50:15 pm »
D&D?
edit: and what for?
503
« on: November 14, 2010, 03:17:21 pm »
15. all programs are deleted upon turning off the calculator.
16. the LCD refreshes at a maximum rate of 3 FPS.
17. only a 32x32 chunk of the LCD is used. the rest is "unnecessary"
18. an 8x8 sized Font is used, making 16 the maximum number of characters displayable. there is no small font.
19. all programs are written in KBasic. KBasic commands include:
-statistic regressions
-addition, subtraction.
- and that is all.
504
« on: November 13, 2010, 10:03:06 pm »
505
« on: November 13, 2010, 09:51:44 pm »
nice!
however, could it be possible to change the Disp command? having Disp X,Y where X is a row 0-7 and Y a column 0-15 is confusing, since X usually increases as you go horizontally to the right, not vertically downwards.
506
« on: November 13, 2010, 09:43:35 pm »
pretty much. recursion is confusing, but it produces short code. quicksort using for and while loops is not so eloquent.
Recursion can be very nice... but it also can be very memory hungry.
memory's cheap
507
« on: November 13, 2010, 09:42:15 pm »
hmmm.. do it in segments?
do 1/5 of the program, make an Appv TEMP1, copy 1/5 of the new program's data to TEMP1, archive it.
repeat for TEMP2, TEMP3, TEMP4, TEMP5.
copy each appvar to the new Program variable separately.. you get the idea.
the problem with that is it 1) it'll take forever due to the archiving and 2) frequent use will wear out the archive.
so, another suggestion, loop through the program data calculating how many spaces you need to add in.
create a temp appvar with enough space to compensate for the extra bytes.
loop through again, this time copying the program data to L3, adding in spaces as necessary. once you reach 768 bytes, copy the L3 data to the new appvar
repeat until all the data is copied.
transfer the appvar to the program var
delete the appvar.
i know, it doesn't solve the memory problem. but cmon. just put a note in the readme to have:
2 * [program_size] + [autoOp_program_size] +[arbitrary_number_like_1000] bytes available in ram.
508
« on: November 13, 2010, 09:19:29 pm »
haha yeah, it's really confusing at first but i'm beginning to grasp it. here is a good tutorial about it. it's also pretty funny.
509
« on: November 13, 2010, 09:18:03 pm »
My question is how are you going to run the program after you add in the spaces? And the only reason the AutoOptimization program is able to edit programs is because it never *increases* the file size, which is incredibly difficult.
as the program runs, count the number of spaces you add in. after you're done, create a temporary appvar. copy all the data from the program you edit to the appvar. then, create the same program variable that you edited with its original size, plus the amount of spaces you added in. copy appvar data to the program variable.
510
« on: November 13, 2010, 08:53:20 pm »
pretty much. recursion is confusing, but it produces short code. quicksort using for and while loops is not so eloquent.
Pages: 1 ... 32 33 [34] 35 36 ... 82
|
Show Posts