Why are they bold? I though maybe it meant they had parent implementations or comments, but neither seemed correct…
Thanks, Sean
-- View this message in context: http://forum.selflanguage.org/Bold-outliner-items-tp7572606.html Sent from the Self mailing list archive at Nabble.com.
Slots can be marked as public or private (or unmarked). This is purely documentational and not enforced at all, but slots marked public get bolded by outlines. I think the idea is to help the user work out which messages to start with.
If you right click on a slot you should see a 'Make public' menu option.
Cheers, Russell,
On 7 Feb 2014, at 8:20 am, SeanDeNigris sean@clipperadams.com wrote:
Why are they bold? I though maybe it meant they had parent implementations or comments, but neither seemed correct…
Thanks, Sean
-- View this message in context: http://forum.selflanguage.org/Bold-outliner-items-tp7572606.html Sent from the Self mailing list archive at Nabble.com.
On Feb 6, 2014, at 6:03 PM, Russell Allen [via Self] ml-node+s2190606n7572607h27@n2.nabble.com wrote:
slots marked public get bolded by outlines
Ahh, okay thanks. In Smalltalk, private methods go in "private - [whatever]". A bit of a hack, but harder to miss!
-- View this message in context: http://forum.selflanguage.org/Bold-outliner-items-tp7572606p7572608.html Sent from the Self mailing list archive at Nabble.com.
Outliners don't really hide private methods enough for me. Lately I've been putting them in a 'private' category so I don't have to see them!
On 7 Feb 2014, at 10:08 am, SeanDeNigris sean@clipperadams.com wrote:
On Feb 6, 2014, at 6:03 PM, Russell Allen [via Self] <[hidden email]> wrote:
slots marked public get bolded by outlines
Ahh, okay thanks. In Smalltalk, private methods go in "private - [whatever]". A bit of a hack, but harder to miss!
View this message in context: Re: Bold outliner items Sent from the Self mailing list archive at Nabble.com.
Reply via web post Reply to sender Reply to group Start a New Topic Messages in this topic(3) VISIT YOUR GROUP • Privacy • Unsubscribe • Terms of Use .
Russell Allen wrote:
Slots can be marked as public or private (or unmarked). This is purely documentational and not enforced at all, but slots marked public get bolded by outlines.
This is true in Self 4.x but wasn't the case in Self 1 and 2 where the privacy declaration made a difference in slot lookup. A private slot would be found be an implicit self send but not by a normal send. This meant that "mumble" and "self mumble" might do different things (note that they still might if 'mumble' is a temporary variable in the current method, but that is a different issue).
Unfortunately this privacy stuff combined with parent priorities and the tie breaker rule to make it really hard for programmers to guess what a piece of code would do. So it was all ripped out in Self 3 until a proper solution could be found but the privacy declarations remained as a kind of comment to be ignored by the VM. The proper solution was Us (do we have a link to the relevant papers for that on the site?).
-- Jecel
self-interest@lists.selflanguage.org