[e-lang] Bug: Non-composability of __getPropertySlot

[Karp, Alan H]

MarkM wrote:
> 
> Should E programs have a standard way to declare what version 
> of E they're 
> written in?  

Having a bit of code declare what version it was written for may be a
convenience, but I'm concerned that it might be a security
vulnerability.  There is always the possibility of an exploitable
implementation error.  My concern is that code written for version X
might declare itself to have been written in version Y.  That would seem
to expand the exposure dramatically.  

Versions are introduced for a reason, almost always a new feature or a
removed one.  That being the case, the E language interpreter can infer
the version number.  (Hey, nothing's impossible for the person who
doesn't have to do it.)  You could also report incompatibilities between
the code and the runtime versions.

_________________________
Alan Karp
Principal Scientist
Virus Safe Computing Initiative
Hewlett-Packard Laboratories 
1501 Page Mill Road
Palo Alto, CA 94304
(650) 857-3967, fax (650) 857-7029
https://ecardfile.com/id/Alan_Karp
http://www.hpl.hp.com/personal/Alan_Karp/
  
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Karp, Alan H.vcf
Type: text/x-vcard
Size: 423 bytes
Desc: Karp, Alan H.vcf
Url : http://www.eros-os.org/pipermail/e-lang/attachments/20060724/0946447d/attachment.vcf