Well, unless someone makes a weird feature request I think the hard parts are
done. I just need to grind through m100.def and make all the wrapper functions.
I suppose I should test them, too :-)
This is probably one of the largest and least compatible Small C libraries
ever. I don't know
Cheer up, Willard. Been there, done that.
More than once... :(
On 3/23/17, Willard Goosey wrote:
> Doesn't help when I get all obsessed with something. I was all "it's a
> pointer it must be declared as such"
>
> Anyway that's most of a day's hacking wasted. At least rcs
Doesn't help when I get all obsessed with something. I was all "it's a pointer
it must be declared as such"
Anyway that's most of a day's hacking wasted. At least rcs is over its mad
Willard
Sent from Samsung tablet
Original message
From "John R. Hogerhuis"
On Thu, Mar 23, 2017 at 1:48 PM, Willard Goosey wrote:
>
> John you're right i'm an idiot
>
> Extern char CSRX is the right thing.
>
>
> Are you sure you want me writing the compiler's library? :-(
>
> Willard
> Sent from Samsung tablet
>
We all make those kinds of mistakes.
John you're right i'm an idiot
Extern char CSRX is the right thing.
Are you sure you want me writing the compiler's library? :-(
Willard
Sent from Samsung tablet
Yeah, sorry... I'd been hacking on that all day with no success, and was more
than a little cranky. Let me try again:
The global absolute label CSRX=0xF63A is the address of the X co-ordinate of
the cursor on the screen. ("Im picking on it because it's the first variable to
appear in m100.def.)
On Thu, Mar 23, 2017 at 1:55 AM, Willard Goosey wrote:
>
> And I really really hoped that the system variables would be as easily
> used. Unfortunately it's not to be. A reference to extern char *CRSX
> (x=CRSX) generates "lhld CRSX \n mov a,m" when what I need is "lxi h,
>
I'm not likely to make it to SoCal any time soon, but Ottawa's a lot closer (or
maybe you'll find yourself in Toronto some day...)
Hope to meet one fine day...
m
- Original Message -
From: Stephen Adolph
To: Model 100 Discussion
Sent: Thursday, March 23, 2017 1:50 AM
On Thu, Mar 23, 2017 at 1:55 AM, Willard Goosey wrote:
> G!!!
>
> Ok, so. My m100.def has, for SmallC purposes, 3 classes of equates. ROM
> function that don't require arguments or return values, ROM functions that
> do require args or return values, and system
G!!!
Ok, so. My m100.def has, for SmallC purposes, 3 classes of equates. ROM
function that don't require arguments or return values, ROM functions that do
require args or return values, and system variables.
Because I use sed to translate the ASM/ZMAC original equates into ASX syntax
10 matches
Mail list logo