Hi, I was wondering in the sense that 'does it not break existing platforms and fixes freebsd' and 'is this the only change that freebsd needs?'
From your explanation, this still sounds like a very hacky and not very good approach to fix the problem at hand though. At Tue, 29 Nov 2011 06:36:43 -0600, Jonathan Nieder wrote: > > Junichi Uekawa wrote: > > > Does this actually help? I kind of doubt it. > > If "help" means "make the code any saner for humans reading", then no. > In principle if not in practice, mode_t could be wider than an int > (so it would end up being promoted to something wider than an int). > > If it means "ensure the code compiles and works correctly on amd64 and > kfreebsd-amd64 (not a very wide range of platforms to try, I admit)", > then yes. > > *checks* It seems that glibc uses va_arg(..., int) for this purpose, > too. So I think it should work on all platforms Debian supports. > > Hope that clarifies a little, > Jonathan > -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
