> > #2 can be accomplished with fusebox.circuit instead. no, it cannot, as that variable is constant throughout the life of a given fuseaction, whereas fusebox.thiscircuit changes value while the core file travels down the circuits and then back up again.
This was explained several times already, by my count, on at least 7 different occasions. I had assumed that you finally worked through that some developers may have use of the fusebox.thiscircuit and others may not. The idea that it can be "ripped" from the spec is also odd -- since going forward with new versions of the spec has already a built-in commitment to backwardly supporting FB3 > 4) Fewer things for a new Fuseboxer to learn and understand. a new fuseboxer need understand nothing about the core files. According to you, since 'everything' can be done with other varaibles then if you are teaching someone about FB you dont need to instruct them on how to use the API variables that you are claiming aren't useful Strange as it may sound, the solution to the world's problems is not in changing the spec every 3 months > > John Q and I have argued about this topic countless times and > I don't think we're any closer to agreement than Sharon and > Arafat. I'm hoping that this time some of the others on the > list will really give it some thought and weigh in on the > subject. Clearly, I get to play Ariel. Would you please do something about that spittle on your lips, Yassir? ==^================================================================ 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 ==^================================================================
