Maybe to add this into the class comment, this is the most concise and
clear description of how it works i've ever seen
пт, 10 янв. 2020 г., 8:13 Eliot Miranda :
>
>
> On Thu, Jan 9, 2020 at 5:03 AM ducasse wrote:
>
>> Hi
>>
>> I wanted to explain
>>
>> | semaphore p1 p2 |
>> semaphore := Semaph
On Thu, Jan 9, 2020 at 5:03 AM ducasse wrote:
> Hi
>
> I wanted to explain
>
> | semaphore p1 p2 |
> semaphore := Semaphore new.
> p1 := [ semaphore wait.
> 'p1' crTrace ] fork.
>
> p2 := [semaphore signal.
> 'p2' crTrace ] fork.
>
> displays p2 and p1.
> but I would like explain
On Thu, 9 Jan 2020 at 12:00, Ronie Salgado wrote:
> Hi All,
>
> I am finally announcing an initial release of my new experimental
> low-level programming language which I am calling Sysmel (For SYStem
> MEtaprogramming Language).
>
> GitHub Page: https://github.com/ronsaldo/sysmel
> Short native
Another requirement for caching and sharing instances is that the object is a
true read only value object.
> On 9 Jan 2020, at 22:45, Esteban Maringolo wrote:
>
> Well... the theme having these colors in a table of some sort, even
> keyed by a role name (very much like windows), isn't like a lo
Well... the theme having these colors in a table of some sort, even
keyed by a role name (very much like windows), isn't like a lot of
work.
Of course, "premature optimization is the root of all evil". But given
that such "careless" behavior has been around for a while, maybe it is
not premature a
>
>
> > In a farther future, a higher performance
> > version of the Woden Engine will be made by using Sysmel, mostly because
> > it
> > seems to be much easier to support real multi-threading in Sysmel by
> > making
> > a completely new system.
>
> Congrats! But... sad that Pharo may eventually l
ducasse wrote
> The idea is how to fight the combinatory explosion of parameters
Cool!!!
-
Cheers,
Sean
--
Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html
Ronie Salgado wrote
> In a farther future, a higher performance
> version of the Woden Engine will be made by using Sysmel, mostly because
> it
> seems to be much easier to support real multi-threading in Sysmel by
> making
> a completely new system.
Congrats! But... sad that Pharo may eventually
ducasse wrote
> it looks like a real plague.
What is the real effect on performance? There is a cost to the complexity of
e.g. caching too, no?
-
Cheers,
Sean
--
Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html
Great!
We were discussing today with Pablo Guillermo pierre gordana Theo and
Angela about fosdem during lunch.
We want to order at least 5 t-shirts (eye catching, turquoise or orange)
for the stand people and presenter :).
We also want to print stickers
,maybe pens, have two screens rolling vide
here is what I’m writing in the book.
Let us image that we have the following two processes and one semaphore.
[[[
| semaphore p1 p2 |
semaphore := Semaphore new.
p1 := [ semaphore wait.
'p1' crTrace ] fork.
p2 := [ semaphore signal.
'p2' crTrace
There is a new Pharo build available!
The status of the build #3 was: FAILURE.
The Pull Request #5461 was integrated:
"5450-Add-executable-comments-in-SequenceableCollection---sorting-shuffling-split-protocol"
Pull request url: https://github.com/pharo-project/pharo/pull/5461
Issue Url: https
Hi
I wanted to explain
| semaphore p1 p2 |
semaphore := Semaphore new.
p1 := [ semaphore wait.
'p1' crTrace ] fork.
p2 := [semaphore signal.
'p2' crTrace ] fork.
displays p2 and p1.
but I would like explain clearly but it depends on the semantics of signal.
--- Begin Message ---
It is a very interesting effort.
The following:
Superclass < #MyObject
uses: #MyTrait;
slots: { #a. #b };
classVariables: { #A. #B };
tags: #(Core) ;
package: #MyPackage
Seems more complex to im
14 matches
Mail list logo
