>>>
>>> :)
>> :)
>>
>> Sometimes I do not know if my humour is strange or not :)
>
> It is! And you are the only one having that kind of humor ;)
Not sure that we are safe :
https://www.thefarside.com
Just arrived last month and it is super great
> Am 10.01.2020 um 22:32 schrieb ducasse :
>
>
>> ducasse wrote
>>> It was so simple that I preferred to do it myself so like that I will look
>>> like a great Pharo contributor.
>>
>> :)
> :)
>
> Sometimes I do not know if my humour is strange or not :)
It is! And you are the only one ha
Thanks Sven
I started to use the suggestions of Ben.
And I’m thinking that I could show my version then step back and explain that
indeed there is another process (the UI one).
I will digest your example and produce a new version of the booklet and people
can give feedback.
S.
> On 10 Ja
Hi Ben,
Great approach, though I would make one change to make your example completely
copy/paste runnable.
Stef's original example:
| trace semaphore p1 p2 |
semaphore := Semaphore new.
trace := [ :message |
('[{1}] {2}' format: { Processor activeProcess priority. message })
crLog
Hi Nicolas,
Sure the implementation description is super important, and did not say that.
All I said is that it is an implementation description and not a high level one.
I just checked the descriptions starting page 257 of the Smalltalk-80 The
Language book, as well as VisualWorks's 1.0 Cookbo
On Fri, Jan 10, 2020 at 2:01 PM Eliot Miranda
wrote:
> Hi Steph,
>
>
> On Jan 10, 2020, at 12:42 PM, ducasse wrote:
>
> Yes this is why in my chapter on Exception I show the VM code while some
> people told me that it was not interesting.
> And this is why in the current chapter on semaphore I
Thanks ben, this is a nice idea to illustrate what is happening I will use it.
Thanks for the VM code :).
I like it too.
I will add a note also mentioning that indeed there is a process to execute the
snippets that the reader will write and execute :).
Stef
PS: what makes me laugh a bit is
Hi Steph,
On Jan 10, 2020, at 12:42 PM, ducasse wrote:
Yes this is why in my chapter on Exception I show the VM code while some
people told me that it was not interesting.
And this is why in the current chapter on semaphore I have a section on the
implementation.
Now it does not mean that the
> ducasse wrote
>> It was so simple that I preferred to do it myself so like that I will look
>> like a great Pharo contributor.
>
> :)
:)
Sometimes I do not know if my humour is strange or not :)
But strange humour is better than no humour :)
Stef
PS: I read too many gary larson comics to b
ducasse wrote
> It was so simple that I preferred to do it myself so like that I will look
> like a great Pharo contributor.
:)
-
Cheers,
Sean
--
Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html
Yes this is why in my chapter on Exception I show the VM code while some people
told me that it was not interesting.
And this is why in the current chapter on semaphore I have a section on the
implementation.
Now it does not mean that the we cannot have a higher view too :).
> On 10 Jan 2020,
Done.
https://github.com/pharo-project/pharo/issues/5466
It was so simple that I preferred to do it myself so like that I will look like
a great Pharo contributor.
> On 10 Jan 2020, at 06:30, Danil Osipchuk wrote:
>
> Maybe to add this into the class comment, this is the most co
For greater visibility and comprehension, it might be useful to early in
the manual define a utility method...
Object>>crTracePriority
self crTrace: '[', Processor activePriority printString, ']', self
printString
On Fri, 10 Jan 2020 at 13:13, Eliot Miranda wrote:
>
>
> On Thu, Jan 9, 2020
For example, whether a Semaphore would queue waiting process by order of
registration (thru a linked list for example) or by order of priority (thru
a Heap for example), would completely change its behavior.
So isn't that kind of implementation detail SUPER important, especially
when hidden in VM?
Hi,
Here are dates for the Pharo TechTalks first half of 2020:
January 23: https://association.pharo.org/event-3697009
Thursday 20 https://association.pharo.org/event-3697011
March 19 https://association.pharo.org/event-3697012
April 23 https://association.pharo.org/event-3697013
May 28 https://
There is a new Pharo build available!
The status of the build #4 was: SUCCESS.
The Pull Request #5456 was integrated: "Improving metalink printing and
visualization in Calypso"
Pull request url: https://github.com/pharo-project/pharo/pull/5456
Issue Url: https://github.com/pharo-project/pharo
Hello alejandro
Thanks for the reminder.
I will have a look.
S
> On 10 Jan 2020, at 12:26, Alejandro Infante
> wrote:
>
> The profiler of my master thesis does this (and a lot more). It instruments
> new on all classes in a package + some other core things like String, Color,
> Rectangle
I didn't claim expertise on the subject (although I use semaphores
extensively), nor its simplicity, nor that the implementation description
should be the only guide on its usage (hence 'to add..., how it works'
wording)
Said that, to me it is the case, when a clear description of what is going
on
The profiler of my master thesis does this (and a lot more). It instruments new
on all classes in a package + some other core things like String, Color,
Rectangle and Collections and check if some of them have equivalent state and
are immutable. If they are the profiler allows you to group the i
Actually, it is just a, albeit concise, description of how Semaphores are
implemented.
It does not help much in understanding them, in learning how they can/should be
used, for what purposes and how code behaves.
Understanding of Process, priorities and Scheduling are also needed for a more
co
There is a new Pharo build available!
The status of the build #1102 was: SUCCESS.
The Pull Request #5431 was integrated:
"2854-Pharo-7-Saving-the-settings-breaks-local-directory"
Pull request url: https://github.com/pharo-project/pharo/pull/5431
Issue Url: https://github.com/pharo-project/pha
Hi Sven,
My apologies for the slow reply.
On Mon, 6 Jan 2020 at 14:44, Sven Van Caekenberghe wrote:
>
>
>
> > On 6 Jan 2020, at 08:16, Alistair Grant wrote:
> >
> >> What is your particular problem ?
> >
> > Pavel did some refactoring in
> > https://github.com/pharo-project/pharo/commit/45b7de2
22 matches
Mail list logo
