Nicolas Celliernicolas.cellier.aka.n...@gmail.com wrote:
Then, the harder work begins:
- File/Socket/Pipe
- Pointers (in External Heap)
- Character encoding/decoding
I just published XtreamsDevelopment(387) with following changes:
* abstracted Encoder out of encoded streams to allow
Thanks!
and welcome back.
Stef
On Oct 11, 2010, at 7:16 AM, Sheridan Mahoney wrote:
I've just re-entered the Pharo world after a long(ish) absence, and wanted to
report a
new bug submission; here's the breakdown:
Pharo image: dev
Pharo core version: Pharo-1.1.1-- Latest update:
There is not enough memory to give squeak the amount specified by the 'memory
EMBED tag.. Additionally there's a Premature end of file error on the image
and then the VM crashes (OS X crash dialog). Issuing the same commands with 1
GB memory works fine (no problems with the image).
Hi , it was a enhancement i did starting from a Chris Muller enhancement for
Squeak.
ISSUE 2653.
http://code.google.com/p/pharo/issues/detail?id=2653can=1q=autocolspec=ID%20Type%20Status%20Summary%20Milestone%20Difficulty
I did a test, maybe a good start would be to see if its failing now.
Hi Nicolas,
You have been working quite quickly, great!
I tried to follow your different releases in Pharo 1.1.1, right now I have 433
tests, 3 failures (#testReadWriteLargeAmount), 11 errors (#..base64 and
#..multipleBufferSize). If will send you the report.
I have been trying some of the
I investigated PluggableListMorph and ListMorph, the problem you
describe is there (likely this should be fixed in Pharo). In
Name: OB-Morphic-lr.149
Author: lr
Time: 11 October 2010, 10:17:53 am
UUID: 285339d9-f9da-4c6d-98b9-e09ea154c91e
Ancestors: OB-Morphic-lr.148
- more efficient
Ok, I opened an issue: http://code.google.com/p/pharo/issues/detail?id=3091
http://code.google.com/p/pharo/issues/detail?id=3091The patch works for
me, Thank you Igor.
Cheers,
-- Pavel
On Sun, Oct 10, 2010 at 6:46 PM, Igor Stasenko siguc...@gmail.com wrote:
On 10 October 2010 17:40,
On Mon, Oct 11, 2010 at 10:18 AM, Lukas Renggli reng...@gmail.com wrote:
I investigated PluggableListMorph and ListMorph, the problem you
describe is there (likely this should be fixed in Pharo). In
Name: OB-Morphic-lr.149
Author: lr
Time: 11 October 2010, 10:17:53 am
UUID:
?
In any way, passing anything else than block literal as argument should work.
You mean in the implementation or in the semantics?
Read my mail.
This is a question of semantics. The argument of iftrue:ifFalse: are thunk
(piece of code with frozen execution).
This is smalltalk, not C
For convenience, this is the link to the issue:
http://code.google.com/p/pharo/issues/detail?id=3090
I suspect that this bug is related to the new block closures.
Adrian
On Oct 11, 2010, at 07:15 , Sheridan Mahoney wrote:
I've just re-entered the Pharo world after a long(ish) absence, and
I integrate
Issue 3086: MCMethodDefinitionshutdown hack to avoid lock down.
http://code.google.com/p/pharo/issues/detail?id=3086
Igor can you have a look and let me know:
1- if we should rollback Issue 3086:MCMethodDefinitionshutdown
hack to avoid lock
Hi,
Some guys from North of France cannot come to Bern.
So we propose to make a shared session with you, but localized at LIFL,
Villeneuve d'Ascq.
We can do it during the two days.
http://code.google.com/p/pharo/wiki/PharoSprints
Cheers,
Jannik
On Sep 27, 2010, at 22:36 , Tudor Girba
On Oct 10, 2010, at 3:13 08PM, Stéphane Ducasse wrote:
personnally I do not like this form
What does it do?
process ifNotNil: #terminate.
for me it means passes the symbol #terminate as argument to the method
ifNotNil:
If it has a more magical behavior then I do not know it.
Sounds good. We just have to see about the technical details.
Cheers,
Doru
On 11 Oct 2010, at 11:17, Laval Jannik wrote:
Hi,
Some guys from North of France cannot come to Bern.
So we propose to make a shared session with you, but localized at LIFL,
Villeneuve d'Ascq.
We can do it
See: http://github.com/SquareBracketAssociates/
Cheers,
- on
___
Pharo-project mailing list
Pharo-project@lists.gforge.inria.fr
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
On 11 October 2010 12:10, Stéphane Ducasse stephane.duca...@inria.fr wrote:
I integrate
Issue 3086: MCMethodDefinitionshutdown hack to avoid lock down.
http://code.google.com/p/pharo/issues/detail?id=3086
Igor can you have a look and let me know:
1- if we should
Begin forwarded message:
From: Tudor Girba tudor.gi...@gmail.com
Date: October 11, 2010 11:38:54 GMT+02:00
To: Pharo-project@lists.gforge.inria.fr
Cc: Moose-related development moose-...@iam.unibe.ch, notre liste
lsehub-st...@lists.gforge.inria.fr
Subject: [Moose-dev] Re: [Pharo-project]
*Hallo to all, *
I am starting my Ph.D on 'languages and environments for autonomous
robotics' -- and pharo will be a huge part of it.
I am currently playing around with the system (to get the feel of it..) and
testing it's programming tools in the context of
different namespaces / environments.
personnally I do not like this form
What does it do?
process ifNotNil: #terminate.
for me it means passes the symbol #terminate as argument to the method
ifNotNil:
If it has a more magical behavior then I do not know it.
Stef
It's exactly the same as using collection do:
Thanks.
So let's see what is the best choice and tell us.
On Oct 11, 2010, at 11:47 AM, Igor Stasenko wrote:
On 11 October 2010 12:10, Stéphane Ducasse stephane.duca...@inria.fr wrote:
I integrate
Issue 3086: MCMethodDefinitionshutdown hack to avoid lock down.
On 11 October 2010 13:53, Stéphane Ducasse stephane.duca...@inria.fr wrote:
personnally I do not like this form
What does it do?
process ifNotNil: #terminate.
for me it means passes the symbol #terminate as argument to the method
ifNotNil:
If it has a more magical behavior then I do not
- i added a test to cover this issue
http://code.google.com/p/pharo/issues/detail?id=3092
On 11 October 2010 14:01, Stéphane Ducasse stephane.duca...@inria.fr wrote:
Thanks.
So let's see what is the best choice and tell us.
On Oct 11, 2010, at 11:47 AM, Igor Stasenko wrote:
On 11 October
On Oct 10, 2010, at 12:49 40PM, nullPointer wrote:
Now I know is possible add a new font, for use cross platform like DejaVu. I
know Juan Vuletich did that but I don´t know found the place of that is
explained. Is heard do that?
Whuups, might've sent you in a wild goose chase, sorry :/
This still seems confusing. Could we just have a new SqueakSource
project called Xtreams (small T + an S)? It's not like projects are
expensive to create...
Julian
On Sat, Oct 9, 2010 at 11:33 PM, Nicolas Cellier
nicolas.cellier.aka.n...@gmail.com wrote:
So, I started a quick port of VW Xtreams
Hi Folks,
I just wanted to install my work on version 1.1 and was surprised
to discover changes which leave me alone to find out for myself how to change
my code :
WorldMenu (I wrote a subclass of PasteUpMorph)
NaturalLanguageTranslator (what is the gettext package mentioned in the
class
Objectvalue
^self
What actually shown here is a use of duck typing, because any object,
which implemets #value, could be safely passed
as argument to #ifTrue:ifFalse: message.
It is well consistent with language design.
Magritte implemented Symbol#value: for a while before any
Name: OB-Morphic-lr.149
Author: lr
Time: 11 October 2010, 10:17:53 am
UUID: 285339d9-f9da-4c6d-98b9-e09ea154c91e
Ancestors: OB-Morphic-lr.148
- more efficient fix for list updating
I try to remember the current scroll position before updating any OB
list, so I guess this works
Hello,
here a situation, with which we can deal in more safer manner:
Suppose you have a weak registry, populated by different objects and
their executors.
Now, when some of them died, a weak registry performs finalization.
The potential danger is , that if there's an error triggered by some
On 11 October 2010 14:28, Lukas Renggli reng...@gmail.com wrote:
Objectvalue
^self
What actually shown here is a use of duck typing, because any object,
which implemets #value, could be safely passed
as argument to #ifTrue:ifFalse: message.
It is well consistent with language design.
On 11 October 2010 14:40, Igor Stasenko siguc...@gmail.com wrote:
Hello,
here a situation, with which we can deal in more safer manner:
Suppose you have a weak registry, populated by different objects and
their executors.
Now, when some of them died, a weak registry performs finalization.
Le 11/10/2010 13:27, Johannes Rasche a écrit :
Hi Folks,
I just wanted to install my work on version 1.1 and was surprised
to discover changes which leave me alone to find out for myself how to
change my code :
WorldMenu (I wrote a subclass of PasteUpMorph)
NaturalLanguageTranslator (what
Hi
we should improve from that side, but unfortunately we do not have enough man
power to build tool
that could support it.
Stef
On Oct 11, 2010, at 1:28 PM, Johannes Rasche wrote:
Hi Folks,
I just wanted to install my work on version 1.1 and was surprised
to discover changes which
Now to me this looks like a hack and again it works because now Symbol are
valuable objects.
Too many hacks will only make the system more hackish.
And especially the
iftrue: 'foo' ifFalse: 'zork'
This is not a hack, because if you refer to implementation:
TrueifTrue:
On Oct 11, 2010, at 1:28 PM, Lukas Renggli wrote:
Objectvalue
^self
What actually shown here is a use of duck typing, because any object,
which implemets #value, could be safely passed
as argument to #ifTrue:ifFalse: message.
It is well consistent with language design.
Magritte
On 11 October 2010 15:18, Stéphane Ducasse stephane.duca...@inria.fr wrote:
Now to me this looks like a hack and again it works because now Symbol are
valuable objects.
Too many hacks will only make the system more hackish.
And especially the
iftrue: 'foo' ifFalse: 'zork'
This is
Dave,
Since when? Even if operating systems started universally covering for such
mistakes, I still would not recommend testing them on it.
Bill
From: pharo-project-boun...@lists.gforge.inria.fr
[pharo-project-boun...@lists.gforge.inria.fr] On
2010/10/11 Johannes Rasche johannesras...@mac.com
Hi Folks,
I just wanted to install my work on version 1.1 and was surprised
to discover changes which leave me alone to find out for myself how to
change my code :
WorldMenu (I wrote a subclass of PasteUpMorph)
NaturalLanguageTranslator
On Mon, 11 Oct 2010, Lukas Renggli wrote:
Objectvalue
^self
What actually shown here is a use of duck typing, because any object,
which implemets #value, could be safely passed
as argument to #ifTrue:ifFalse: message.
It is well consistent with language design.
Magritte implemented
Thanks indeed to John and to you Eliot.
Noury
On 9 oct. 2010, at 03:48, Eliot Miranda wrote:
Hi All,
I'm please to let you know that John Maloney has published his
MicroSqueak code on his website under the MIT license.
http://web.media.mit.edu/~jmaloney/microsqueak/
Apologies for
Hi Nick,
Stef and I worked on an implementation a few years ago.
http://www.squeaksource.com/Namespace.html
Cheers,
Alexandre
On 11 Oct 2010, at 07:53, Nick Papoylias wrote:
Hallo to all,
I am starting my Ph.D on 'languages and environments for autonomous robotics'
-- and pharo will be
On Mon, 11 Oct 2010, Lukas Renggli wrote:
I eventually removed Symbol#value: for good. Re-occuring questions
in the mailing list disappeared.
That's strange, because Symbol #value: was added to Squeak in 2006 during
the developement of 3.9.
Why?
Filename: Magritte-All-lr.185.mcz
Also, i remember someone presented the namespaces implementation
during last ESUG conference. Its fresh, and probably will run on pharo.
But i don't remember who did this.
On 11 October 2010 16:10, Alexandre Bergel alexan...@bergel.eu wrote:
Hi Nick,
Stef and I worked on an implementation a
On 11 oct. 2010, at 15:17, Igor Stasenko wrote:
Also, i remember someone presented the namespaces implementation
during last ESUG conference. Its fresh, and probably will run on pharo.
But i don't remember who did this.
Here you go, it's a GSOC project, video included:
Begin forwarded
Filename: Magritte-All-lr.185.mcz
Author: Lukas Renggli
Timestamp: 19 January 2007 2:25:14 pm
UUID: e26ba5b5-15b0-4128-9839-1536359b89f0
Ancestors: Magritte-All-lr.184.mcz
- removed #value: and #value:value: from Symbol (this is now in 3.9
and not
12189
-
- Issue 2883: Anymorphic Style. Thanks Anymorphic and Nicolas Paez.
- Issue 2979: Controlling UI feedback. BlockClosuresilentlyValue
___
Pharo-project mailing list
Pharo-project@lists.gforge.inria.fr
Stef and I worked on an implementation a few years ago.
http://www.squeaksource.com/Namespace.html
And it is a bad one :)
Now we are working on making the system environment-aware so that we can browse
part of the system, (remotely too with you).
Stef
Cheers,
Alexandre
On 11 Oct
We already integrated the fixes for the systemOrganization he did.
More is needed.
Stef
On Oct 11, 2010, at 3:23 PM, Simon Denier wrote:
On 11 oct. 2010, at 15:17, Igor Stasenko wrote:
Also, i remember someone presented the namespaces implementation
during last ESUG conference. Its
That hack is really cool IMO. The code is easily understood by anyone:
#(4 1 3 5 2) sort: #=.
yes in Moose people are using that a lot for scripting. Now the problem is that
as soon
as you need more you have to get a block.
Stef
___
Pharo-project
On Mon, 11 Oct 2010, Igor Stasenko wrote:
Hello,
here a situation, with which we can deal in more safer manner:
Suppose you have a weak registry, populated by different objects and
their executors.
Now, when some of them died, a weak registry performs finalization.
The potential danger is ,
On Mon, 11 Oct 2010, Stéphane Ducasse wrote:
That hack is really cool IMO. The code is easily understood by anyone:
#(4 1 3 5 2) sort: #=.
yes in Moose people are using that a lot for scripting. Now the problem is that
as soon
as you need more you have to get a block.
Why is that a
On 11 October 2010 16:59, Schwab,Wilhelm K bsch...@anest.ufl.edu wrote:
I'm glad to see that it works like class names (at least effectively) as
messages to environments than a clone of Java syntax that I saw elsewhere.
On the completely pragmatic level, it will make more obvious the fact
Thanks Alain, Stef and Mariano for fast answer.
I assume that will help.
Possibly I can contribute to improve documentation by carefull reading, trying
and so on
Johannes
Am 11.10.2010 um 14:51 schrieb Mariano Martinez Peck:
2010/10/11 Johannes Rasche johannesras...@mac.com
Hi Folks,
On 11 October 2010 16:51, Levente Uzonyi le...@elte.hu wrote:
On Mon, 11 Oct 2010, Igor Stasenko wrote:
Hello,
here a situation, with which we can deal in more safer manner:
Suppose you have a weak registry, populated by different objects and
their executors.
Now, when some of them died,
Levente,
Ok, but just because the system saves us at the last instant does not mean that
we should be going out of our way to multiply free external resources. Files
are well known to the vm; other things (GSL vectors/matrices comes to mind)
will not enjoy such protections. This strikes me
On Oct 11, 2010, at 3:55 PM, Levente Uzonyi wrote:
On Mon, 11 Oct 2010, Stéphane Ducasse wrote:
That hack is really cool IMO. The code is easily understood by anyone:
#(4 1 3 5 2) sort: #=.
yes in Moose people are using that a lot for scripting. Now the problem is
that as soon
as
12190
-
- Issue 3065: HardCoded SystemOrganization references.
Stef
___
Pharo-project mailing list
Pharo-project@lists.gforge.inria.fr
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
On Mon, 11 Oct 2010, Igor Stasenko wrote:
On 11 October 2010 16:51, Levente Uzonyi le...@elte.hu wrote:
On Mon, 11 Oct 2010, Igor Stasenko wrote:
Hello,
here a situation, with which we can deal in more safer manner:
Suppose you have a weak registry, populated by different objects and
their
Dolphin has all of its required processes rigged to restart themselves if
terminated; we must follow that lead. As far as getting error information from
one thread to another, in one case I grab a callstack (just the Thisthat,
Thatthis text with line feeds) and capture it to be included as
On Mon, 11 Oct 2010, Stéphane Ducasse wrote:
On Oct 11, 2010, at 3:55 PM, Levente Uzonyi wrote:
On Mon, 11 Oct 2010, Stéphane Ducasse wrote:
That hack is really cool IMO. The code is easily understood by anyone:
#(4 1 3 5 2) sort: #=.
yes in Moose people are using that a lot for
On 11 October 2010 17:24, Levente Uzonyi le...@elte.hu wrote:
On Mon, 11 Oct 2010, Schwab,Wilhelm K wrote:
Levente,
A similar discussion arose around Dolphin's event (#trigger*) mechanism.
My recollection is that it was not fully addressed due to performance
concerns. Forking and error
Nick,
Just first reactions, but:
(1) questions about integration with the browsers go to Lukas and others who
are doing that work;
(2) keep the design simple and consistent with everything is an object, all
computation happens by sending messages to objects
(3) use (2) vs. creating new syntax
On Mon, 11 Oct 2010, Schwab,Wilhelm K wrote:
Levente,
Ok, but just because the system saves us at the last instant does not mean that
we should be going out of our way to multiply free external resources. Files
are well known to the vm; other things (GSL vectors/matrices comes to mind)
I think that for typing in a transcript experessions when you want to
experiment with something
selectors are fun but not in method body. But I know that this is not a really
good argument. Just feeling.
May be we get trapped in our way of thinking.
I personally don't like the
On Mon, 11 Oct 2010, Igor Stasenko wrote:
On 11 October 2010 17:24, Levente Uzonyi le...@elte.hu wrote:
On Mon, 11 Oct 2010, Schwab,Wilhelm K wrote:
Levente,
A similar discussion arose around Dolphin's event (#trigger*) mechanism.
My recollection is that it was not fully addressed due to
Hi guys
there is a HUGE HUGE HUGE difference between
(1) namespace at the language level and we do not want that the way
german did it.
Give us some times and we will try different solutions and see what come out
(2) systemDictionary at the infrastructure level.
We are
Sig,
I'm not saying to leave the finalizer wide open to the wrath of errors from
poorly coded objects. I am saying that we should strive for one finalizer per
object (preferably the object itself) and that to get there, we need to make
the registry thread safe and have some vm support.
On 11 October 2010 17:34, Schwab,Wilhelm K bsch...@anest.ufl.edu wrote:
Levente,
Ok, but just because the system saves us at the last instant does not mean
that we should be going out of our way to multiply free external resources.
Files are well known to the vm; other things (GSL
GPL is a problem. It means that nothing I write on top of GSL gets out the
door. However, I see no reason not to give others the same mix of capability
and concern in the form of an interface to it.
From: pharo-project-boun...@lists.gforge.inria.fr
For example there currently exist a setter in the class side for 'migratting'
in a new environment, that just alters the class knowledge about the new
namespace and does not erase it's record from the old namespace.
where?
Is this intented ? What is the underlying design ? Should we add
Excellent, can I also push the Seaside Book there?
The main data store remains Pier of course, but we already today keep
the backups and other resources in the SCG SVN.
Lukas
On 11 October 2010 17:06, Serge Stinckwich serge.stinckw...@gmail.com wrote:
Great Oscar ! How to join the
12191
-
- Issue 3092: Additional test for weak registry to check for deadlocks.
Thanks Igor Stasenko.
Issue 3093: Weaklings cleanup fixes. Thanks Igor Stasenko.
Igor the testFinalizationOfMultipleResources breaks, can you have a look?
Stef
2010/10/11 Nick Papoylias npapoyl...@gmail.com:
Hallo to all,
I am starting my Ph.D on 'languages and environments for autonomous
robotics' -- and pharo will be a huge part of it.
Hi Nick,
Great to see that another guy will work in the domain of embedded
systemsautonomous robots with
Argh
ObjectFinalizerfinalize
Finalize the resource associated with the receiver. This message
should only be sent during the finalization process. There is NO
garantuee that the resource associated with the receiver hasn't been
free'd before so take care that you don't run into
On Oct 11, 2010, at 4:10 13PM, Schwab,Wilhelm K wrote:
I am far more worried about having multiple executors per object (when did
p=malloc();free(p);free(p);free(p) become good style?) than I am about
getting the finalizer process itself completely robust at this point.
Bill
I fail to
Excellent, can I also push the Seaside Book there?
If you want. Now I do not see the interest of git when we use it as svn. And I
would prefer to host the book on an inria server
because I know that this is backup by someboyd else than me.
and for a book I do not want to fork it (or people can
On Mon, Oct 11, 2010 at 5:11 PM, Stéphane Ducasse stephane.duca...@inria.fr
wrote:
For example there currently exist a setter in the class side for
'migratting' in a new environment, that just alters the class knowledge
about the new namespace and does not erase it's record from the old
Welcome and any help is welcome.
On Oct 11, 2010, at 4:22 PM, Johannes Rasche wrote:
Thanks Alain, Stef and Mariano for fast answer.
I assume that will help.
Possibly I can contribute to improve documentation by carefull reading,
trying and so on
Johannes
Am 11.10.2010 um 14:51
Excellent, can I also push the Seaside Book there?
If you want. Now I do not see the interest of git when we use it as svn. And
I would prefer to host the book on an inria server
because I know that this is backup by someboyd else than me.
and for a book I do not want to fork it (or people
Lukas == Lukas Renggli reng...@gmail.com writes:
Lukas 1. It is not easily understandable for newbies.
Lukas 2. It quickly leads to very unreadable, hard to understand and hard to
Lukas refactor code.
Lukas 3. It is very limiting in itself and quickly leads to other hacks
Lukas (like to replace
I think this discussion has diverged a lot from the original question, which
is to do with the compiler being too pedantic.
#ifNotNil: and friends are the selectors of methods which just happen to
give the compiler an opportunity for a nice optimization, in the case when
the argument that follows
I am currently concerned with remote programming (debugger, browser,
compiler e.t.c) in Pharo from one image (or environment) to another, so that
this infrastructure can be used in the field of autonomous robotics to ease
the development cycle.
So we should definitely exchange ideas ! Cause there
Henry,
Ok, what valid use of multiple executors have I missed?
Bill
From: pharo-project-boun...@lists.gforge.inria.fr
[pharo-project-boun...@lists.gforge.inria.fr] On Behalf Of Henrik Johansen
[henrik.s.johan...@veloxit.no]
Sent: Monday, October 11,
Nick,
I'm certainly no expert on DST, but I will gladly help where I can. You're
starting a PhD program? Is Stef your advisor? That would put you in good
hands.
Bill
From: pharo-project-boun...@lists.gforge.inria.fr
On 11 October 2010 17:49, Stéphane Ducasse stephane.duca...@inria.fr wrote:
I would really like to have the same behavior than the squeak system ie
having the source modification
send to the list. I could not see how to set it up on squeaksource.
May be this is not the same version running.
Maybe on a separate mailing list.
Cheers,
Alexandre
On 11 Oct 2010, at 12:49, Stéphane Ducasse wrote:
I would really like to have the same behavior than the squeak system ie
having the source modification
send to the list. I could not see how to set it up on squeaksource.
May be this is
On Oct 11, 2010, at 8:07 AM, Stéphane Ducasse wrote:
Hi guys
there is a HUGE HUGE HUGE difference between
(1) namespace at the language level and we do not want that the way
german did it.
Stéphane,
Are you suggesting that the approach Germán Leiva demonstrated at ESUG last
Meanwhile, i'll try to implement two test cases for WeakRegistryTest.
One, should cover following:
coll := OrderedCollection new.
obj := Object new.
wrapper := WeakArray with: obj.
coll add: wrapper.
obj toFinalizeSend: #remove: to: coll with: wrapper.
obj toFinalizeSend: #remove: to: coll
2010/10/11 Peter Hugosson-Miller oldmanl...@gmail.com:
I think this discussion has diverged a lot from the original question, which
is to do with the compiler being too pedantic.
#ifNotNil: and friends are the selectors of methods which just happen to
give the compiler an opportunity for a
On Mon, 11 Oct 2010, Schwab,Wilhelm K wrote:
Henry,
Ok, what valid use of multiple executors have I missed?
I described it earlier how the AXAnnouncements project uses this feature.
Levente
Bill
From:
Ok, I'll dig around for that and have a look.
From: pharo-project-boun...@lists.gforge.inria.fr
[pharo-project-boun...@lists.gforge.inria.fr] On Behalf Of Levente Uzonyi
[le...@elte.hu]
Sent: Monday, October 11, 2010 12:31 PM
To:
On 11 October 2010 19:28, Schwab,Wilhelm K bsch...@anest.ufl.edu wrote:
Sig,
The Dolphin approach is to restart any of the finalizer, main, timer, idler
threads (I *think* there is one more in a baseline image) any time they quit;
an #ensure: block forks a new thread of the type that
It is not the mailing list that is the problem, it is the
squeaksource.com server that is. It takes several minutes to calculate
a simple diff of a single version and that just kills responsiveness
at the current rate of commits.
Lukas
On 11 October 2010 18:01, Alexandre Bergel
El lun, 11-10-2010 a las 10:56 +0200, Stéphane Ducasse escribió:
12188
-
- Issue 3086: MCMethodDefinitionshutdown hack to avoid lock down.
- Issue 2875: PharoKernel Part 11. Thanks Pavel Krivanek and Nicolas Paes
Now that John Maloney has released MicroSqueak as MIT
Sig,
Understood, but are they all that different? The ones that were served ahead
of the error should stay that way (proper recording of same is what needs
attention), and those yet to be served, if it's done well, should be ready for
the new thread to handle. Just something to consider.
2010/10/11 Levente Uzonyi le...@elte.hu:
On Mon, 11 Oct 2010, Lukas Renggli wrote:
Objectvalue
^self
What actually shown here is a use of duck typing, because any object,
which implemets #value, could be safely passed
as argument to #ifTrue:ifFalse: message.
It is well consistent
Stef,
Let's go forward in time. NativeBoost, Alien or FFI provide callbacks, I do
some adaptation on my end, and out comes a pretty capable wrapper for the GNU
Scientific Library. That sentence trivializes a LOT of work :( Details
aside, is the wrapper code itself affected by GPL, or is it
Sig,
As a friend here: when did I say I'd remove all? Remove and process one at a
time. I will admit to having a bias toward doing this with a single executor
per object, but even if multiples turn out to have value (need to hunt down and
read Levente's description of that), the same idea
On Mon, 11 Oct 2010, Lukas Renggli wrote:
It is not the mailing list that is the problem, it is the
squeaksource.com server that is. It takes several minutes to calculate
a simple diff of a single version and that just kills responsiveness
at the current rate of commits.
That seems to be a
Sven Van Caekenberghes...@beta9.be wrote:
I tried to follow your different releases in Pharo 1.1.1, right now I have
433 tests, 3 failures (#testReadWriteLargeAmount), 11 errors (#..base64 and
#..multipleBufferSize). If will send you the report.
I have been trying some of the examples from
On 11 October 2010 21:07, Schwab,Wilhelm K bsch...@anest.ufl.edu wrote:
Sig,
As a friend here: when did I say I'd remove all? Remove and process one at a
time. I will admit to having a bias toward doing this with a single executor
per object, but even if multiples turn out to have value
1 - 100 of 131 matches
Mail list logo
