More on Permissions

 

Brief review of permission bits:

Objects - rwf

r

anyone can get a list of verbs and props on your obj. This doesn't mean they can actually read those verbs or props. (That is handled by the permissions of those verbs and props).

f

fertile

w

if the object is writable, this means that anyone could add or remove verbs or props from your object, even if your object is not readable.

Verbs - rdxw

r

the verb is readable, anyone can @list your verb

d

debug bit. This means if verb hits an error, you get a traceback.

x

can the verb be called from other verbs (executable)

w

the verb is world writable. This means that anyone can change your verb code, but it still runs under the original author's permissions. This is almost always a BAD THING (tm).

Properties - rcw

r

the property is world readable.

w

this means that anyone can write to your property (ie. change the value of your prop). Generally, w permission bits, whether on objs, verbs or props, is not a great idea, though of the 3, a +w prop is probably the least problematic, though I suppose it depends on how much of a problem you think someone changing the value of your prop might present. ;-)

c

this is perhaps the trickiest, (initially) of the different permission bits. If a prop is +c, anyone who creates a @kid of your object, will own the property. This means that they can directly change it, but also means that your verbs will no longer have permission to change it. So, the owner of a kid could change the prop with eval, or change the prop using @set. If you want YOUR verbs to be able to change the property, then you want so set the prop !c, so that you will be the owner of the prop for any kids. If anyone needs or wants any clarification on any of this.