It is even more true since the beginning of Pharo 3.0. I see so many things
integrated, bugs quickly fixed. Nice job Pharoers :)
2013/5/5 Max Leske
> +100!
>
> Special thanks to Stef and all the guys at Lille. You're responsible for a
> lot of the drive that we generate.
>
> Max
>
> On 05.05.20
can interpret it with a loop
[currentASTNode hasNextNode] whileTrue: [ self interpret: currentASTNode
nextNode ].
And interpretation looks like :
interpret 2
interpret 1
interpret + with two precedent results on stack
interpret ^ with precedent result on stack
2013/5/4 Clément Bera
> 2013/
2013/5/4 stephane ducasse
>
> On May 4, 2013, at 1:04 AM, Igor Stasenko wrote:
>
> > Did i said already that i don't like how ASTInterpreter implemented? :)
>
>
> We will let perfection for later :)
>
It is not a question of perfection or so.
Igor does not like that we interpret recursively th
It is AlainTreeModel.
Ben told me, I cheated. When I don't know I go ask him. Reportedly he has
sent a mail yesterday about that. But I didn't see it.
2013/5/3 Clément Bera
> It is AlainTreeModel.
>
> Ben told me, I cheated. When I don't know I go ask him. Reporte
It is AlainTreeModel.
Ben told me, I cheated. When I don't know I go ask him. Reportedly he has
sent a mail yesterday about that. But I didn't see it.
2013/5/3 roberto.mine...@usi.ch
> Ok, what's "the correct implementation of tree"?
>
> On May 3, 2013, at 4:48 PM, Benjamin >
> wrote:
>
> >
Hum several of your improvements look cool. Marcus and I are currently
working on Opal. We are quite busy for the next two weeks but we'll find
some time to have a deeper look on your changes. Then we'll mail you back.
2013/5/1 Nicolas Cellier
> Opal is fun.
> I have a few simplifications to pr
Yeah it would be nice.
We wanted to avoid stuff as "primitiveChangeClassTo:". It is nice we can
avoid them with Spec.
Btw the new inspectors are quite stable so Pharo 3.0 should have soon Spec
inspectors by default.
2013/4/30 stephane ducasse
> ben
>
> we should add that to the spec chapter.
There is currently no way to do this.
There is a good reason for that, the new debugger has got inspectors only
since yesterday, so it was hardly usable before. Today I peer programmed
all day long with Camillo on the new inspectors, based on Spec and a new
model, and we are about to have somethin
* "Do I have to use Pharo 3.0 to have black labels?"*
If you want to implement something for a customer, you should *not* use
Pharo 3.0. It is in alpha state which means you might have unexpected bugs
or VM crashes (even if the alpha version is currently quite stable). The
best for you would be to
* "Do I have to use Pharo 3.0 to have black labels?"*
If you want to implement something for a customer, you should *not* use
Pharo 3.0. It is in alpha state which means you might have unexpected bugs
or VM crashes (even if the alpha version is currently quite stable). The
best for you wo
I don't know any easy way to do it right now.
What I would do, as LabelModel>>#text: can take a Text instance as
argument, is :
self text: ('the string I want to display' asText addAttribute: TextColor
red)
But of course it is not very good.
Clement
2013/4/29 roberto.mine...@usi.ch
> Hi,
>
>
yeah I heard these symbol were hardcoded in metacello so they don't work by
default.
There's no tag yet for pharo 3.0.
2013/4/23 Goubier Thierry
> Hi,
>
> is there already a #'pharo3.0.x' tag in metacello when we want to have
> different package version in Pharo 3.0 instead of 2.0 ? I tried
>
And then you need to save the file, and then you need to reload the map ...
Again save the file, and reload ...
Each time you reload the program restart at the beginning of course.
Yeah that would look better in Pharo, basically the same without reload
button but runtime behavior modifications.
Yeah this is really cool. Especially now BlockClosure and optimized
BlockClosure (to:do:, ifTrue:ifFalse:, ifNil:ifNotNil:, and:, or:) have the
same behavior for debugger byte code to source code mapping, for
decompilation, ...
2013/4/17 Marcus Denker
> Hi,
>
> We implemented this today:
>
> #s
These was because Destructive regression tests were loaded in the image.
Should be fixed soon.
2013/4/16 Goubier Thierry
> Le 16/04/2013 14:11, Marcus Denker a écrit :
>
>
>> On Apr 16, 2013, at 2:08 PM, Esteban Lorenzano
>> wrote:
>>
>> oops... those are a lot of regressions :)
>>>
>>
>> Thi
Because I used it and there are some problems that might result in image
freeze. Explicitely, problems with the debugger byte code to source code
mapping or with new class compilation.
And it was not planned to put Opal by default on Pharo because it cannot
compile Slang whereas the old compiler c
+1
I needed the selectPackageBrowser for the Tree coverage tool and I had to
duplicate code because it was in code critics browser and not external.
2013/4/15 stephane ducasse
> Indeed Merlin would be useful.
> I cleaned it a bit when migrating to smalltalkhub.
>
> Stef
>
> > I want to extract
Yeah the video is really cool.
Please guys tweet about it :)
2013/4/10 Nicolas Petton
> Awesome!!
>
> Nico
>
> On Apr 10, 2013, at 4:20 PM, Esteban Lorenzano
> wrote:
>
> Hi,
>
> I made a small video to show how work the “life environment” we pharoers
> (and every smalltalker) always talk. Th
that have been reached.
> The method #checkPoint: could then use some attributes to the
> CompiledMethod.
>
> This is a common technique when (i) the VM does not give you what you need
> and (ii) when you do not want to change the VM.
>
> This is something I wanted to do for year in
n Apr 6, 2013, at 10:35 AM, Clément Bera wrote:
>
> > This is exactly that. The tree coverage tool is a subclass of
> AST-interpreter, which adding to the interpretation marks the nodes. And
> then I use this marking to color the source code. And I use as you said RB
> ast.
> >
nk
>
> On 6 April 2013 11:00, Clément Bera wrote:
> > Actually, it is quite different than Jejak.
> >
> > Implementation wise, Jejak used Opal so I guess it relies on bytecode
> > modification to do its analysis where my tool relies on ast annotations.
> >
>
Actually, it is quite different than Jejak.
Implementation wise, Jejak used Opal so I guess it relies on bytecode
modification to do its analysis where my tool relies on ast annotations.
This implies some difference in features. It seems that Jejak record all
calls, all values and all assignments
I forward this to Pharo project it might interest some of you too.
-- Forwarded message --
From: Clément Bera
Date: 2013/4/5
Subject: Game prototype with Amber deployed
To: amber-l...@googlegroups.com
Hello amber community,
Eight months ago I met Nicolas Petton, discovered
about Squeak compared to Pharo newcomers don't know
both of them.
Regards
2013/3/29 Frank Shearar
> On 29 March 2013 15:30, Clément Bera wrote:
> > Interesting, this English Pharo wiki page.
> >
> > I quote : 'Pharo is now organized as a benevolent dictatorship o
o introduce Pharo in the page instead of
having a bunch of critics against some people of the community.
Regards,
2013/3/28 Serge Stinckwich
> On Thu, Mar 28, 2013 at 4:40 PM, Clément Bera
> wrote:
> > I tried to write some more stuff on the French Pharo wiki page :
> > htt
I tried to write some more stuff on the French Pharo wiki page :
http://fr.wikipedia.org/wiki/Pharo .
I moved all the reference to history (birth of smalltalk, relation with
companies, forking) in the history section. I tried to focus the page on
How to use Pharo and Who uses Pharo. I would like t
Yeah it's fine. Thank you.
2013/3/27 Janko Mivšek
> Yuriy, thanks for your explanation, I now understand the intent of your
> idea better. Good luck with it!
>
> Janko
>
> Dne 26. 03. 2013 20:24, piše Yuriy Tymchuk:
> > Hi Janko,
> >
> > To be honest, you are touching Java only by parsing it's c
Title: A Pharo Image running on top of VirtualBox with the help of a Linux
micro kernel
Level: intermediate
Possible mentor: Clement Bera
Possible second mentor: Marcus Denker, Camillo Bruni
Description
Archiving Pharo / Squeak Image is not easy : it depends on a VM, that
depends on a
Hello,
I have no documentation but examples. Basically either :
- you choose to write the default spec with row and columns, you can
precise height or row of some elements. With this method it is easier to
get what you want but quite slow sometimes.
ex : (Inspector UI)
defaultSpec
^ SpecLayout
2013/3/12
> Hi! We're sending this automatic email twice a month, to give the
> community an opportunity to easily know what's happening and to coordinate
> efforts. Just answer informally, and feel free to spawn discussions
> thereafter!
>
>
Do I have to answer to that mail too ? I'm impressed
There was a discussion about that recently now the autocompletion is
partially done with tab and partially with enter by default. In your case
tab didn't work because it was necessary to use enter.
You can change in the setting browser to your favorite setting.
2013/3/3 stephane ducasse
> Check
Hello,
I was looking for VM tests in the Pharo image and I found the
class IslandVMTweaksTestCase. The strange thing is its comments :
"Test case for some tweaks to the VM that Islands requires. These tests are
largely for documentation; with an un-tweaked VM, the tests mostly still
succeed, albei
>
> Even weirder: played with the debugger and sayed Over Over Over then
> Proceed and it worked. Strange
>
> What do you mean exactly ? You were not able to Proceed after clicking on
Over several times on Pharo 1.4 ?
I've just made a fix in the debugger that was integrated today.Give me more
d
2013/2/5 Denis Kudriashov
2013/2/5 Esteban Lorenzano
> RizelVM
What is RizelVM?
Correct me if I am wrong, but Rizel VM is a VM that permits to benchmark.
It was done by a student and worked nicely but it is not maintained any
more.
>
Actually this was in the bug tracker
http://code.google.com/p/pharo/issues/detail?id=2759&can=1&q=orderedDictionary&colspec=ID%20Type%20Status%20Summary%20Milestone%20Difficulty
error 2759
This OrderedIdentityDictionary is only used for user interface that is why
it is on Spec-Core for now. See
Hello,
In fact IR->AST is useless but if you don't have the pharo sources aside
from your vm.
You right, BC -> IR is kind of a trivial 1 to 1 mapping. But even if it is
trivial, it had to be done :)
Adding to integration and decompiler, I think the doIt compilation might
not be finished too. It
Yeah actually they showed it at the moose lesson this afternoon. The moose
team have moose analysis graphs on their jenkins. It could be nice to have
it also on the Pharo/rmod jenkins.
2013/1/18 Camillo Bruni
> I love to see this! :)
>
> I just hear today, that apparently for moose they have the
I dont know if this can help you but the manifest classes are updated
through the codecritics change browser. It keeps in memory the false
positive for the future use of code critics
2013/1/18 Camillo Bruni
> Why do the Manifest.* classes have no class comments?
>
> This is highly confusing, as
Several months ago I made a prototype of a small game in amber. (To play my
prototype, download it, run index.html and click Multiplayer>beta fight. The
source is here : https://github.com/clementbera/easnoth:. It uses
Jquery.getJSON() so it might not work on some web browsers/computers)
I asked s
I reported. I am doing the slice.
2012/12/9 Marcus Denker
> Can you add a issue at
> http://code.google.com/p/pharo/issues/list
> ?
> On Dec 8, 2012, at 5:57 PM, Ciprian Teodorov
> wrote:
>
> It seems that this issue can be fixed by modifying the = method in
> Association.
>
> Association>>= a
Yeah here in your BlockClosure [^1] the homeContext and the outerContext is
the context created for UndefinedObject>>DoIt.
2012/11/17 Frank Shearar
> On 16 November 2012 16:53, Stéphane Ducasse
> wrote:
> > Hi guys
> >
> > I'm updating the exception chapter to show the interplay between
> excep
Hello,
I don't understand something on BlockClosure>>ensure:. Why does it use
'self valueNoContextSwitch' and not 'self value' ? In which case is there
an issue ?
Thank you for any answers
BlockClosure>>ensure: is implemented this way :
ensure: aBlock
"Evaluate a termination block after evalua
42 matches
Mail list logo
