Prop addition error

[Shan Hollen]

Ok, idiot question: Why is it impossible to add a "flags" property to
any object but the system obj?

[Luke-Jr]

On Wednesday, December 07, 2011 11:22:19 AM Shan Hollen wrote:
> Ok, idiot question: Why is it impossible to add a "flags" property to
> any object but the system obj?

Works fine for me.

[Josh Benner]

Works for me, too.

[Shan Hollen]

>Works for me, too.
>

The prop exists on object #1 in my old db, but I cannot add it to any
object but #0 in Minimal db.

Is there something wrong with this: ;add_property(#1, "flags", {},
{#300, "rw"})

I can add any prop I want to except fricking "flags."

I get...

#-1:Input to EVAL, line 3: Invalid argument
... called from built-in function eval()
... called from #3:eval, line 8
(End of traceback)

I use a different eval verb, but I reverted to a more basic version
when I encountered the prop problem. The eval verb looks like this:

.program #3:eval
set_task_perms(player);
program = argstr;
program = program + ";";
if (!match(program, "^
*%(;%|%(if%|fork?%|return%|while%|try%)[^a-z0-9A-Z_]%)"))
program = "return " + program;
endif
program = tostr("me = player; here = player.location;", program);
notify(player, toliteral(program));

[Todd Sundsted]

This error will occur if a parent or child already has a property
named "flags" is there any chance of that?

Todd

[Shan Hollen]

>This error will occur if a parent or child already has a property
>named "flags" is there any chance of that?
>

No. That's the first thing I checked. I dunno what's going on. I'm
sure it's something I'm overlooking, though. I have no problems with
a brand new db.

[Todd Sundsted]

Does any other object in the database define the property "flags"?

[Tim van Dijen]

If <object> is not valid or <object> already has a property named
<prop-name> or <info> does not specify a legitimate owner and permission
bits, then E_INVARG is raised.

Op 8-12-2011 2:03, Todd Sundsted schreef:

[Shan Hollen]

>If <object> is not valid or <object> already has a property named
><prop-name> or <info> does not specify a legitimate owner and
>permission bits, then E_INVARG is raised.

This happened as I was laying objects out in Minimal for a new core.
I finally gave up and started over, but I think it was an ownership
issue.