General Advice - objects, classes and coding style

I am in the process of transforming a procedural code base into an OO
code base. The code lends itself to this refactoring and it is proving
an effective exercise.

However, I am running into a few irritations.

I am using __autoload to load class files corresponding to code names.

I've cranked up error reporting, but if for some reason there is a
syntax error or whatever in a class, the application crashes with no
explanation. The bug hunt takes ages and lots of echoing.

Is there anything I can do to help myself? Use of assert, or exceptions,
or try-catch handling?

Re: General Advice - objects, classes and coding style

turnitup wrote:
> I am in the process of transforming a procedural code base into an OO
> code base. The code lends itself to this refactoring and it is proving
> an effective exercise.
>
> However, I am running into a few irritations.
>
> I am using __autoload to load class files corresponding to code names.
>
> I've cranked up error reporting, but if for some reason there is a
> syntax error or whatever in a class, the application crashes with no
> explanation. The bug hunt takes ages and lots of echoing.
>
> Is there anything I can do to help myself? Use of assert, or exceptions,
> or try-catch handling?
>

Personally, I don't use __autoload. It isn't that hard to add
require_once statements where necessary.


--
==================
Remove the "x" from my email address
Jerry Stuckle
JDS Computer Training Corp.
jstucklex@attglobal.net
==================

Re: General Advice - objects, classes and coding style

Greetings, turnitup.
In reply to Your message dated Thursday, October 25, 2007, 00:52:55,

t> I am in the process of transforming a procedural code base into an OO
t> code base. The code lends itself to this refactoring and it is proving
t> an effective exercise.

t> However, I am running into a few irritations.

t> I am using __autoload to load class files corresponding to code names.

t> I've cranked up error reporting, but if for some reason there is a
t> syntax error or whatever in a class, the application crashes with no
t> explanation. The bug hunt takes ages and lots of echoing.

t> Is there anything I can do to help myself? Use of assert, or exceptions,
t> or try-catch handling?

Did You read user comments on Autoloading Objects article?
http://ru2.php.net/autoload
There's some useful info and good examples.


--
Sincerely Yours, AnrDaemon

Re: General Advice - objects, classes and coding style

On Oct 24, 4:52 pm, turnitup wrote:
> I am in the process of transforming a procedural code base into an OO
> code base. The code lends itself to this refactoring and it is proving
> an effective exercise.
>
> However, I am running into a few irritations.
>
> I am using __autoload to load class files corresponding to code names.
>
> I've cranked up error reporting, but if for some reason there is a
> syntax error or whatever in a class, the application crashes with no
> explanation. The bug hunt takes ages and lots of echoing.
>
> Is there anything I can do to help myself? Use of assert, or exceptions,
> or try-catch handling?

You might have turned up error reporting, but did you enable display
errors? If not you won't see them. You should always enable
display_errors when developing, and disable it in production. In
production use log_errors so your error messages go to a file instead.

Re: General Advice - objects, classes and coding style

On Oct 24, 2:52 pm, turnitup wrote:
> I am in the process of transforming a procedural code base into an OO
> code base. The code lends itself to this refactoring and it is proving
> an effective exercise.
>
> However, I am running into a few irritations.
>
> I am using __autoload to load class files corresponding to code names.
>
> I've cranked up error reporting, but if for some reason there is a
> syntax error or whatever in a class, the application crashes with no
> explanation. The bug hunt takes ages and lots of echoing.
>
> Is there anything I can do to help myself? Use of assert, or exceptions,
> or try-catch handling?

I would definitely check your php.ini's Error Reporting settings. To
find out what your PHP's settings are, you can make a new php file and
put:

echo phpinfo();
?>

It will show you where your php.ini file is, as well as your
display_error settings.