[Solar-talk] Move Solar.php to Solar/Solar.php ?
Clay Loveless
clay at killersoft.com
Sun Sep 9 20:37:48 CDT 2007
On Sep 5, 2007, at 10:05 PM, Clay Loveless wrote:
> On Sep 5, 2007, at 5:30 PM, Paul M Jones wrote:
>
>> Nitpick: it's an "arch" class, not a "base" class. ;-)
> ...
>> Even so, moving *some* of the arch-class functions (e.g., the file-
>> related ones) to their own class does make sense to me. But that
>> doesn't help with the original point; i.e., how best to help out
>> the svn:externals folks.
>
> Ok -- How about arch.php? (Or 'Arch.php'?)
>
> Option 1:
> Since we're talking about making an exception to the naming
> conventions anyway, I would be in favor of something like this:
>
> include 'Solar/arch.php';
> Solar::start();
>
>
> ... where arch.php is a logical name for the file (makes more sense
> than 'Solar/Solar.php'), and rather than defining a 'Solar_Arch'
> class, it's just the 'Solar' arch class.
>
> Option 2:
> I could also see 'Arch.php' defining Solar_Arch, but Solar_Arch
> "sets up" or otherwise returns a 'Solar' class that is a
> convenience handle, of sorts.
>
> Option 3:
> Or, stick with Solar_Arch throughout -- it's fewer keystrokes than
> 'Solar_Framework'. :)
... so was this a big flop? Or are people still thinking about these
options/suggestions?
Just curious. :)
--
Killersoft.com
More information about the Solar-talk
mailing list