On Sun, Oct 07, 2001 at 12:15:38PM -0400, Kirrily Robert wrote: > In perl.modules, you wrote: > > modid: System2 > > rationale: > > > > this is an easier and 'cheaper' alternative to using open3 to > > getting stderr as well as stdio from a child process. > > Is "system2" the common Unix name for this feature?
No, it is not. It _is_ an occasionally used convention for implementing a extension of an established function. (eg.: atan2 dup2 exp2 gethostbyname2 log2, etc...) This convention is used within the perl distribution: eg. IPC::Open2 (creates open2), IPC::Open3 (creates open3). > If so, I approve > the name. If, however, it's just your own way of saying "this is > another way of doing System" I'd suggest System::Whatever (where > "whatever" is the distinguishing feature of your module as compared to > System, eg "Fast" or "Simple" or whatever.) There isn't a 'System' heirarchy; I don't feel comfortable inventing a new top-level namespace, just to put something underneath it. :) _Maybe_ it could be argued that this could live under the 'IPC' heirarchy. If the Powers-That-Be want to argue such a change into place, I guess I could go with that. But, this module has been available on CPAN for months now, and I know that some people are using it, so, if nothing else, I plea that for the sake of running code, I don't change the namespace spuriously. > K. > > -- > Kirrily 'Skud' Robert - [EMAIL PROTECTED] - http://infotrope.net/ > The latest politico-sexual minority: Bisexual separatists -- Brian 'you Bastard' Reichert <[EMAIL PROTECTED]> 37 Crystal Ave. #303 Daytime number: (603) 434-6842 Derry NH 03038-1713 USA Intel architecture: the left-hand path
