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 - Xeda112358
Pages: 1 ... 68 69 [70] 71 72 ... 317
1036
« on: March 19, 2013, 06:51:24 am »
Then it probably is a short circuit somewhere o.o They should probably last years unused, months with typical use, and even a month or two with using it quite often.
1037
« on: March 18, 2013, 01:11:25 pm »
Oh, I see. Do you store the input string in RAM somewhere? For example, do you have "func -h" stored somewhere in RAM as you type? If so, you can just pass a pointer to the arguments in HL or something. So your interpreter reads "func ", and as soon as it hits the end of the input or a space, it searches for the function, and passes a pointer to whatever follows. This way, each function completely handles its own inputs, like stings and file names. (This is how I did it in FileSyst, too.)
1038
« on: March 18, 2013, 01:02:09 pm »
 I just checked my email. Cool! The first game is like Whack-a-mole (in English) though the rules might be a little different. I will try to finish it soon!
1039
« on: March 18, 2013, 12:39:20 pm »
Nice o.o Maybe you can make it set or reset bits as actual flags. For example, you can set IY to point to a bunch of flags, and -a would reset bit 0, +a would set bit 0. Then bit 7,(IY+0) is the 'h' flag so the program knows that its 'help' code should be called.
Since it is your OS, you can control the IY register without any harm o.o
1040
« on: March 18, 2013, 07:59:58 am »
Oh, sorry. Also, cool o.o So does this mean functions will have a 'help' field, where the function describes what it does?
1041
« on: March 18, 2013, 07:12:17 am »
Yes, or add a ClrIO command (to clear the prompt screen), maybe add the '?' command for help?
1042
« on: March 18, 2013, 07:05:04 am »
Yes, that is the trick  Then, whenever an argument is read, it shifts the bits out to see if it should be read as indirection.
1043
« on: March 18, 2013, 07:02:10 am »
I don't consider that cheating, but rather awesome o.o
1044
« on: March 18, 2013, 06:54:05 am »
Yeah, that is why I didn't upload anything, either. Also, how did you make such an awesome intro? o.o I made a picture editor thing because drawing on the graph screen using the OS is kind of annoying.
1045
« on: March 18, 2013, 06:49:33 am »
That looks absolutely gorgeous! I had no clou the graphics could be so awesome! I am so used to the z80 clacs, I didn't even think of doing an intro screen like that o.o
1046
« on: March 18, 2013, 06:38:01 am »
Awesome! I should really look at this OS starter kit thing >.> Would you like some routines for reading strings of numbers so the user can pass arguments? Or are you creating that yourself? 
1047
« on: March 18, 2013, 06:34:07 am »
Ok buddy, i'll check which data you need to pass and tell you that soon =]
Okay, thanks! What if you did ind2() \ ind1()?  That's a cool idea, though, and definitely something that will make writing more complicated games easier
Yes, that is valid, and it would cause the next argument to be indirection, then the one after that is normal, then the argument after that is indirection. The way this could be useful is when passing arguments to calls where you can force a call to use indirection. Though in that case, something like ind1() \ ind2() might be better.
1048
« on: March 17, 2013, 11:27:38 am »
I like option 2 the best, because that seems more automated and the user still gets to see that it is in fact asmdream doing the work. Also, Update: I removed the keyMask port. Really, it isn't needed since it was actually faster to just scan all of the keys without checking if it needed to be read. In fact, I optimised the key scanning routine to be even faster and smaller than what I originally thought it could be: ld bc,0701h
ld a,$FE ;test the keys
ld hl,saveSScreen+key0
KeyUpdateLoop:
out (1),a
rlca
nop
ini
jr nz,KeyUpdateLoop
I replaced the byte with something else, explained later. For now, the next update is indirection: I added in the ind1() and ind2() instructions. They have more complicate abilities, but the easiest way to use them is something like: ind2()
lda(addr1,indirect)
ind2() says that the second argument passed to the processor will be read as indirection. How that may get complicated is with something like this: ind2()
inc(addr1)
inc(indirect)
The first increment works as normal, but the second one has indirection. Internally, ind() instructions rotate a bit into an indirection counter (up to 8 bits). I did this on purpose, instead of simply setting bit 0 or bit 1 accordingly. It is just as easy to rotate the bits in, so why give the extreme coder the ability to use all 8 bits? With this in mind, you can make both arguments in an instruction read as indirection: ind1()
ind1()
lda(indirect,indirect)
The way that works, is first a bit is rotated in, then another bit is rotated in, leaving the lower 2 bits of the indirection byte set, so the next two addresses will be computed as indirection. Even better is that the indirection byte is what has replaced keyMask, so you can control indirection a little more and save bytes in some cases. The attached file has an updated Jade.inc with all of the supported instructions, as well as some documentation, a 'readme' an example, and the associated asmdream macros and equates that have been updated. No new screenies yet, sorry 
1049
« on: March 17, 2013, 09:19:59 am »
If you want to have the ASMDream compiling screen display, that would be fine! If not, that is fine with me, too, and I could handle error messages and the goto feature if needed.
1050
« on: March 14, 2013, 11:13:39 am »
Was one of those entries mine? If so, Stefan won unless you all have a cruel sense of humor  My entry just said "This program does nothing. C'est tout. Tchüss!" EDIT: Also, Mr. Bendl was working on it (he is from TI-Basic Developer)
Pages: 1 ... 68 69 [70] 71 72 ... 317
|
Show Posts