"R. Joseph Newton" <[EMAIL PROTECTED]> writes: > If you can tell us a little more about the context and sense in which you > are seeking file type information, we may be able to help you find the > distinctions appropriate to that context.
First... point taken about the bit-anding. But as you said. (and I'm paraphrasing here) "Any self respecting programmer needs to know about that...." but `self respecting programmer' is several jumps up from my level.. This is going to sound pretty lame but I've actually lost sight of why I wanted to know file type. It has come up a few times in various scripts ... I wanted a function that just spits out the info like Unix(gnu) `stat' does. First line of unix `stat' output tells the type. Its more acuratte than -f -d tests. Or even better, something that behaves like unix `file' command. And as far as environment goes, I'm always working on a linux or openbsd platform... occassionally solaris (x86). I use the term `working' loosely here since my efforts are really little more than a retiree's tinkering. -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
