[Oopic-compiler-devel] FW: OFFLIST: Request for compiler information WAS: [oopic] Re: Oopic compiler issues - The low down.

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

Neil, Andrew,

I'm posting a copy of this request to Scott Savage by regular mail today.

I've had offlist communication with Scott (about http://OOPicide.McGlothin.info)
in which he said that he only occasionally monitors e-mail to the hotmail
address he is using on the list.  I presumed therefore, that he has it set up so
that all but yahoo groups list mail is filtered.

Anyway, I've sent this to that email address, and today by postal mail.

Best regards,
Daniel

-----Original Message-----
From: D. Daniel McGlothin [mailto:dd...@mc...]
Sent: Thursday, April 29, 2004 2:18 AM
To: sms...@ho...
Cc: D. Daniel McGlothin
Subject: OFFLIST: Request for compiler information WAS: [oopic] Re:
Oopic compiler issues - The low down.


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.


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.