Author Topic: Axe Parser (Read 493394 times)

DJ Omnimaga · « **Reply #570 on:** May 10, 2010, 10:57:32 pm »

I think if cross calc compatibility is broken with certain commands, there should be a warning in the doc for each commands. If it just breaks compatibility between 6 and 15 MHz mode (like I think), then the command list should simply warn to not use the 15 MHz command on a regular 83+ or in 6 MHz mode and to not use the 6 MHz commands in 15 MHz mode (use Normal beforehand).

calc84maniac · « **Reply #571 on:** May 11, 2010, 12:27:00 am »

I actually switch to 6MHz before grayscale display in Chip's Challenge. It's not an uncommon method.

meishe91 · « **Reply #572 on:** May 11, 2010, 12:29:30 am »

Just as a quick side question: Does 15MHz have any advantage over 6MHz besides for speed?

Quigibo · « **Reply #573 on:** May 11, 2010, 12:30:48 am »

Quote from: calc84maniac on May 11, 2010, 12:27:00 am

I actually switch to 6MHz before grayscale display in Chip's Challenge. It's not an uncommon method.

Alright, that reinforces my thoughts. If you want 15MHz grayscale, you will have to switch to 6MHz manually to display it. Even if some new programmer accidentally tries it in the 15MHz mode, it doesn't crash the calc or anything, it just displays funky garbage on the screen, so its not a big deal.

DJ Omnimaga · « **Reply #574 on:** May 11, 2010, 12:31:57 am »

ooooh ok, like when I beta tested xLIB on a SE back in its early app days

I am kinda glad it won't crash.

Will the 6 MHz command remain DispGraphr btw?

ztrumpet · « **Reply #575 on:** May 11, 2010, 07:44:42 am »

Quote from: calc84maniac on May 11, 2010, 12:27:00 am

I actually switch to 6MHz before grayscale display in Chip's Challenge. It's not an uncommon method.

That makes it sound a lot better. I now think this is the best method.

Would DispGraph automatically put it in 6mhz, or would the user have to do this themselves?

Quigibo · « **Reply #576 on:** May 11, 2010, 12:37:47 pm »

I could have it do that for you, but I'd rather the programmer do it themselves since those making 6MHz games won't want to have the extra size increase for a feature they're not using.

DJ Omnimaga · « **Reply #577 on:** May 11, 2010, 12:44:54 pm »

Does calling the grayscale from a sub-routine slows it down a lot? If not, then I guess this would be the best solution. Otherwise, my big concern ATM is the increase in file size due to having to use Normal:Dispgraph^r:Full instead of Dispgraph^r. With about 20-30 grayscale commands total, would the increase in code size be considerable?

Quigibo · « **Reply #578 on:** May 11, 2010, 12:51:43 pm »

No, a subroutine is negligible unless its called over 9000 times per second. Typically, the screen updates around 20-60 times a second.

DJ Omnimaga · « **Reply #579 on:** May 11, 2010, 12:53:53 pm »

Ok thanks. I guess it shouldn't be that bad, then.

ztrumpet · « **Reply #580 on:** May 11, 2010, 04:08:02 pm »

Quote from: Quigibo on May 11, 2010, 12:37:47 pm

I could have it do that for you, but I'd rather the programmer do it themselves since those making 6MHz games won't want to have the extra size increase for a feature they're not using.

Ah, very good point!

I like how things are headed.

Full and Normal translate to one byte of code more each, right?

Quigibo · « **Reply #581 on:** May 11, 2010, 07:08:39 pm »

2 bytes in the source code if you include the colon. The actual size in the executable is 9 and 3 bytes for Full and Normal respectively. Full is a little larger because it also returns if the calculator was successful in running 15MHz mode, which is used to distinguish what type of calculator is being used.

ztrumpet · « **Reply #582 on:** May 11, 2010, 10:15:19 pm »

Ah, okay. Can there be a Full that doesn't return, so it would be smaller and faster if you want it to be? I'm all for compiled size and speed.

Thanks!

kindermoumoute · « **Reply #583 on:** May 15, 2010, 12:01:55 pm »

I am French, I love what you made, I'm still learning axe parser!

DJ Omnimaga · « **Reply #584 on:** May 15, 2010, 12:05:21 pm »

Hi and welcome here. Glad you like it!

Author Topic: Axe Parser (Read 493394 times)

DJ Omnimaga

Re: Axe Parser

calc84maniac

Re: Axe Parser

meishe91

Re: Axe Parser

Quigibo

Re: Axe Parser

DJ Omnimaga

Re: Axe Parser

ztrumpet

Re: Axe Parser

Quigibo

Re: Axe Parser

DJ Omnimaga

Re: Axe Parser

Quigibo

Re: Axe Parser

DJ Omnimaga

Re: Axe Parser

ztrumpet

Re: Axe Parser

Quigibo

Re: Axe Parser

ztrumpet

Re: Axe Parser

kindermoumoute

Re: Axe Parser

DJ Omnimaga

Re: Axe Parser