[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Help-smalltalk] Code update and class variables
From: |
Paolo Bonzini |
Subject: |
Re: [Help-smalltalk] Code update and class variables |
Date: |
Mon, 6 Sep 2010 13:09:05 +0200 |
On Mon, Sep 6, 2010 at 12:53, Holger Hans Peter Freyther
<address@hidden> wrote:
>>> 2.) #doesNotUnderstand will not work from what I see as the Logging Module
>>> does not know who is going to add areas to it, unless I do something like
>>> LogConfig allSubClassesDo: []... is that appropriate?
>>
>> I don't understand why would you subclass LogConfig rather than create
>> multiple instances?
>
> Maybe my approach is wrong, so let me recap. I have multiple subsystems that
> add their own areas but I want to write code like this anObject logDebug:
> 'message' area: #sccp. So for this I need to have a LogConfig per Process (or
> one global one to start with).
Do you have a pointer to the API you're taking inspiration from?
Paolo
- [Help-smalltalk] Code update and class variables, Holger Hans Peter Freyther, 2010/09/06
- Re: [Help-smalltalk] Code update and class variables, Paolo Bonzini, 2010/09/06
- Re: [Help-smalltalk] Code update and class variables, Holger Hans Peter Freyther, 2010/09/06
- Re: [Help-smalltalk] Code update and class variables, Paolo Bonzini, 2010/09/06
- Re: [Help-smalltalk] Code update and class variables, Holger Hans Peter Freyther, 2010/09/06
- Re: [Help-smalltalk] Code update and class variables,
Paolo Bonzini <=
- Re: [Help-smalltalk] Code update and class variables, Holger Hans Peter Freyther, 2010/09/06
- Re: [Help-smalltalk] Code update and class variables, Paolo Bonzini, 2010/09/07
- Re: [Help-smalltalk] Code update and class variables, Holger Hans Peter Freyther, 2010/09/07
- Re: [Help-smalltalk] Code update and class variables, Paolo Bonzini, 2010/09/07