| From: | Paul Hill |
| Date: | 15 Jul 2000 at 19:11:38 |
| Subject: | Re: I am going OO nuts !!! |
On 15-Jul-00 17:16:49, Colin Wenzel wrote:
>On 16-Jul-00, Paul Hill wrote:
>> On 15-Jul-00 15:25:03, Allan Odgaard wrote:
>>> On 15-Jul-00, Colin Wenzel wrote:
>>>> However, linking is another story, I cannot resolve the
>>>> symbols: DoMethod() & MUI_MakeObject()
>>>> [...]
>>>> Could you or anyone else supply the stub routines or
>>>> prototype info for these calls please.....
>>> Though the latter should be done by the compiler, by using "#pragma
>>> tagcall" in the appropriate pragma file. And the former is a
>>> function of amiga.lib, it's prototyped in "clib/alib_protos.h".
>> For GCC these calls are stored as macros [1] in the appropriate proto
>> file. They're generated form the fd/clib files by fd2inline.
>> [1] this method is less than ideal and can cause problems, especially
>> with MUI. I got around this by sticking MUI_MakeObject() in a .lib
>> and commenting out the sections in inline/muimaster.h.
>> Not nice. I know.
>I'm sorry, but I don't really understand exactly what you mean
>when you say they are stored as macros...
>Is the # pragma definition what you call a macro ??
I was talking about GCC (I didn't know what compiler you used). AFAIK GCC
doesn't use #pragmas.
>What I need is the stub code for the rom call DoMethod()
>in whatever library it is in.... (intuition ??)
>and MUI_MakeObject() as it appears not to be in mui.lib.
DoMethod() and DoMethodA() are both in amiga.lib.
>I am using the Aztec 5.2 compiler & the "amiga.lib"
>on the dev cd's are not compatible anymore,
>so I have always had to build my own after about WB1.3 days.
Aztec..Never used it, sorry. Doesn't MUI come with Aztec support?
In my 'pragmas/muimaster_pragmas.h' it mentions SAS & Aztec only.
>To do this, I need the stub code, which I can simply make from
>the FD files supplied on the CD, but this function is not in any of
>them.
>As this is the very first time I have ever done any of this OO stuff
>I have not needed a stub for these functions,
>so that is why they are unresolved.
Actually I think the problem isn't OO related rather Tag related.
Functions that end in 'A' usually take their parameters as a TagList. For
example in MUI it's common to build the entire GUI with 1 call and 100s of
parameters.
------------------------------------------------------------------------
The Most Expensive Thing You Can Haul Is An Empty Trailer.
http://click.egroups.com/1/5776/1/_/451227/_/963699856/
------------------------------------------------------------------------