Re: Fluid Application Environment 3.0.alpha1 Released!
- Posted by jimcbrown (admin) Oct 14, 2013
- 2284 views
certified to not crash as if it would if hacked in by the random user who does not understand FAE so well.
I don't think this is possible either. function_to_do() could simply call crash("some msg") and crash that way. I think what you want is integrity checking inside of FAE itself (akin to what a kernel does at its syscall interface when being called by user-space code), to reject garbage if garbage is passed in. I agree that this would be a good idea, but I must reluctantly acknowledge that it's difficult to catch all cases - and even more difficult to cerify in any way that has some sort of reliable meaning.
Ok, then the certified code that won't crash in FAE's widget
if sequence(dir elephant_3legs.e) then include elephant_3legs.e end if procedure do_user(sequence what) elephant_3legs:gui_interface(what)-- must exist in my elephant_3legs.e end procedure
Well, I just tried that out (commenting out the one line in do_user since I don't have a file called elephant_3legs.e) and it crashed.
I don't want someone to say "i hacked FAE, and now it doesn't work, what a $%^&#$!", because that happened to me and EuBot (why is Creole making a bad link to that?), so i know how it feels.
Ouch. Who the heck said that? Having used eubot, I disagree completely.
