Le 05/09/2014 08:43, p...@highoctane.be a écrit :
Yes there is that annoying thing with windows that set things bacl to
white. Why is that indeed?
It is Window theme to keep it consistant I guess
--
Dr. Geo - http://drgeo.eu
iStoa - http://istao.drgeo.eu
no smalltalk around is “smalltalk”, technically they are all dialects and Pharo
is just one dialect more.
smalltalk-80 itself does not exist since… well, smalltalk-80 :)
so no, your code would not be directly portable to other smalltalks (with the
possible exception of gemstone).
Esteban
On 0
Hi everyone!
When loading a package via Monticello, while compiling methods it gives an
error:
Syntax Error: Cannot store into and then a method.
What does it mean?
Best,
Mark
--
View this message in context:
http://forum.world.st/Syntax-Error-Cannot-store-into-tp4776675.html
Sent from the Ph
which package?
On 06 Sep 2014, at 10:28, Mark Rizun wrote:
> Hi everyone!
>
> When loading a package via Monticello, while compiling methods it gives an
> error:
> Syntax Error: Cannot store into and then a method.
> What does it mean?
>
> Best,
> Mark
>
>
>
> --
> View this message in con
Package of my project RewriteTool.
Here it is:
http://smalltalkhub.com/#!/~MarkRizun/RewriteTool/packages/RewriteTool
2014-09-06 11:33 GMT+03:00 Esteban Lorenzano :
> which package?
>
>
> On 06 Sep 2014, at 10:28, Mark Rizun wrote:
>
> > Hi everyone!
> >
> > When loading a package via Monticell
well, this is weird :)
the error you have is usually because you have something like this:
myMethod: aParameter
…
aParameter := something.
…
(same can happen with blocks).
you cannot assign a parameter… and compiler protests if you try.
but I wander how you could introd
You are right there is such a code.
And it's really strange how it compiled earlier:)
Thanks
2014-09-06 11:42 GMT+03:00 Esteban Lorenzano :
> well, this is weird :)
> the error you have is usually because you have something like this:
>
> myMethod: aParameter
> …
> aParameter := something.
> …
>
If you missed our discussion with Marcus, Opal allowed constructs like that
until week ago.
Uko
Sent from my iPhone
> On 06 Sep 2014, at 10:46, Mark Rizun wrote:
>
> You are right there is such a code.
> And it's really strange how it compiled earlier:)
> Thanks
>
>
> 2014-09-06 11:42 GMT+0
Now that's not strange.
Thanks for info
2014-09-06 11:49 GMT+03:00 Yuriy Tymchuk :
> If you missed our discussion with Marcus, Opal allowed constructs like
> that until week ago.
>
> Uko
>
> Sent from my iPhone
>
> On 06 Sep 2014, at 10:46, Mark Rizun wrote:
>
> You are right there is such a co
I don’t know what technical incompatibilities may exist, but for many
practicalities Pharo is compatible with Squeak and other dialects. I am using
an application (Todd Blanchard’s HTMCSS parser and validator) which was
originally written for Squeak. Some years ago I ported it to Dolphin Smallta
he, I missed that discussion :)
good to know!
Esteban
On 06 Sep 2014, at 10:53, Mark Rizun wrote:
> Now that's not strange.
> Thanks for info
>
>
> 2014-09-06 11:49 GMT+03:00 Yuriy Tymchuk :
> If you missed our discussion with Marcus, Opal allowed constructs like that
> until week ago.
>
>
yes… 99% of the time Pharo and Squeak will be compatible.
we share the vm and a large part of the codebase.
but libraries are slowly diverging so you might find that what works in the one
does not works automatically in the other.
but again… my point is that all smalltalks are dialects… there
Hi,
i ran a program that did some calculations for about an hour. in between
i occasionally moved the cursor (so that the computer did not go to
sleep) and probably clicked occasionally on the browser. after some time
this resulted in several errors from the browser (the program itself
does no
In my opinion, this dialect thing is getting increasingly silly. And
confusing. And silly.
2014-09-06 10:01 GMT+01:00 Esteban Lorenzano :
> yes… 99% of the time Pharo and Squeak will be compatible.
> we share the vm and a large part of the codebase.
> but libraries are slowly diverging so you mi
Werner Kassens wrote:
Hi,
i ran a program that did some calculations for about an hour. in
between i occasionally moved the cursor (so that the computer did not
go to sleep) and probably clicked occasionally on the browser. after
some time this resulted in several errors from the browser (the
Hi,
On 09/06/2014 03:35 PM, Ben Coman wrote:
Just to be clear, by "did some calculations for an hour" do you mean the
Image basically locked up during the calculation, and the mouse clicks
were queued until the calculation ended?
exactly, after the calculation different windows spring into th
Sergi Reyner wrote:
In my opinion, this dialect thing is getting
increasingly silly. And confusing. And silly.
Identity and vision are important parts of community building. I
wasn't around when Pharo forked from Squeak, but I can see it was
useful to build a separate identity to distingu
In my opinion, this dialect thing is getting increasingly silly. And
confusing. And silly.
It is not getting. It was like that already back in 1998 and before too.
The syntax is one thing the libraries are another one!
BTW I opened last year a VW from 1994 and I do not want to live there :)
Werner Kassens wrote:
Hi,
On 09/06/2014 03:35 PM, Ben Coman wrote:
Just to be clear, by "did some calculations for an hour" do you mean the
Image basically locked up during the calculation, and the mouse clicks
were queued until the calculation ended?
exactly, after the calculation different
I'd like to learn a bit more about the implementation of Weak objects.
For example, I see...
Magnitude>LookupKey>Associaton >> key: aKey value: anObject
key := aKey.
value := anObject
Magnitude>LookupKey>WeakValueAssociaton >> key: aKey value: anObject
key := aKey.
self value: an
Magnitude weakSubclass: #WeakKeyAssociation
instanceVariableNames: 'value'
classVariableNames: ''
category: 'Collections-Support'
weakSubclass: ...
On 06 Sep 2014, at 16:47, Ben Coman wrote:
>
> I'd like to learn a bit more about the implementation of Weak objects. For
Sven Van Caekenberghe wrote:
Magnitude weakSubclass: #WeakKeyAssociation
instanceVariableNames: 'value'
classVariableNames: ''
category: 'Collections-Support'
weakSubclass: ...
Oh! the shame
Thanks Sven.
On 06 Sep 2014, at 16:47, Ben Coman wrote:
I'd like to l
> Sorry, I can't tell across email if that is
> tongue-in-cheek since you know exactly what to do, or you are looking
> for advice :)
Hi Ben,
i did not want to irritate you, i just thought perhaps i need to do some
sort of clean up with that fork thing afterwards (like deleting a
process or wh
I find myself saying Pharo Smalltalk and Github marks our code as
Smalltalk.
Which is fine.
"Pharo is Pharo" indeed.
But the contents of the Blue Book still holds true.
What I do know is that I enjoy programming in Pharo more than with anything
else.
VisualWorks may have more power but I can't
Le 06/09/2014 16:36, stepharo a écrit :
In my opinion, this dialect thing is getting increasingly silly. And
confusing. And silly.
It is not getting. It was like that already back in 1998 and before too.
Yes. Who remember the differences between Envy / Parcplace / Digitalk /
Smalltalk-mt /
On 06 Sep 2014, at 17:42, p...@highoctane.be wrote:
> At the moment I am running Pharo every single day for all day long and it is
> a great recurring experience.
Good for you !
Werner Kassens wrote:
> Sorry, I can't tell across email if that is
> tongue-in-cheek since you know exactly what to do, or you are looking
> for advice :)
Hi Ben,
i did not want to irritate you, i just thought perhaps i need to do
some sort of clean up with that fork thing afterwards (like de
On Sat, Sep 06, 2014 at 06:09:15PM +0200, Thierry Goubier wrote:
> Yes. Who remember the differences between Envy / Parcplace /
> Digitalk / Smalltalk-mt / Smalltalk/X / Dolphin Smalltalk ?
I still play with Smalltalk/X. It is very different from Pharo, but it is an
implementation of Smalltalk non
28 matches
Mail list logo
