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 - Quigibo
Pages: 1 ... 23 24 [25] 26 27 ... 135
361
« on: June 16, 2011, 04:57:16 am »
Actually, that's something I can fix. I haven't updated the token replacement chart for ages since no one's requested any new ones. I'll see what I can do for the next update.
362
« on: June 15, 2011, 07:19:39 pm »
I can't seem to replicate that no-axe-source bug. I'm looking at the source code where this problem would be, but I don't see anything suspicious. Can someone explain starting from a RAM clear how to reproduce it? It probably depends on what's in the program or something, I've tried 5 different BASIC programs (and all together) and none of them do it.
363
« on: June 15, 2011, 04:46:57 am »
Ah yes I found it thanks. I was storing the "Is File" boolean in a variable instead of the operator stack and that made file references non-nestable. I'll have that fixed next version.
364
« on: June 15, 2011, 12:21:42 am »
I think its more likely that {Y1+offset} evaluated to 0 meaning it would have copied the entire 65536 bytes of RAM which would certainly cause an instant crash.
365
« on: June 14, 2011, 11:51:29 pm »
Just wanted to give everyone a quick update on progress. This is day 6 of the rewrite. I can now parse simple programs and have data, labels, variables, and gotos working correctly. Though I still need to rewrite subs, interrupts, internal subroutines, and axioms. So currently, I cannot compile any large programs, but I'm almost at the point where I can. There is at least one extra MAJOR convenience feature that was requested a long time ago that will finally make it to the update, but I won't spoil what it is yet.  I still have no idea when it'll be finished because of all the inevitable unexpected issues to come, but hopefully before the end of the month.
366
« on: June 13, 2011, 11:22:35 pm »
Haven't posted in this section for a while... Sunburn - MuseReally cool music. I actually learned it for piano yesterday. In Transit - Albert Hammond Jr.I just really like the song. Chelsea Dagger - The FratellisSuper catchy Her Morning Elegance - Oren LavieAmazing music video! And really nice song too. New Soul - Yael NaïmAlso super catchy and really makes you feel good.
367
« on: June 12, 2011, 02:36:47 am »
Reading labels as values is for sure coming in the next version. But its mostly for Axioms that require labels as arguments because there really isn't any other use for them since you still can't jump to arbitrary values due to leaks and unsafe code. I think I might have a way to allow programs to exit anywhere soon, but I already have to rewrite half of the parser from scratch so I doubt I'll have time next version. For those other assembly commands, most of them are really too specific and low level for any general use. Runer112 actually made an LCD Axiom LCD Kit that does most of those already and you could certainly design a port axiom to allow arbitrary port writing, I just don't see the purpose of that for the average game.
368
« on: June 11, 2011, 03:36:37 pm »
Those return different things.
Something->{E} will return E instead of {E} after the store since E is variable. On the other hand, if you store to a constant location like Something->{L1} then it will return {L1} instead of L1. This strange behaviour is only because it leads to massive optimizations in the executables.
369
« on: June 11, 2011, 03:33:30 pm »
It could be related to Crabcake if you're using that. I'm not sure how it works exactly, but its possible it could be conflicting with the archive reading commands since the memory mapping is different.
370
« on: June 11, 2011, 01:42:59 am »
This is a really simple one. When an interrupt is called, interrupts are automatically disabled. So you don't need to start the interrupt routine with DI. They are disabled automatically already... there is a di at the start of the interrupt routine. Is there some bug with that? Also, about those archive reading commands... archive reading isn't as useful as it should be due to those sector boundary issues. For instance, you can't reliably iterate a tilemap in archive because there is a small chance it could overlap between a sector boundary and iterating over it would add a "glitch byte" to the map since each sector adds an extra byte in front. Although I guess you could modify those routines to take that into account, that might work since you can't read more than 64 consecutive kilobytes anyway.
371
« on: June 11, 2011, 12:13:21 am »
Oh yeah, I forgot to mention that! Bit 3 controls if auto backups should be turned on or not when using the CompileOP1 entry point. Axe always saves the current setting configuration when it exits so if you want it to restore the original settings, you'd have to read and then modify the Axe appvar, which contains a single byte: the setting. Maybe I'll change that for 1.0.0 though since I see how that can be annoying.
372
« on: June 09, 2011, 11:17:12 pm »
Tower defense games are programming games in that sense. This one is good too: Stick Ranger
373
« on: June 09, 2011, 07:55:32 pm »
That includes sprites too though. You can't do:
Pic1+8->Pic2
Pt-On(0,0,Pic2)
[]->Pic1
However, you could do:
Pt-On(0,0,Pic2)
[]->Pic1
Pic1+8->Pic2
And you can always declare the sprite first like Axe has been doing so far:
[]->Pic1
Pic1+8->Pic2
Pt-On(0,0,Pic2)
374
« on: June 09, 2011, 07:17:11 pm »
Yeah, I was thinking about that, but it could take an infinite amount of passes to resolve the constants, like:
oB->oC
oA->oB
5->oA
The first pass can assign A, and B the second pass, but C would not be identified then. I'm going to have to re-think a lot of this actually and figure out some rules that will make this easy to implement... probably something like the above example would be illegal. Perhaps I will make a rule like you cannot store to a static unless everything on the left hand side is declared already.
375
« on: June 09, 2011, 06:36:34 pm »
Would it be possible to chain variable declarations, like:
L1->oMyVar1+2->oMyVar2+1->oMyVar3
Would make it a lot easier to change the size of a variable or add/remove variables during development.
Ooo! That's a cool idea. You can definitely chain them line-to-line but I'll see if I can add it all on the same line.
Pages: 1 ... 23 24 [25] 26 27 ... 135
|
Show Posts