[Oopic-compiler-devel] Re: [oopic] Re: Oopic compiler issues - The low down.

[D. D. M. <dd...@mc...>]

The more I think about Dan Sandberg's idea, I like it.

The notation of 'background' as an attribute of the routine is essentially
what I was thinking of with my Delphi unit 'sections' approach.

Daniel


----- Original Message -----
From: "scottmsavage" <sms...@ho...>
To: <oo...@ya...>
Sent: Friday, 30 April 2004 10:55
Subject: [oopic] Re: Oopic compiler issues - The low down.


> --- In oo...@ya..., Dan Sandberg <x@c...> wrote:
> > With the THEORETICAL syntax I was mentioning earlier,
> > combined with the kinda of objects that the OOPic
> > already supports, we could do something like this:
> > background void activateSolenoid() {
> >      if ( button.pressed ) {
> >          solenoid = true;
> >          solenoidTimer = 5;
> >          solenoidTimer.operate = true;
> >      }
> > }
> > background void deactiveateSolenoid() {
> >      if ( solenoidTimer.operate and solenoidTimer == 0 ) {
> >          solenoid = false;
> >          solenoidTimer.operate = false;
> >      }
> > }
>
> Yes, I like it and it is really COOL!  But it is not the way the
> OOPic works.  Give me some time and maybe I will be able to figure
> out how to incorporate it.
>
> > Perhaps the root of my confusion is that I don't understand
> > why the code on the OOPic must be so slow.
>
> I am confused.  How did you miss it?  Read this page of the manual:
> http://www.oopic.com/pgchap14.htm
>
> > The OOPic is the only microcontroller I've ever used, so perhaps
> > I am missing something fundamental.
>
> Sounds to me like it is just that you want the OOPic to be something
> it is not.  I think your wish list is a cool idea, but I do not
> think that there is anything on the market right now that works that
> way.
>
> Give me some time and I may be able to change that.
>
> -Scott Savage
>