optional parameters of "component"

[Zegnåt]

And I don't like breaks, as they are basically a goto ;-)

We’ll let Chris decide over the multiple-returns or break usage then ;-)

As developer of components (with PHP code) I have to test the component (in debug mode) and will get error messages.

You still get error messages my way. Because the code is still eval()’d before I return anything. It’s just that the function will return FALSE if an error occurs, that way you can use it inside the template to offer an alternative when the component were to break.

And components returning values would add additional complexity, the user would have to look at the component to know what it returns and would not be able to do something as described above.

That’s something up to the “user” (as you call them) though. You might never want to use a return inside eval()’d code, I surely never want that, but someone might. It’s just a case I had to include in the check.

My proposed return is this: (Where $eval holds the return value of eval().)

Code:

$eval===NULL||$eval!==FALSE;

BTW: I think this will output a warning (at least in debug mode), if the component does not exist, as $eval is not set :-(

You are right, that’s my mistake, I will try to figure out what to do about that. The problem is that I can’t use isset(), because a working eval() will return NULL and isset(NULL)==FALSE.

I’m going to see what I can do.