On Mon, Feb 13, 2012 at 09:01:03AM +0100, Simon Schick wrote:
> Hi, Paul
>
> I personally pretty much like the idea of auto-loaders, but that's a
> personal point of view.
> If you have always develop with scripts having autoloaders you'll hate to
> write a *require_once* command at the beginning
Hi, Elbert
I personally would remove the set_error_handler completely. This is a
configuration that the administrator has to handle himself. In a
development-env they want to see all errors, warnings etc, yes - even a
strict_notice. But in a production-env they dont want to show anything to
the us
Hi, Paul
I personally pretty much like the idea of auto-loaders, but that's a
personal point of view.
If you have always develop with scripts having autoloaders you'll hate to
write a *require_once* command at the beginning of all files. And what
would a dependency-injection-container be without a
On Sun, Feb 12, 2012 at 11:36 PM, Paul M Foster wrote:
> The more I've thought about it since then, the more I've considered it a
> Good Thing(tm). It makes troubleshooting existing code a whole lot
> easier. I don't have to wonder what the autoloader is doing or where the
> files are, on which th
On Mon, Feb 13, 2012 at 09:24:38AM +1100, Elbert F wrote:
> Hi Simon,
>
> I think you're right that I may be abusing the constructor a bit. I'm going
> to follow your suggestion and split it up into smaller functions. I'm also
> thinking of moving the set_error_handler and spl_autoload_register
>
Hi Simon,
I think you're right that I may be abusing the constructor a bit. I'm going
to follow your suggestion and split it up into smaller functions. I'm also
thinking of moving the set_error_handler and spl_autoload_register
functions to index.php where Swiftlet is bootstrapped so they can be
c
Hi, Elbert
I've looked through the code and found it quite tiny. I like that.
Until now I found some things that I'd like to discuss with you:
In the class App you're doing all the stuff (routing, calling the
constructor aso) in the constructor. Would it not be better to have
separate functions
I'm looking for constructive feedback on Swiftlet, a tiny MVC framework
that leverages the OO capabilities of PHP 5.3. It's intentionally
featureless and should familiar to those experienced with MVC. Any comments
on architecture, code and documentation quality are very welcome.
Source code and do
8 matches
Mail list logo
