proxy inlets, msp, obex


    Mar 20 2008 | 7:32 pm
    In an obex external, when I use proxy_getinlet(x), I am getting an warning: /Developer/Projects/czero~/czero~.c:132: warning: passing argument 1 of 'proxy_getinlet' from incompatible pointer type
    this is an MSP object, thus a t_pxobject
    should I care? is there a better way to do this?
    bt
    barry threw Media Art and Technology
    San Francisco, CA Work: 857-544-3967 Email: bthrew (at) gmail (dot) com Web: www.barrythrew.com

    • Mar 20 2008 | 11:35 pm
      On Mar 20, 2008, at 12:32 PM, barry threw wrote: > In an obex external, when I use proxy_getinlet(x), I am getting an > warning: /Developer/Projects/czero~/czero~.c:132: warning: passing > argument 1 of 'proxy_getinlet' from incompatible pointer type > > this is an MSP object, thus a t_pxobject > > should I care? is there a better way to do this?
      You can either safely ignore the warning, or use explicit typecasting (the latter is preferable, and required with strict pointer type checking)--e.g. proxy_getinlet((t_object *)x);
      -Joshua
    • Mar 20 2008 | 11:59 pm
      Ah. Thanks.
      I was using t_pxobject, and getting the same error.
      b
      On Mar 20, 2008, at 4:35 PM, Joshua Kit Clayton wrote: > > On Mar 20, 2008, at 12:32 PM, barry threw wrote: >> In an obex external, when I use proxy_getinlet(x), I am getting an >> warning: /Developer/Projects/czero~/czero~.c:132: warning: passing >> argument 1 of 'proxy_getinlet' from incompatible pointer type >> >> this is an MSP object, thus a t_pxobject >> >> should I care? is there a better way to do this? > > You can either safely ignore the warning, or use explicit > typecasting (the latter is preferable, and required with strict > pointer type checking)--e.g. proxy_getinlet((t_object *)x); > > -Joshua > >
      barry threw Media Art and Technology
      San Francisco, CA Work: 857-544-3967 Email: bthrew (at) gmail (dot) com Web: www.barrythrew.com
    • Mar 21 2008 | 4:13 am
      Barry, which compiler was this?
      On Thu, Mar 20, 2008 at 3:59 PM, barry threw wrote: > Ah. Thanks. > > I was using t_pxobject, and getting the same error. > > b > > > > On Mar 20, 2008, at 4:35 PM, Joshua Kit Clayton wrote: > > > > On Mar 20, 2008, at 12:32 PM, barry threw wrote: > >> In an obex external, when I use proxy_getinlet(x), I am getting an > >> warning: /Developer/Projects/czero~/czero~.c:132: warning: passing > >> argument 1 of 'proxy_getinlet' from incompatible pointer type > >> > >> this is an MSP object, thus a t_pxobject > >> > >> should I care? is there a better way to do this? > > > > You can either safely ignore the warning, or use explicit > > typecasting (the latter is preferable, and required with strict > > pointer type checking)--e.g. proxy_getinlet((t_object *)x); > > > > -Joshua > > > > > > > barry threw > Media Art and Technology > > San Francisco, CA > Work: 857-544-3967 > Email: bthrew (at) gmail (dot) com > Web: www.barrythrew.com > > > >
    • Mar 21 2008 | 4:35 am
      GCC 4.0.1
      b
      On Mar 20, 2008, at 9:13 PM, Brandon Nickell wrote: > Barry, which compiler was this? > > On Thu, Mar 20, 2008 at 3:59 PM, barry threw wrote: >> Ah. Thanks. >> >> I was using t_pxobject, and getting the same error. >> >> b >> >> >> >> On Mar 20, 2008, at 4:35 PM, Joshua Kit Clayton wrote: >>> >>> On Mar 20, 2008, at 12:32 PM, barry threw wrote: >>>> In an obex external, when I use proxy_getinlet(x), I am getting an >>>> warning: /Developer/Projects/czero~/czero~.c:132: warning: passing >>>> argument 1 of 'proxy_getinlet' from incompatible pointer type >>>> >>>> this is an MSP object, thus a t_pxobject >>>> >>>> should I care? is there a better way to do this? >>> >>> You can either safely ignore the warning, or use explicit >>> typecasting (the latter is preferable, and required with strict >>> pointer type checking)--e.g. proxy_getinlet((t_object *)x); >>> >>> -Joshua >>> >>> >> >> >> barry threw >> Media Art and Technology >> >> San Francisco, CA >> Work: 857-544-3967 >> Email: bthrew (at) gmail (dot) com >> Web: www.barrythrew.com >> >> >> >>
      barry threw Media Art and Technology
      San Francisco, CA Work: 857-544-3967 Email: bthrew (at) gmail (dot) com Web: www.barrythrew.com