On 2008-07-15 at 23:14:13 [+0200], Salvatore Benedetto <emitrax@xxxxxxxxx> wrote: > 2008/7/14 Ingo Weinhold <ingo_weinhold@xxxxxx>: > >> I plan to move the IPC code to its own source file and extend its > >> usage for message queues > >> and shared memory. I know we already talked about it and decided to > >> use 3 different tables > >> but I don't really see the point of that, besides other OSes don't > >> seems to do so. > > > > One obvious point of using different tables is right here: It avoids > > special > > cases. Another is that, since the standard is not very explicit in this > > respect, I expect most programs not to share IPC keys for the different > > kinds > > of IPC subsystems. So you would end up with table entries that potentially > > reference three kinds of IPC objects, but actually reference only one. > > But what if some programs do share IPC keys for different kinds of IPC > subsystems? > Wouldn't that result in a bug from the application POV? I don't see what kind of potential bug you're thinking of. CU, Ingo