>>>>> "DS" == Dan Sugalski <[EMAIL PROTECTED]> writes: >> Er, you still have to think about whether something could be tied and >> tainted at the same time. DS> Yeah, that's an issue. We need to hammer out how much is the responsibility DS> of the vtable functions, and how much is the responsibility of the op DS> functions. DS> Looks like "tainted" qualifies as the first flag bit in the global flags DS> field... Just a thought. Have a tainted and untainted vtbl. Let tainted data have a tainted vtbl. Then 'unsafe' operations simply call the data access routine with a 'I don't want tainted data'. Untainted vtbls ignore the option. Tainted data, abort/scream. <chaim> -- Chaim Frenkel Nonlinear Knowledge, Inc. [EMAIL PROTECTED] +1-718-236-0183
- Re: Method call optimization. Chaim Frenkel
- Re: Method call optimization. Nick Ing-Simmons
- Re: Method call optimization. David L. Nicol
- Re: Method call optimization. Dan Sugalski
- Re: Method call optimization. Nick Ing-Simmons
- Re: Method call optimization. Nick Ing-Simmons
- Re: Method call optimization. Nick Ing-Simmons
- Re: Ramblings on "base cla... Ken Fox
- Re: Ramblings on "base cla... Larry Wall
- Re: Ramblings on "base cla... Dan Sugalski
- Re: Ramblings on "base cla... Chaim Frenkel
- Re: Ramblings on "base cla... Dan Sugalski
- Re: Ramblings on "base cla... Larry Wall
- Re: Ramblings on "base cla... Ken Fox
- Re: Ramblings on "base cla... Nick Ing-Simmons
- Re: Ramblings on "base cla... Nick Ing-Simmons
- Re: Ramblings on "base class" for ... Nick Ing-Simmons
- Re: Ramblings on "base class" ... Dan Sugalski
- Re: RFC: Foreign objects in perl Benjamin Stuhl
- Re: RFC: Foreign objects in perl Dan Sugalski
- Re: RFC: Foreign objects in perl Simon Cozens