some things php needs

jgetner

well we all know php needs some things so here is my hopes for php to add.

1 . itself() - so when your pissed off it can go f itself!.
2. true typehinting - for the originals ( string , int , char, long, etc...);
3. Careless() - when you dont want the type hinting you can careless.
4. DoAll() - thats it i want it to do all.
5. Get Rid of the Whole Try Catch for Exceptions()!....
6. make a better reflection class that doesnt suck!.
7. make a good damn cache class that is built in that doesnt suck.
8. make the CGI implementation optional so Better console and desktop applications can be made with php that doesnt require a browser

so lets here them what does php need and of course in practical ones are ok if they are in moderation....

laserlight

jgetner wrote:
5. Get Rid of the Whole Try Catch for Exceptions()!....

As in get rid of exceptions, or... what alternative would you propose to that keeps exceptions in the picture?

jgetner wrote:
8. make the CGI implementation optional so Better console and desktop applications can be made with php that doesnt require a browser

It is already optional, though I do not think stuff like PHP-GTK have really caught on.

jgetner

i would suppose a mechanism that can catch all exceptions so you can still throw exceptions like normal but not have to use try {something etc....} catch(Exception $e) {who somethings etc...}

i like exceptions as they are great but i really hate if you that you have to catch them all as i use them all for my error handling and reporting having to to write a try catch block everywhere is rather useless in my point of view.... something like a autoload() but for exception autocatch(Exception $e);

it is optional can you point me in the direction for to learn how to implement this? and is it comparable to such as python, ruby...?

laserlight

jgetner wrote:
i would suppose a mechanism that can catch all exceptions so you can still throw exceptions like normal but not have to use try {something etc....} catch(Exception $e) {who somethings etc...}

You can already do that by just having one set of try/catch blocks around the main part of your script.

jgetner wrote:
i like exceptions as they are great but i really hate if you that you have to catch them all as i use them all for my error handling and reporting having to to write a try catch block everywhere is rather useless in my point of view.... something like a autoload() but for exception autocatch(Exception $e);

But if you are writing try/catch blocks everywhere, then you're probably using exceptions wrongly, e.g., you are trying to handle them even when you cannot handle them appropriately, instead of letting them propagate to a point where you can handle them appropriately.

jgetner wrote:
it is optional can you point me in the direction for to learn how to implement this?

I cannot say much as I do not use PHP in this way myself, but you can start with:
Using PHP from the command line
PHP-GTK

jgetner

i handle them correctly but on large applications that requires many exceptions throughout the application what then? i know my framework runs 6 different exception types all handled by 1 handler but this is a must have as my exceptions are split for 2 uses one side by me and my framework another by someone else and there application.....

laserlight

jgetner wrote:
i handle them correctly but on large applications that requires many exceptions throughout the application what then?

We have to do what we have to do :p

Like I said, you can already surround every main script with try/catch and be done with it, but then you'll be missing out on those cases where the exception could be handled appropriately at a lower level. In the case of a framework, you would be missing out on cases where it is appropriate to translate the exception to something specific to your framework.

dalecosp

laserlight;10966899 wrote:
As in get rid of exceptions, or... what alternative would you propose to that keeps exceptions in the picture?

It is already optional, though I do not think stuff like PHP-GTK have really caught on.

At least partly because if you can grok the GTK part of that, you're probably good enough in C or C++ to do it the "right" way.