Author Topic: Axe Parser (Read 552498 times)

indubitably · « **Reply #390 on:** April 11, 2010, 11:37:25 am »

I feel like an idiot, somehow, when I first downloaded axe, I left out the documentation file and I have had the most trouble using axe. I just downloaded the update, read the file, and wow that helps sooooooooooooo much.

Raylin · « **Reply #391 on:** April 11, 2010, 11:43:50 am »

Eh.
Noobish mistake.

It happens.

ACagliano · « **Reply #392 on:** April 11, 2010, 11:54:36 am »

Quote from: Raylin on April 11, 2010, 11:43:50 am

Eh.
Noobish mistake.

It happens.

He's right. You will learn eventually never to download anything without documentation.

indubitably · « **Reply #393 on:** April 11, 2010, 12:49:29 pm »

yeah I thought the all the documentation everybody was talking about was the optimizing tips and the general help.

Raylin · « **Reply #394 on:** April 11, 2010, 12:53:45 pm »

Naw.
It's the HTML file that is included in the update.

DJ Omnimaga · « **Reply #395 on:** April 11, 2010, 01:23:30 pm »

Quote from: ACagliano on April 11, 2010, 11:54:36 am

Quote from: Raylin on April 11, 2010, 11:43:50 am
Eh.
Noobish mistake.

It happens.

He's right. You will learn eventually never to download anything without documentation.

The sad part though is that in some cases, when you download something, there's no doc provided or the doc is separate from the binaries

Oh well, that happens ^^

And glad to see new update! I migth give the grayscale commands a try at one point. The way I see it it works like Reuben Quest but using overwrite logic instead of XOR, right?

About the program file access, does this means there's now a way to use the data from programs, such as external levels and map data? Can the data be retrieved directly from archive without unarchiving the program first? If it's possible to retrieve data from external programs, could someone post a routine on how to run sub programs?

Also it might be a good idea to include the stuff explained in http://ourl.ca/4050/84944 in the doc, because in the doc, there's no indication about v and prgm prefixes and the grayscale command isn't explained into as much details.

Raylin · « **Reply #396 on:** April 11, 2010, 02:42:11 pm »

QUESTION: What can you do with the accessing of programs in Axe?

DJ Omnimaga · « **Reply #397 on:** April 11, 2010, 02:53:07 pm »

What I thought about is accessing archived data like tilemaps or NPC convos (text) from our main program, so basically, we can have games that takes more than 24 KB of memory by taking advantage of the Flash ROM.

calc84maniac · « **Reply #398 on:** April 11, 2010, 03:58:57 pm »

hmm, I doubt reading from flash is supported

Quigibo · « **Reply #399 on:** April 11, 2010, 04:03:44 pm »

While you can run executable code from another program, its way too dangerous, so I'm not going to support it right now. But you can with assembly commands. Anyway, the main usage is for reading and writing to programs. Like if you made a new program with HELLO as the first line, you can read that just like you read an appvar, and also write over and modify it. The advantage is that appvars are not easily editable. So if you want to make an external level pack come with your game, you might want to consider using a program instead so levels can easily be edited.

Raylin · « **Reply #400 on:** April 11, 2010, 06:30:46 pm »

I keep failing at this...

Okay, so I have:

Code: (prgmA) [Select]

:"RAWR

Code: (prgmB) [Select]

:"prgmA"->Str1
:Disp {Str1}>Frac

Why is this not working?

Builderboy · « **Reply #401 on:** April 11, 2010, 06:35:06 pm »

Methinks because strings in Basic programs are not the same as strings in compiled axe programs? Not sure...

ACagliano · « **Reply #402 on:** April 11, 2010, 06:35:09 pm »

You can't display a program. You have to select it, then read the bytes of that line from it, then display THAT.

Am I right?

Raylin · « **Reply #403 on:** April 11, 2010, 06:44:49 pm »

If this is true, how would you read and write data from programs in Axe?

SirCmpwn · « **Reply #404 on:** April 11, 2010, 07:06:46 pm »

Quote from: Raylin on April 11, 2010, 06:30:46 pm

Code: (prgmA) [Select]
:"RAWR
Code: (prgmB) [Select]
:"prgmA"->Str1 :Disp {Str1}>FracWhy is this not working?

Take off the {}, its implied. Also, remove >Frac, unless you just want the first character.
Also, I'm not entirely sure if the prgm token will show right, you may need to spell out p-r-g-m

Quote from: Raylin on April 11, 2010, 02:42:11 pm

QUESTION: What can you do with the accessing of programs in Axe?

* SirCmpwn pokes calc84maniac to re-make OTBP Assembler with Axe

Quote from: Raylin on April 11, 2010, 06:44:49 pm

If this is true, how would you read and write data from programs in Axe?

You read the data, store it somewhere. You take the data from where it is stored, and write it.

Author Topic: Axe Parser (Read 552498 times)

indubitably

Re: Axe Parser

Raylin

Re: Axe Parser

ACagliano

Re: Axe Parser

indubitably

Re: Axe Parser

Raylin

Re: Axe Parser

DJ Omnimaga

Re: Axe Parser

Raylin

Re: Axe Parser

DJ Omnimaga

Re: Axe Parser

calc84maniac

Re: Axe Parser

Quigibo

Re: Axe Parser

Raylin

Re: Axe Parser

Builderboy

Re: Axe Parser

ACagliano

Re: Axe Parser

Raylin

Re: Axe Parser

SirCmpwn

Re: Axe Parser