You might each want to take your local snapshot of the page Scott has
provided, in case this is a temporary URL.
This confirms that my analysis I posted last week--using this will be much
more convient than hard thinking for the byte-code reverse engineering.
I'll now concentrate on the objects and the byte-code emitted as a result of
script syntax examples.
Also, I've requested the Access database, but it may not be much more than
what was posted on the OOpic list a week or so ago (that link was
http://www.oopic.com/ObjectPropListo.html).
Daniel
----- Original Message -----
From: "Scott Savage" <sms...@ho...>
To: <dd...@mc...>
Sent: Wednesday, 05 May 2004 13:18
Subject: RE: OFFLIST: Request for compiler information WAS: [oopic] Re:
Oopic compiler issues - The low down.
> I only check this email ever so often.
>
> Here is item 1 on your list.
> http://www.oopic.com/OOPicObjectCommandList.html
>
> As for Item2, do you have Access 2k? If so I can send you item #2.
>
> -Scott Savage
>
>
> >From: "D. Daniel McGlothin" <dd...@mc...>
> >To: <sms...@ho...>
> >CC: "D. Daniel McGlothin" <dd...@mc...>
> >Subject: OFFLIST: Request for compiler information WAS: [oopic] Re:
> >Oopic compiler issues - The low down.
> >Date: Thu, 29 Apr 2004 02:25:38 -0400
> >
> >Scott,
> >
> >You said:
> >
> >"If you guys want to put
> >together a full blown C language compiler, you will have my full
> >support. No need to reverse engineer the compiler. Just ask for
> >whatever you need. I will release the native code instructions and
> >the Object definitions for your developer's group."
> >
> >and a bit later:
> >
> >"No NDA necessary. I have been thinking about releasing the native
> >language for some time."
> >
> >
> >I thank you for your generous offer.
> >
> >On behalf of the group (https://sourceforge.net/projects/oopic-compiler),
> >would you provide:
> >
> >1. native code instructions
> >2. object definitions, with OOpic firmware levels each of supported at
> >3. permission to package the OOPicMK.exe with the project (versions 3,
4,
> >and 5)
> >4. catalog of error messages generated by OOPicMK.exe
> >5. algorithm or source for OOpicMK.exe
> >6. permission to package corrections to the OOpic documentation, or
> >alternatively, provide an electronic means of allowing us to send
revisions
> >of the same to you for psoting at www.oopic.com.
> >7. any lists of bugs/annoyances/things-to-do for the OOpic toolchain that
> >might be addressed in toolchain revisions. We are aware of Dennis
Clark's
> >buglist.
> >8. list of deprecated and un-implemented objects
> >9. a comment on your take as to whether the failure of the shift
operation
> >(Basic syntax << and >>) is a IDE, compiler, or a firmware issue.
> >10. a comment on your take as to whether the problems with array elements
> >beyond 4 or 5 is solely a compiler issue.
> >
> >
> >I understand if you wish to keep any of the above 'under wraps' for
> >whatever
> >reason. Further, I'm aware that some of this information is included at
> >www.oopic.com and in the released IDE, but if it is available in a more
> >concise form, it would be appreciated.
> >
> >If you are aware of significant overlap of any effort between yourself
and
> >this project, perhaps we could assist you rather than working at
> >cross-purposes. Please let me know if this is the case.
> >
> >Finally, congradulations on the Microchip arrangement, as well as the
> >SpeakJet; and thanks for the peek at the visual virtual circuit editor
you
> >recently posted.
> >
> >Best regards,
> >Daniel McGlothin
> >
> >
> >PS, Understanding your position on e-mail, I'll post this by paper mail
to
> >the address listed at www.oopic.com if I do not get a reply of receipt
> >within a couple of days.
> >
> >
> >
>
> _________________________________________________________________
> Stop worrying about overloading your inbox - get MSN Hotmail Extra
Storage!
>
http://join.msn.com/?pgmarket=en-us&page=hotmail/es2&ST=1/go/onm00200362ave/
direct/01/
>
>
>
|
