On Friday 22 March 2002 17:53, Russ Allbery wrote: > Brent Dax <[EMAIL PROTECTED]> writes: > > > Parrot_Foo for external names, FOO for internal names, struct > > parrot_foo_t for struct names. > > POSIX reserves all types ending in _t. I'm not sure that extends to > struct tags, but it may still be better to use _s or something else > instead to avoid potential problems.
We had always used _T (structs), _E (enums), _EE (enum elements), and _F (enums that were flags). I always thought that was a little overboard, but far less so than Hungarian notation, which I had always abhorred. I've rewritten stacks.[ch] as close to the "coding standards" as I could get it, along with some additional constraints that I'll be putting on types. It's probably not 100%, but an idea of what the code should probably end up looking like. (One exception is the exceptions.) Folks, take a peek, and identify the stuff you've a grief with now. Let's make whatever changes to the coding standards that we need to do, and move on from there. We need to start cracking the whip now. I'll take responsbility for refactoring the old code. -- Bryan C. Warnock [EMAIL PROTECTED]
