[PD-DEV] binbuf_addv, t_int to int for "i" args?

[guenter geiger]

On Fri, 27 Aug 2004, guenter geiger wrote:
> I do not understand the problem here. It would be worse if
> binbuf_addv() would expect smaller integers. If it  expects bigger ones,
> they are correctly converted.

oops, sorry, forgot that binbuf_addv() is an elipse function.
Still wondering why it actually worked on the  alpha then.

In fact, it seems the places where int's are actually passed
as parameters are the gui's coordinates mainly.

Guenter


>
> I have been using pd for some years on a 64 bit machine, and it worked
> without problems. I do not know how much code was added since then,
> especially the gui stuff might cause problems, but fixing this should not
> be too much of an headache. Again, I offer to send a patch, I bet
> that what runs on the alpha runs on the athlon too.
>
> Guenter
>
>
> >
> > I think I should change binbuf_addv() so that integer arguments are
> > simply "int", not "t_int".  Can I do this without causing a lot of
> > headaches for extern writers?  (I think it should be OK since Pd
> > doesn't work at all on athlon64 as it is...)
> >
> > The alternative would be to use (t_int) casts everywhere, but
> > really, the "int" argument is intended as a convenience;
> > the data gets converted to a float anyway...
> >
> > cheers
> > Miller
> >
> > _______________________________________________
> > PD-dev mailing list
> > PD-dev at iem.at
> > http://iem.at/cgi-bin/mailman/listinfo/pd-dev
> >
>
>
> _______________________________________________
> PD-dev mailing list
> PD-dev at iem.at
> http://iem.at/cgi-bin/mailman/listinfo/pd-dev
>