Am Dienstag 19 September 2006 04:01 schrieb Miles Bader: > Steve Langasek <[EMAIL PROTECTED]> writes: > > It is also clear that this is how many maintainers have understood it, > > because as you yourself have noticed, there are many packages that > > assume they can ship directories in /var/run and have them remain > > available after reboot. :) > > I think it's more likely that the average maintainer just never thought > about the issue, and did what they did because "it works". > > I.e. the same reason many people used to assume int was 32 bits. When > 64-bit processors became common, lots of programs broke. The solution > to that was to educate programmers to be more careful and assume less, > not to retroactively add silly restrictions to the definition of int.
Which OS combination does not define int to be 32bit on a 64bit architecture? long should better be 64bit then as many assume that you can cast a pointer into a long and back (e.g. timer in the linux kernel has a long for private data and not a void*, really sick). HS -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
