Hi,
I've re-targeted our Modula-2 compiler system to Palm OS and now I'm
constructing the support libraries. I've written the startup code and all
that good jazz, have the "Hello, World" in Modula-2 workin on Palm OS. But
that's not the reason for this mail... I have a question relating to
copyright and header files.
What I'd like to do is, in Modula-2, construct a set of definition modules
which use the standard Palm C prototypes, naming conventions and parameters.
This means that anybody using our Modula-2 compiler for Palm OS can
piggyback on the documentation which is already produced for C.
As an example of what I want to do, here's a procedure I cooked earlier:
PROCEDURE ErrDisplayFileLineMsg(filename: ARRAY OF CHAR; lineNo: CARDINAL;
msg: ARRAY OF CHAR)
[CODE(04E40H+SysTraps.sysDispatchTrapNum,
SysTraps.sysTrapErrDisplayFileLineMsg),
NOHIGH];
It's (almost) identical to the standard C prototype, but is in a Modula-2
guise. What I don't want to do is land in murky water and Palm's lawyers if
I simply transcribe all C header files to Modula-2. There's the standard
rider at the top of each Palm header which says I should get written
permission to transcribe, translate, and so on. However, who do I call?
Should I worry? If there's somebody from 3Com listening, could yo tell me
who I should contact about this? Or whether I should worry?
Thanks,
--
Paul Curtis
Rowley Associates Ltd.
