Branch: refs/heads/5.0
Home: https://github.com/pharo-project/pharo-core
Commit: 784a2d28016f67372b71fa0916f695902921ab87
https://github.com/pharo-project/pharo-core/commit/784a2d28016f67372b71fa0916f695902921ab87
Author: Jenkins Build Server
Date: 2016-04-27 (Wed, 27 Apr 2016
Branch: refs/tags/50722
Home: https://github.com/pharo-project/pharo-core
... maybe
#result should beTheResultOf: [mock someMessage].
#result should not beTheResultOf: [mock anotherMessage].
Cordially - Carlos
On Wed, Apr 20, 2016 at 9:22 PM, Denis Kudriashov
wrote:
>
> 2016-04-20 20:36 GMT+02:00 S Krish :
>
>> result should return: [mock someMessage]
>
>
> It shoul
> On 26 Apr 2016, at 23:17, Denis Kudriashov wrote:
>
>
> 2016-04-26 20:16 GMT+02:00 Sven Van Caekenberghe :
> Making log events subclasses of Announcement and using an Announcer instance
> local to a subsystem is one easy implementation choice, but not necessarily
> the only one.
>
> One co
2016-04-26 20:16 GMT+02:00 Sven Van Caekenberghe :
> Making log events subclasses of Announcement and using an Announcer
> instance local to a subsystem is one easy implementation choice, but not
> necessarily the only one.
>
> One concrete (but not perfect) implementation of my ideas can be found
Hi Denis,
I was missing this fine-grained logging also so I wrote a couple of
classes, long ago, that use events. It still logs to the Transcript and
to a log file, in parallel. The test doesn't even make a test, to my
chagrin. Look at TraceMonitor for the output bits and at senders of
Object
Hi
2016-04-26 20:16 GMT+02:00 Sven Van Caekenberghe :
> Try to look at it this way: by using objects (events, signals,
> announcements, whatever) and just generating them on the spot and sending
> them off somewhere, you have everything you need, without imposing any
> restrictions.
>
If logging
Denis,
Try to look at it this way: by using objects (events, signals, announcements,
whatever) and just generating them on the spot and sending them off somewhere,
you have everything you need, without imposing any restrictions.
If you want to use log/severity levels and/or categories and/or ta
2016-04-26 17:28 GMT+02:00 Denis Kudriashov :
> Please do not do that. This might make sense for C or Java (although it
> does not), but we have objects and we should filter based on those without
> relying on a rigid system based on random levels. Please.
And I forgot mention that my proposed A
Hi Tudor.
2016-04-26 15:36 GMT+02:00 Tudor Girba :
>
> > Let's think about logging API to log any object in the system. Most
> natural way is just send message #log to object itself:
> >
> > anObject log
> >
> > It would be nice replacement for Object>>logCr.
>
> This type of usage should be disc
Branch: refs/heads/5.0
Home: https://github.com/pharo-project/pharo-core
Commit: 930e6b02f21cc22fb69d6689c3a5a83a0b7858b7
https://github.com/pharo-project/pharo-core/commit/930e6b02f21cc22fb69d6689c3a5a83a0b7858b7
Author: Jenkins Build Server
Date: 2016-04-26 (Tue, 26 Apr 2016
Branch: refs/tags/50721
Home: https://github.com/pharo-project/pharo-core
Hi Dennis,
> On Apr 26, 2016, at 3:26 PM, Denis Kudriashov wrote:
>
> Hello.
>
> I resumed discussion about SystemLogger and Beacon here
> http://forum.world.st/What-the-state-of-unifying-Beacon-with-SystemLogger-td4890684.html.
>
> I plan to unify both approaches by saving traditional term
Hello.
I resumed discussion about SystemLogger and Beacon here
http://forum.world.st/What-the-state-of-unifying-Beacon-with-SystemLogger-td4890684.html
.
I plan to unify both approaches by saving traditional terminology from
SystemLogger and cool features from Beacon.
Let's think about logging AP
Branch: refs/heads/5.0
Home: https://github.com/pharo-project/pharo-core
Commit: 727e21dd92c93b62cc215db17d9aaf8120c3ec8f
https://github.com/pharo-project/pharo-core/commit/727e21dd92c93b62cc215db17d9aaf8120c3ec8f
Author: Jenkins Build Server
Date: 2016-04-26 (Tue, 26 Apr 2016
Branch: refs/tags/50720
Home: https://github.com/pharo-project/pharo-core
Branch: refs/tags/50719
Home: https://github.com/pharo-project/pharo-core
Branch: refs/heads/5.0
Home: https://github.com/pharo-project/pharo-core
Commit: f3436231f2ca0c40107d924afcd5bd8fcd7f4889
https://github.com/pharo-project/pharo-core/commit/f3436231f2ca0c40107d924afcd5bd8fcd7f4889
Author: Jenkins Build Server
Date: 2016-04-26 (Tue, 26 Apr 2016
Branch: refs/tags/50718
Home: https://github.com/pharo-project/pharo-core
Branch: refs/heads/5.0
Home: https://github.com/pharo-project/pharo-core
Commit: 9df37bad96048acf7f71614a79d586dd13695a37
https://github.com/pharo-project/pharo-core/commit/9df37bad96048acf7f71614a79d586dd13695a37
Author: Jenkins Build Server
Date: 2016-04-26 (Tue, 26 Apr 2016
Branch: refs/tags/50717
Home: https://github.com/pharo-project/pharo-core
Branch: refs/heads/5.0
Home: https://github.com/pharo-project/pharo-core
Commit: 02d361e8f60d0086f324de6af655eaf5502ab3b3
https://github.com/pharo-project/pharo-core/commit/02d361e8f60d0086f324de6af655eaf5502ab3b3
Author: Jenkins Build Server
Date: 2016-04-26 (Tue, 26 Apr 2016
Branch: refs/tags/50716
Home: https://github.com/pharo-project/pharo-core
Branch: refs/heads/5.0
Home: https://github.com/pharo-project/pharo-core
Commit: 0ae434c0f966d46075dd8cc81ce1ebac483fa5ea
https://github.com/pharo-project/pharo-core/commit/0ae434c0f966d46075dd8cc81ce1ebac483fa5ea
Author: Jenkins Build Server
Date: 2016-04-26 (Tue, 26 Apr 2016
Hi,
Steph, the image logic also has changed in Pharo. There should not be
any difference (at least from the list that Eliot gave).
Guille
Original Message
Wow, thanks for the detailed explanation!
Cheers,
Bernhard
Am 21.04.2016 um 16:48 schrieb Eliot Miranda :
Hi Bernh
Branch: refs/heads/5.0
Home: https://github.com/pharo-project/pharo-core
Commit: b1b738b40653feebd993cef3f84c9f4556aca695
https://github.com/pharo-project/pharo-core/commit/b1b738b40653feebd993cef3f84c9f4556aca695
Author: Jenkins Build Server
Date: 2016-04-26 (Tue, 26 Apr 2016
Branch: refs/tags/50715
Home: https://github.com/pharo-project/pharo-core
27 matches
Mail list logo
