Show Posts

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 - LordConiupiter

Pages: 1 ... 12 13 [14] 15 16 ... 24
196
The Axe Parser Project / Re: Bug Reports
« on: September 06, 2010, 11:41:40 am »
I get pretty often the error: ERR:PIC MISSING, while my Pics are all in Archive. when I compile my prog right after it, the error seems to be solved, in other words: i don't get the error anymore. I haven't found any reason jet for the error, but it is possible this error only shows up when I just sent programs to my calc with TiLP.

197
The Axe Parser Project / Re: Axe Parser
« on: September 06, 2010, 11:38:45 am »
just out of curiousity: why do you use the 'space': 0x20 in the name of the parser itself, but in the compiled versions the 'zero': 0x00 after the name?

198
Axe / Re: Routines
« on: September 04, 2010, 02:36:50 pm »
wow! nice hint! I myself wouldn't have thought of it. I'm really gonna use this.

199
Axe / Re: Axe Boolean Logic
« on: September 03, 2010, 04:48:38 pm »
well, it was a theory, but it's proved to be wrong I see. let's think of a new theory. Or should we perhaps just ask Quigibo? :P

200
KnightOS / Re: KnightOS
« on: September 03, 2010, 03:43:16 am »
wow! this is really a nice project. but how will the libraries be created? and will there be some SDK for it?

201
The Axe Parser Project / Re: Bug Reports
« on: September 03, 2010, 02:15:17 am »
NO, i wasn't, it was just an example. I did something like this:
Code: [Select]
.B
L1->Q
1->N+1->O
1->{Q+O}->{Q+N}
which gives me a 37 ???

202
The Axe Parser Project / Re: Bug Reports
« on: September 03, 2010, 01:48:31 am »
did you take the 2 byte expression? or dit you only take {L5+4}? an adress is allways a 16 bit number, right?

203
The Axe Parser Project / Re: Bug Reports
« on: September 03, 2010, 01:46:06 am »
well, perhaps that's still working that way right now then.

204
Axe / Re: Axe Boolean Logic
« on: September 03, 2010, 01:40:58 am »
Axe boolean checks only the last bit of the byte pointed to I found out. to you get Yes only for odd numbers, and No for the even numbers :P
so b10101 And b0110 will be 0 And 0 for Axe, and b0101 And b0110 will be 1 and 0 for . so both numbers have to be odd.

Bool is just only the last bit of a byte!


correct me if I'm wrong, but this is what I thought based on my experiences with trying Bool-using statements as they all are...

205
The Axe Parser Project / Re: Bug Reports
« on: September 03, 2010, 01:37:20 am »
interesting, that sounds like a bug to me!  Thats not supposed to happen, its supposed to return the value of what you put in.  (unless that has changed to something else??)
what do you mean? It changed? I've no Interrupts enabled, and the only thing I know is that {L1} holds the right value, but {L5+4} doesn't...

206
The Axe Parser Project / Re: Bug Reports
« on: September 02, 2010, 03:57:27 pm »
copy the data from GDB1 or whatever data into a freeRAM area, and then u can modify it as much as u want!
you could also decide to use AppVars for all the data, which could be Archived and UnArchived whenever u want.

got another bug: I can't do the following:
Code: [Select]
1->{L1}->{L5+4}
and I would really like to, because I am told that it is much more efficient this way.

207
The Axe Parser Project / Re: Bug Reports
« on: September 02, 2010, 12:16:21 pm »
0.4.4 :(

208
wow! sound pretty neat! have you written 16 lvl grayscale routines for Axe? doesn't this consume too much CPU power?

209
The Axe Parser Project / Re: Bug Reports
« on: September 02, 2010, 10:58:08 am »
it's crashing and gives me a RAM clear, so it's nothing telling than just
Code: (screen) [Select]
Compiling
1st Pass   41%

210
The Axe Parser Project / Re: Axe Parser
« on: September 02, 2010, 07:05:52 am »
o no! please don't! I'm using this pretty much u know!

Pages: 1 ... 12 13 [14] 15 16 ... 24