--- Melchior FRANZ wrote:
> * Stuart Buchanan -- Friday 30 March 2007:
> > Functionally, it seems reasonable to force all IO access through a
> wrapper
> > .nas file in $FG_ROOT/Nasal that could attempt to restrict dangerous
> > activities.
>
> But every Nasal code would have to have access to use those
> wrapper/validator functions ... and could then also overwrite them.
> Or bypass the wrappers and use the wrapped core functions directly.
> I assume any validation would have to be done in C++.
I had forgotten that Nasal allows one to over-write a function in another
namespace. Is is possible to declare a function/namespace "final"?
I was going to suggest doing validation in the io.nas file.
An alternative would be to simply add a sub-set of the IO functions to the
system functions we already have in Scripting/NasalSys.*, with the
validation done there.
That would allow us to add I/O functions on an as-needed basis, though
obviously restricts the innovative ideas we may have.
Scenery editing is a use you already mentioned, and I guess data logging
is another, but what other reasons do we have for generic I/O?
-Stuart
___________________________________________________________
Yahoo! Messenger - with free PC-PC calling and photo sharing.
http://uk.messenger.yahoo.com
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
