> > In my experience, the resulting > > code tends to be more portable across architectures with different > > pointer/long sizes and endian-ness. > > This is where I disagree. Too often people cast away the bugs and end > up with overflow and sign problems.
Since we haven't tried this yet, and since without the warnings you'd never know about the problems in the first place, at least we have an improvement over the status quo. If it sucks, we can back it out. If not, then we can keep it. Relax, both of you. This is -current, remember? -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ [email protected] \\ The race is long, and in the \\ [email protected] \\ end it's only with yourself. \\ [email protected] To Unsubscribe: send mail to [email protected] with "unsubscribe freebsd-current" in the body of the message
