IMHO, this is the biggest flaw in the current core file, and hopefully the new committee will agree.
There is currently no way to avoid this happening - you have to  "handle" it using try/catch or cferror.
I'm not going to comment on the specifics of section 8 (i'd ramble even more...), but the way i see it, the core file is a glorified switch.
It switches on the "circuit" (plus a few other things).
But in the current core file there is no way to define a default case, ie something to do when it can't find a valid circuit.
(an invalid fuseaction can be handled by us in the fbx_switch)

There was also a thing about trailing and leading dots to indicate default circuit and fuseactions.
i.e.
fuseaction=foo. indicates the foo circuit and the default fuseaction in the foo circuit
fuseaction=.foo indicates the foo circuit and the foo fuseaction in the default circuit

The first bit was kind of implemented in FB3, (and flaky logic with a ListGetAt() causes the second error you mention) and AFAIK, the leading dot stuff got left behind (where IMHO it belongs).

Hopefullee the crack pot who was rooting for this dotty stuff is nowhere near the standards steering committee
;)

Also, it would be worth checking out the FEX stuff that NatP and ErikV have done - thats got a load of fancy error handling...

Bert

ps sorry - it turned into a bit of a rant - its late and i can her Matilda on the baby CB....

At 18:30 09 05 2002 -0500, you wrote:
While doing a basic bug check on my new FB3 app, I ran into a problem that
makes the site fail each and every time...

I then went to the Fusebox.org site, and it fails there too:
http://www.fusebox.org/index.cfm?fuseaction=asdf.asdf

Basically, if the fusebox.circuit that is referenced in the URL is invalid,
you get an error.
(BTW, fusebox.supresserrors is true)

I also tried several variations of this, such as leaving the fuseaction off,
leaving only the circuit. The error is different, yet just as ugly:
http://www.fusebox.org/index.cfm?fuseaction=home

Is there a fix in the works for this? This seems pretty serious.

Thanks all,
Jeremy

==^================================================================
This email was sent to: [email protected]

EASY UNSUBSCRIBE click here: http://topica.com/u/?bUrFMa.bV0Kx9
Or send an email to: [EMAIL PROTECTED]

T O P I C A -- Register now to manage your mail!
http://www.topica.com/partner/tag02/register
==^================================================================

Reply via email to