Re: Compiler error during porting exercise

2006-08-15 Thread Philip Guenther
On 8/2/06, Otto Moerbeek <[EMAIL PROTECTED]> wrote: On Wed, 2 Aug 2006, Michael C wrote: ... > Why is it that the MetroWerks CodeWarrior 3.1 cannot handle the following? > > in header file (pcb.h): > intin_baddynamic (u_int16_t, u_int16_t); > > in c file (pcb.c) > int > in_baddynamic (a, b)

Re: Compiler error during porting exercise

2006-08-14 Thread Woodchuck
On Wed, 2 Aug 2006, Michael C wrote: > Hi, > > I am trying some porting examples to winscw and I have a question: > > Why is it that the MetroWerks CodeWarrior 3.1 cannot handle the following? > > in header file (pcb.h): > intin_baddynamic (u_int16_t, u_int16_t); > > in c file (pcb.c) > in

Re: Compiler error during porting exercise

2006-08-02 Thread Otto Moerbeek
On Wed, 2 Aug 2006, Michael C wrote: > Hi, > > I am trying some porting examples to winscw and I have a question: > > Why is it that the MetroWerks CodeWarrior 3.1 cannot handle the following? > > in header file (pcb.h): > intin_baddynamic (u_int16_t, u_int16_t); > > in c file (pcb.c) > in

Compiler error during porting exercise

2006-08-02 Thread Michael C
Hi, I am trying some porting examples to winscw and I have a question: Why is it that the MetroWerks CodeWarrior 3.1 cannot handle the following? in header file (pcb.h): int in_baddynamic (u_int16_t, u_int16_t); in c file (pcb.c) int in_baddynamic (a, b) u_int16_ta; u_