> Yech, good point. I'm not even sure you can do any sort of sane > abstraction there. > > In that case, are we better off chopping it out entirely and leaving > it to library code, or making it a simple yes/no indicator that there > are some? (Chopping it out's probably the best thing)
Chopping off sounds like less coding :-) I think the same general KISS approach applies here that you chose with the time handling - no need to implement calendar algorithms in Parrot lowest layer, so I don't think trying to abstract Universal ACL schema is a priority. If someone after Parrot 1.0 wants to implement Tibetan lunar calendar or POSIX 1.e ACLs in IMC, let them. The operative word being "them". -- Jarkko Hietaniemi <[EMAIL PROTECTED]> http://www.iki.fi/jhi/ "There is this special biologist word we use for 'stable'. It is 'dead'." -- Jack Cohen
