Re: Fluid Application Environment 3.0.alpha1 Released!
- Posted by useless_ Oct 14, 2013
- 2299 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
and elephant_3legs.e must take care of catching invalid procedure calls? Or i need to copy/paste my filename.e into the widget launcher in FAE, with no mistakes? That's ok too, altho an slightly odd name for a widget. But i think you get the idea, i do not know the internals of FAE, so making it happen is up to Ry. 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.
useless
