Variables are all statically allocated. Proc2.b and Proc3.a are separate 
locations.
No real local variables, sorry. Atypical is just an assembler that happens 
to look
vaguely HLL-like.

>Is it possible to do things like:
>	w = a, + b, - c;

Yup, for sure, as long as each operation is a PIC instruction. This is still 
assembly language,
not a compiler. I.e.,
    w = 123          // OK, this is a MOVLW
    STATUS = 123 // No good; no MOVFW instruction

>Do I understand that bit variables are placed in "<>" e.g. STATUS<Z>? Would
>temp<0> be the low order bit of temp?

Yup. I chose <> to mirror the Microchip notation.

I actually mentioned Atypical on the piclist a year or two ago. It was a 
little experiment
that worked well for me. I thought I'd write up a doc and put it out there, 
but I'm
too lazy (tech writing is my day job!). Plus it's 14-bit only, so I'm not 
sure how much
interest there would be.


m

>From: "James Newton, Host" <jamesnewton@piclist.com>
>Reply-To: "Microcontroller discussion list - Public." <piclist@mit.edu>
>To: "'Microcontroller discussion list - Public.'" <piclist@mit.edu>
>Subject: RE: [PIC] interesting language aty
>Date: Mon, 14 Feb 2005 13:56:55 -0800
>
>Interesting language.
>
>I assume the "." before the "b" in "byte .b" makes that a local variable
>which can be reused by other routines? What do you do if:
>
>Proc1:
>	call Proc2
>	return
>
>Proc2:
>	byte .b
>	.b = w
>	nop
>	return
>
>Proc3:
>	byte .a
>	call Proc2
>	return
>
>How does Proc3 allocate .a without having that overwritten by Proc2? Does 
>it
>check all the procedures that it calls to find the maximum number of locals
>under it? Or does Proc2 check all the procedures that call it?
>
>Is it possible to do things like:
>	w = a, + b, - c;
>
>Do I understand that bit variables are placed in "<>" e.g. STATUS<Z>? Would
>temp<0> be the low order bit of temp? Why not use the period again? 
>Slightly
>different meaning but very close to the same thing. STATUS.Z is the bit
>called Z in the scope of STATUS just as OutputWInHex.toHex is the label
>called toHex in the scope of OutputWInHex.
>
>Is this compiler available? Open Source? Can I publish it on Piclist.com?
>
>---
>James Newton: PICList webmaster/Admin
>mailto:jamesnewton@piclist.com  1-619-652-0593 phone
>http://www.piclist.com/member/JMN-EFP-786
>PIC/PICList FAQ: http://www.piclist.com
>


-- 
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist