On 10/1/05 7:38 PM, Robert Slifka didst favor us with:
> Hi Bob,
>
> Removing the pascal keyword definitely builds, but I get a SIGILL the first
> time it casts/runs a function with one of those data types, and I'm having a
> hard time figuring out the cause.
>
> Definitely feel like I'm in over my head here.
I think you're looking in the wrong place for the problem. The presence or
lack of the pascal keyword isn't going to have any effect once you can get
the code to compile because that keyword no longer does anything. You need
to look at how you're using the functions instead, and maybe post some of
that code.
Larry
>
> Rob
>
>> From: Bob Currier <email@hidden>
>> Date: Sat, 1 Oct 2005 16:06:30 -0700
>> To: Robert Slifka <email@hidden>, <email@hidden>
>> Subject: Re: 'pascal' keyword not accepted in typedefs
>>
>> On Sat, Oct 1, 2005 3:44 PM, Robert Slifka <email@hidden> wrote:
>>
>>> The cross-platform header file this is in (supplied by device mfr.)
>>> specifically defines it.
>>>
>>> #ifdef _WINDOWS
>>> #define PASCAL
>>> #else
>>> #define PASCAL pascal
>>> #endif
>>>
>>
>> I think the definition of pascal is done in ConditionalMacros.h, where
>> most of the compiler-specific stuff is. If you're on 10.4, it's certainly
>> possible the headers are just broken for CodeWarrior--since Apple claims
>> to have no copy of it in-house to test with.
>>
>> But first I'd just try using the Windows definition for the Mac to see if
>> this is even the right track to be on.
>>
>> -- Bob
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Carbon-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/carbon-dev/email@hidden
This email sent to email@hidden
