I really interested to see if pharo would run on a JVM.
Do you know what smalltalk they are working on?
Stef
On Apr 12, 2011, at 4:20 PM, Stephan Eggermont wrote:
http://mail.openjdk.java.net/pipermail/mlvm-dev/2011-April/002802.html
Comment #3 on issue 3991 by stephane...@gmail.com: use them instead of
UITheme current
http://code.google.com/p/pharo/issues/detail?id=3991
in 13146
Updates:
Status: Started
Comment #4 on issue 3984 by stephane...@gmail.com: Announcements announced
when a test is runned
http://code.google.com/p/pharo/issues/detail?id=3984
(No comment was entered for this change.)
sven did you get a look at issue 3999 since camillo started.
http://code.google.com/p/pharo/issues/detail?id=3999
Stef
On Apr 11, 2011, at 4:10 PM, Sven Van Caekenberghe wrote:
Hi All,
I have this idea that I would like to discuss on the next Pharo sprint and
maybe start to implement if
we should have that in our success stories.
Stef
Begin forwarded message:
From: Sven Van Caekenberghe s...@beta9.be
Date: April 9, 2011 10:25:39 AM GMT+02:00
To: Seaside - general discussion seas...@lists.squeakfoundation.org
Subject: Re: [Seaside] Should I become a Seasider?
Reply-To:
13146
-
- Issue 3991: use them instead of UITheme current. Thanks Fernando Olivero.
You were faster than me on this one but this is cool since I could review the
code faster.
Stef
On 04/13/2011 09:00 AM, Stéphane Ducasse wrote:
I really interested to see if pharo would run on a JVM.
Probably not. I mean you all the code relying on primitives, all the
code relying on ByteString having the same memory layout as ByteArray,
all the code relying on the scheduler being
On Apr 13, 2011, at 9:32 AM, Philippe Marschall wrote:
On 04/13/2011 09:00 AM, Stéphane Ducasse wrote:
I really interested to see if pharo would run on a JVM.
Probably not. I mean you all the code relying on primitives, all the
code relying on ByteString having the same memory layout as
Comment #1 on issue 3997 by fernando...@gmail.com: Move all code in Morph
related the properties, to a trait: TProperties
http://code.google.com/p/pharo/issues/detail?id=3997
I made a mistake in the first fix.
The TProperties should be plugged into MorphExtension, instead of Morph.
Load
I like the idea. Another thing that we may think about is the exception
conventio name...
Do the classes need a suffix or not ? which ones? Exception/Error/Warning?
when Exception and when Error ?
Cheers
Mariano
On Wed, Apr 13, 2011 at 9:24 AM, Stéphane Ducasse stephane.duca...@inria.fr
On Mon, Apr 11, 2011 at 4:10 PM, Sven Van Caekenberghe s...@beta9.bewrote:
Hi All,
I have this idea that I would like to discuss on the next Pharo sprint and
maybe start to implement if there is some consensus on it.
It has been mentioned many times before on this list that Object#error:
Updates:
Labels: Milestone-1.3
Comment #2 on issue 1817 by marcus.d...@gmail.com: [etoy] Should remove
project
http://code.google.com/p/pharo/issues/detail?id=1817
So we can now easily remove Project: the only thing left are some methods
on the class side that are already
in
On 13 Apr 2011, at 10:50, Mariano Martinez Peck wrote:
You probably know the PharoByExample chapter on exceptions,
but just in case:
https://gforge.inria.fr/frs/download.php/26600/PBE2-Exceptions-2010-03-02.pdf
Seems like the right kind of preparation, I will reread it.
I love written
Updates:
Status: Closed
Comment #8 on issue 3818 by marcus.d...@gmail.com: CommandLine Manager
http://code.google.com/p/pharo/issues/detail?id=3818
in 13147
13147
-
Issue 3818: CommandLine Manager
(some cleanup of Undeclared AutoStart will be needed later)
--
Marcus Denker -- http://www.marcusdenker.de
INRIA Lille -- Nord Europe. Team RMoD.
Status: Accepted
Owner: marcus.d...@gmail.com
Labels: Milestone-1.3
New issue 4002 by marcus.d...@gmail.com: AbstractLauncher needs to be
removed
http://code.google.com/p/pharo/issues/detail?id=4002
...make sure to rewrite the SystemSettings references.
I think we should remove
Status: Accepted
Owner: marcus.d...@gmail.com
Labels: Milestone-1.3
New issue 4003 by marcus.d...@gmail.com: Build of Core 1.3 broken because
of integration of 13147
http://code.google.com/p/pharo/issues/detail?id=4003
Issue 13147 has some problem:
+ /builds/builder/build13.sh -i
Status: Accepted
Owner: marcus.d...@gmail.com
Labels: Milestone-1.3
New issue 4004 by marcus.d...@gmail.com: Obsolete class references to
AutoStart
http://code.google.com/p/pharo/issues/detail?id=4004
Two methods:
#loadUpdateFromServerAtStartup
AbstractLauncher class autoStarter
Comment #1 on issue 4003 by marcus.d...@gmail.com: Build of Core 1.3 broken
because of integration of 13147
http://code.google.com/p/pharo/issues/detail?id=4003
I think changing how scripts are loaded in an image started with a script
is not good.
The image itself when updated seems
Comment #1 on issue 4002 by ryd...@gmail.com: AbstractLauncher needs to be
removed
http://code.google.com/p/pharo/issues/detail?id=4002
Security? That script could contain sinister arbitrary code! :)
Comment #2 on issue 4003 by marcus.d...@gmail.com: Build of Core 1.3 broken
because of integration of 13147
http://code.google.com/p/pharo/issues/detail?id=4003
So I did a new prebuild.
https://gforge.inria.fr/frs/download.php/28478/PharoCore-1.3-13147.zip
But now Hudson hangs when loading
Comment #3 on issue 4003 by marcus.d...@gmail.com: Build of Core 1.3 broken
because of integration of 13147
http://code.google.com/p/pharo/issues/detail?id=4003
I think I found it. I added
CommandLine initialize
to the postscript but forgot
CodeLoader initialize
Comment #4 on issue 4003 by marcus.d...@gmail.com: Build of Core 1.3 broken
because of integration of 13147
http://code.google.com/p/pharo/issues/detail?id=4003
Now the script loads but we get a walkback. One that does not kill the
image interestingly.
Updates:
Status: FixToInclude
Comment #5 on issue 4003 by marcus.d...@gmail.com: Build of Core 1.3 broken
because of integration of 13147
http://code.google.com/p/pharo/issues/detail?id=4003
I think the problem is a exception handler that swallows all Exceptions
Hey,
What I've seen so far and I like is to use small helper methods to signal
exceptions:
usage
Dictionary at: aKey
...
self keyNotFound: aKey.
helper method to fill the exceptions params
Dictionary keyNotFound: aKey
KeyNotFoundException signalWithKey: aKey
helper
still this can always be interesting to learn your limit and dependencies.
Stef
On Apr 13, 2011, at 9:32 AM, Philippe Marschall wrote:
On 04/13/2011 09:00 AM, Stéphane Ducasse wrote:
I really interested to see if pharo would run on a JVM.
Probably not. I mean you all the code relying on
Status: FixProposed
Owner: marcus.d...@gmail.com
Labels: Milestone-1.3
New issue 4005 by marcus.d...@gmail.com: Disconnect SecurityManager
http://code.google.com/p/pharo/issues/detail?id=4005
... remove all but one references to security Manager.
Later:
- remove from startup lost
- fix
Updates:
Status: Started
Comment #6 on issue 4003 by marcus.d...@gmail.com: Build of Core 1.3 broken
because of integration of 13147
http://code.google.com/p/pharo/issues/detail?id=4003
Nope. Now we don't get a debug log anymore but it nevertheless hangs.
On 04/13/2011 02:57 PM, Stéphane Ducasse wrote:
still this can always be interesting to learn your limit and dependencies.
Sure, didn't make any judgments in any way. Just said I see some
problems on the road.
Cheers
Philippe
This works:
counter := Class new
superclass: Object;
addInstVarNamed: 'counter';
compile: 'initialize
counter := 0';
compile: 'counterString
^ counter asString';
compile:
Comment #7 on issue 4003 by siguc...@gmail.com: Build of Core 1.3 broken
because of integration of 13147
http://code.google.com/p/pharo/issues/detail?id=4003
here the part of code which responsible for doing startup:
self processStartUpList: resuming.
resuming
On 13 Apr 2011, at 09:32, Philippe Marschall wrote:
Probably not. I mean you all the code relying on primitives, all the
code relying on ByteString having the same memory layout as ByteArray,
all the code relying on the scheduler being non-preemptive, all the
code relying on #become: and so
On 13 April 2011 16:16, laurent laffont laurent.laff...@gmail.com wrote:
This works:
counter := Class new
superclass: Object;
addInstVarNamed: 'counter';
compile: 'initialize
counter := 0';
compile:
On 13.04.2011 16:16, laurent laffont wrote:
This works:
counter := Class new
superclass: Object;
addInstVarNamed: 'counter';
compile: 'initialize
counter := 0';
compile: 'counterString
On Wed, Apr 13, 2011 at 4:21 PM, Stefan Marr ph...@stefan-marr.de wrote:
On 13 Apr 2011, at 09:32, Philippe Marschall wrote:
Probably not. I mean you all the code relying on primitives, all the
code relying on ByteString having the same memory layout as ByteArray,
all the code relying on
Cool ! Thank you all !
Have put this at
http://magaloma.blogspot.com/2011/04/polymorph-counter-example.html
http://magaloma.blogspot.com/2011/04/petite-horloge-revisited.html
Laurent.
On Wed, Apr 13, 2011 at 4:25 PM, Henrik Sperre Johansen
henrik.s.johan...@veloxit.no wrote:
On 13.04.2011
Hi:
On 13 Apr 2011, at 16:44, Mariano Martinez Peck wrote:
Running on the JVM and Running on the JVM are two completely different
things.
Here seems to be the same
'Running on the JVM' = 'Running on the JVM' - true
ehehhe I guess you forgot to change something or I am so stupid to
Status: FixProposed
Owner: benjamin...@gmail.com
Labels: Nautilus
New issue 4006 by benjamin...@gmail.com: Some UI improvement
http://code.google.com/p/pharo/issues/detail?id=4006
- Extraction of a method in IconicButton to allow subclasses to easily
redefine the extra border.
- a forgotten
Updates:
Status: Closed
Comment #8 on issue 4003 by marcus.d...@gmail.com: Build of Core 1.3 broken
because of integration of 13147
http://code.google.com/p/pharo/issues/detail?id=4003
fixed
El mié, 13-04-2011 a las 14:52 +0200, Camillo Bruni escribió:
And as Mariano pointed out, there should be a convention on the
naming: I am still not sure about suffixing the exception classes with
Exception, but I guess this is a good thing to do. Though I must say
that I omitted it so far ;)
On 2011-04-13, at 18:55, Miguel Cobá wrote:
El mié, 13-04-2011 a las 14:52 +0200, Camillo Bruni escribió:
And as Mariano pointed out, there should be a convention on the
naming: I am still not sure about suffixing the exception classes with
Exception, but I guess this is a good thing to
I think it is not a good idea to use the prefix Exception. We do not use the
word exception in real life, so we should not do it on our systems.
About the proposed hierarchy, the problem with having specific exceptions is
that they are important for those who catch them, not for those who signal
Some thoughts from an old man (started programming before exceptions of
any kind were available:) ...
In the old days, error numbers had a place in the universe ... error
numbers of a certain range indicated specific errors and the error
handlers could check for a range or a specific error
JSR 292 explicitly talks about become: (calls it hotswap) and is supposed
to make it possible to run Smalltalk efficiently on a jvm.
I don't know how complete the jsr 292 implementation is of mlvm.
I got the link in a tweet. Roos builds modular automated test equipment.
Stephan
Hi all,Can any suggest me some documents on1.UIBuilder Tool2.UI/Morph
Class3.Database Connection Programming using Pharo.ThanksRegards,Sourav
RoyBangaloreIndiaGet Yourself a cool, short @in.com Email ID now!
Added !
Laurent.
On Wed, Apr 13, 2011 at 6:45 PM, Juan Vuletich j...@jvuletich.org wrote:
Hi Laurent,
I'd like to be added to
http://www.pharo-project.org/community/contributors . My picture is
attached. Description text could be Contributed the default anti-aliased
fonts and the
I'd like to know the state of:
OSProcess
and
CommandShell
under pharo.
There's a ConfigurationOfOSProcess but there's no
ConfigurationOfCommandShell.
What's working and what's not working?
Best regards
CdAB
Laurent can you plase add a link to my blog instead of what is now in my
NAME?
http://marianopeck.wordpress.com
Thanks :)
On Wed, Apr 13, 2011 at 8:18 PM, laurent laffont
laurent.laff...@gmail.comwrote:
Added !
Laurent.
On Wed, Apr 13, 2011 at 6:45 PM, Juan Vuletich j...@jvuletich.org
On Wed, Apr 13, 2011 at 8:49 PM, Juan Vuletich j...@jvuletich.org wrote:
Thank you Laurent! Also thanks for the link to Cuis.
Just a minor detail: my name reads 'Vueltich' instead of 'Vuletich'.
Oups sorry. Fixed.
Laurent.
Cheers,
Juan Vuletich
laurent laffont wrote:
Added !
On Wed, Apr 13, 2011 at 8:52 PM, Mariano Martinez Peck
marianop...@gmail.com wrote:
Laurent can you plase add a link to my blog instead of what is now in my
NAME?
http://marianopeck.wordpress.com
done
Laurent.
Thanks :)
On Wed, Apr 13, 2011 at 8:18 PM, laurent laffont
On 13.04.2011 19:40, Stephan Eggermont wrote:
JSR 292 explicitly talks about become: (calls it hotswap) and is supposed
to make it possible to run Smalltalk efficiently on a jvm.
What I know as hotswap as hot swap would not help with #become:. My
understanding is that when they went from an
Stefan,
Am 13.04.2011 um 19:40 schrieb Stephan Eggermont step...@stack.nl:
JSR 292 explicitly talks about become: (calls it hotswap)
the HotSwap I know is JVM technology introduced in Java 1.4 and is solely about
changing method implementations at run-time. I haven't read the JSR, but I'd be
Thanks a lot everybody for the reactions, this could become a nice discussion
next Friday.
All points raised are valid, I would like simple names and a compact
multipurpose hierarchy too.
On 13 Apr 2011, at 19:39, Dale Henrichs wrote:
Some thoughts from an old man (started programming before
On Tue, Apr 12, 2011 at 10:14 PM, laurent laffont laurent.laff...@gmail.com
wrote:
Today: TAssertable
Is it used ? Could not find any reference.
Laurent.
Comment Of The Day Contest - One Day One Comment
Rules:
#1: Each day a not commented class is elected. Each day the best
Perfect, I ll be there to bang heads ;).
So without Exception pre- or suffix seems to be nice. However I don't see the
need of using symbols over real classes. This feels indeed like going to stone
age of error handling, thats what you have polymorphism and ExceptionSets for.
Anyway, the main
A while back I asked if anyone on the squeak-dev list was in the greater
Seattle area and wanted to meet up. I did get a few responses. Thanks to
those who wrote back, and I apologize for the delay. I'm starting this up in
part to create a venue here where Smalltalk isn't automatically out as
Camillo,
Hey, I _am_ old, but not _that_ old:) ... There are a couple of things
that were invented in the Stone Age that have survived to today, so old
ideas are not immediately bad, because they are old:)
It feels like you are creating classes that are not much more than
symbols ...
I am
Excellent idea. I cc'ed vw.
BTW... I am imaging how the logo could look like...something betweenKurt
Cobain and the Smalltalk baloon heheheh.
On Wed, Apr 13, 2011 at 9:52 PM, Casey Ransberger
casey.obrie...@gmail.comwrote:
A while back I asked if anyone on the squeak-dev list was in the
OSProcess is supported and all tests are green in Pharo 1.1 and Pharo
1.2.
The stable version for Pharo 1.2 is the 4.4.0 but you can also load and
run 4.3.11 and 4.3.12 (although if you don't disable deprecations
warnings a lot of pop ups will show). 4.4.0 doesn't have problems with
deprecated
I completely agree with what Dale is saying... if you look at Patagonia (is
on squeak source) you will see a package call Patagonia-AssertionsModel
where I use something similar (if not the same) as Dale is saying... That
package reifies different types of assertions, but when an assertion fails,
LOL yeah and the roads here just go every which way... it's as if they gave
a guy two bottles of scotch, and wherever he walked with them, they built a
road. Seriously, though, if you think about it: Smalltalk has a culture that
was founded by musicians. One thing I'd really like to see is a room
Here is a small variation. It's not perfect, and most elements are
already in Stephane's text.
But maybe we can jump deeper in the first example that claims some explanations.
We can first explain that 0.1 will answer the Float nearest to (1/10).
Thanks to this important property, if we enter
I find the managing the exception hierarchy a bit strange... Do you
really have to manage anything more than just normal classes? Every
exception is related to a specific part of your code, just like other
classes. What's wrong with creating hundreds of small classes wherever
it's necessary?
From:
http://www.jcp.org/en/jsr/detail?id=292
We will also investigate support for hotswapping, the capability to modify the
structure of classes at run time.
So, yes, they planned to investigate a version of become:
The DaVinci Machine
http://openjdk.java.net/projects/mlvm/
On Wed, Apr 13, 2011 at 11:06 PM, Dave Mason dma...@mason-rose.ca wrote:
From:
http://www.jcp.org/en/jsr/detail?id=292
We will also investigate support for hotswapping, the capability to modify
the structure of classes at run time.
So, yes, they planned to investigate a version of
What's wrong is simple to explain: Your image is a namespace. The more
names you have, the more difficult it is to apprehend, understand and
reuse.
Wait, wait, wait, you might say, whether I use Symbols or Class names,
there are always the same number of names at the end.
Yes, but what makes the
On 04/13/2011 11:15 PM, Mariano Martinez Peck wrote:
On Wed, Apr 13, 2011 at 11:06 PM, Dave Mason dma...@mason-rose.ca
We will also investigate support for hotswapping, the capability to
modify the structure of classes at run time.
So, yes, they planned to investigate a version of
Maybe if that class has living instances, you must provide a way to
mutate the instances...
The easiest way is to create a mutated clone and becomeForward.
Nicolas
2011/4/13 Mariano Martinez Peck marianop...@gmail.com:
On Wed, Apr 13, 2011 at 11:06 PM, Dave Mason dma...@mason-rose.ca wrote:
ahagood point guys. Thanks :)
On Wed, Apr 13, 2011 at 11:29 PM, Nicolas Cellier
nicolas.cellier.aka.n...@gmail.com wrote:
Maybe if that class has living instances, you must provide a way to
mutate the instances...
The easiest way is to create a mutated clone and becomeForward.
Nicolas
By managing the class hierarchy:
Imagine trying to find meaningful exception classes in a class
hierarchy of 10,000 classes with significant nesting vs finding a
meaningful class in a hierarchy of 10 classes ... at what point does
the hierarchy get out of hand?
I think GemStone had 600
Nicolas,
Well put:)
Dale
On 04/13/2011 02:20 PM, Nicolas Cellier wrote:
What's wrong is simple to explain: Your image is a namespace. The more
names you have, the more difficult it is to apprehend, understand and
reuse.
Wait, wait, wait, you might say, whether I use Symbols or Class names,
On 13 Apr 2011, at 23:27, Göran Krampe wrote:
On 04/13/2011 11:15 PM, Mariano Martinez Peck wrote:
On Wed, Apr 13, 2011 at 11:06 PM, Dave Mason dma...@mason-rose.ca
We will also investigate support for hotswapping, the capability to
modify the structure of classes at run time.
Is it such a problem if you duplicate a certain exception class? At the
moment you'll do the same anyway by not completely writing the exact
same symbol.
And if the problem is not finding classes anymore, maybe we need a
better way of organizing the exception classes away from the standard
Reusing is important because it means reducing the number of concepts
and reducing the complexity.
Once we fail to manage this complexity, the image grows exponentially:
two times more classes means half chance to find matching information,
and twice to reinvent.
But of course, that does not mean
On 04/13/2011 02:58 PM, Toon Verwaest wrote:
Is it such a problem if you duplicate a certain exception class? At the
moment you'll do the same anyway by not completely writing the exact
same symbol.
It's a simple matter of namespaces and volume of names ... with a large
open ended namespace
Hello all,
I have been successful in using unixODBC and a Postgres driver to communicate
with what I believe is an encrypting server (at least according to pgadmin). I
did lots of things, such as building the driver from source, that might have
been critical, but I strongly suspect that the
I missed the start of the thread but I've been using PostgreSQL and Pharo for
quite a while on Windows XP (both PostgreSQL Pharo). So far, Pharo is
rock-solid with ODBC, at least on WinXP !
-
Benoit St-Jean
Yahoo! Messenger: bstjean
A standpoint is an intellectual horizon of
You didn't miss anything that I can see - just passing along something I wish I
had found in writing a few hours ago =:0
I was motivated to get ODBC working specifically because it has worked well for
me too. At least in the version of ODBCLibrary that I am using, there is some
room to grow
On Apr 13, 2011, at 5:00 PM, Dale Henrichs wrote:
To say that if one were to handle the KeyNotFoundException, they will need
the complete context, I prefer to say Until one needs the complete context
of the KeyNotFoundException, don't bother creating class
I hope (as an outsider) that this
79 matches
Mail list logo
