[Tinymux] @decomp doesn't give same results

[Greg Russell]

I did an @decomp of an object (syntax: @decomp/db #4625).   Not counting
locks and flags, it gave me commands to recreate 31 attributes.
Problem is that there are 63 attributes on the object.  It output 24 of
them, then skipped a bunch and then output the last 7.   I noticed it
luckily as the first attribute I wanted to edit was missing.
 
So I did it again, same command.   It output 40 attributes this time.
The first 31, and then the last 9.
 
Then I do:  @dolist lattr(#4625)=@decomp/db #4625/##.    It outputs the
first 29 attributes, and then the last 9.
 
The attributes it is skipping I can output doing them one by one with
@decomp/db.    I can also do an @dolist and give the explicit list of
skipped attributes and all of them output.   I did a wildcard @decomp
that would match some of the missing attributes and they all exported
fine.   
 
I did an @dolist with the entire list of 63 attributes explicitly
written out instead of using lattr(), and it worked fine.
 
I then went back to @dolist lattr(#4625)=@decomp/db #4625/##, which had
failed before, and this time it worked fine. 
 
Anyone have any ideas what is going on?  I'm starting to worry this db
is ready to go boom with how this is behaving.
 
- Greg
----------------------------------------------------------------------
This e-mail, including any attached files, may contain confidential and privileged information for the sole use of the intended recipient.  Any review, use, distribution, or disclosure by others is strictly prohibited.  If you are not the intended recipient (or authorized to receive information for the intended recipient), please contact the sender by reply e-mail and delete all copies of this message.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.tinymux.org/pipermail/tinymux/attachments/20050902/6b89cb3c/attachment.html