[self-interest] Error: module object: <0> has no name .
mail at russell-allen.com
Tue Sep 6 00:32:09 UTC 2011
I would strongly recommend using the interface to deal with modules
rather than trying to manage them manually which is what it sounds like
you are doing.
I don't know how far you've been able to read so far, but there is a
description of what the Transporter is doing at
and also you should work through the tutorial at
which needs updating but is still a good way of getting your head round
things and describes the process of making sure your objects have a
canonical name (ie a creator path from the lobby) and that each of their
slots has a module noted in its annotation.
The key to understanding the Transporter is that it doesn't file out
objects per se, but sets of slots positioned relative to the lobby.
On Mon, 05 Sep 2011 23:12:40 +0200, Jan-Paul Bultmann wrote:
> I can only speculate what goes wrong, maybe the guys just getting up,
> there over the big pond now a bit more ;)
> Normaly Self identifies its objects by the place they are found in
> the Lobby, to give them the name, so when you get "a slots object"
> this means that it is not registered somewhere with or as a proto.
> Secondly, modules are normally generated not by Lobby inheritance (as
> you seem to assume when you state that the module Object looks the
> same as the other)
> but they are (additonally? sorry I never got that deep^^) expressed
> in slot annotations.
> As the transporter doesn't group objects into modules but slots. This
> is so that you can modify std Objects and ship those Modifications
> with your App.
> I hope this helps at least a little bit :)
> Btw, if you like you could take a look at the #self-lang channel for
> some chat and insta debugging help :) (or open jabber where I already
> spammed you :P)
> Cheers Jan
> On Sep 5, 2011, at 5:55 PM, Mildred Ki'Lya wrote:
>> Hi again,
>> I'm trying to hack the klein application, and I added a new
>> "assemblerSystems llvm" object. I set its parent* to
>> "assemblerSystems framework" and set the slot parent* to be in a
>> module asmLLVM which I set to be a child of asmKit.
>> Everything seems fine. If I look at the changed modules, I get
>> asmKit and asmLLVM. I both write them to the disk and close the
>> Next session, I load the klein/vmKits.self file (I suppose it's the
>> parent module for all other modules) ... and I get a strange error:
>> Error: module object: has no name .
>> Receiver is: a slots object.
>> Apparently, a new module got inserted in the registery ..
> I assume you mean Lobby by this :)?
>> . If I look at the offending object, it seems to be a rightful
>> module except the window says "a slots object". But it looks like
>> any module out there, including parent*
>> The call on "name" happens in an ascendingOrder message.
>> The problem is that this exception prevents me from getting the
>> list of changed modules, and saving them. I don't know how I could
>> fix this.
> mailto:janpaulbultmann at me.com?subject=Re%3A%20%5Bself-interest%5D%20Error%3A%20module%20object%3A%20%3C0%3E%20has%20no%20name%20%2E
> mailto:self-interest at yahoogroups.com?subject=Re%3A%20%5Bself-interest%5D%20Error%3A%20module%20object%3A%20%3C0%3E%20has%20no%20name%20%2E
> mailto:self-interest-traditional at yahoogroups.com?subject=ChangeDeliveryFormat:Traditional
> mailto:self-interest-digest at yahoogroups.com?subject=EmailDelivery:Digest
> mailto:self-interest-unsubscribe at yahoogroups.com?subject=Unsubscribe
>  http://docs.yahoo.com/info/terms/
More information about the Self-interest