Re: [Pharo-dev] Problem with Finder

Hello, 2014-04-06 12:30 GMT-07:00 jannik laval : > Probably, you can answer another problem: > > During reengineering a system (Phratch), I need to know senders / > implementors in a specific group of package. > The only way I found to do this is to use the Finder. > Does exist another way ? > >

Re: [Pharo-dev] Puzzled

Hey, I remembered removing the initializeAutoRefresh code from the debugger. Perhaps I didn't commit that package. Or I forgot this one. 2014-04-03 12:34 GMT-07:00 Pharo4Stef : > ok now I understand: an endless loop inside the debugger creation. I do > not understand why we did not address it w

Re: [Pharo-dev] Fwd: Feedback for Pharo 3

Hello, About #valueWithInterval: and co, I added that in Pharo because they are present in javascript with the same name and I think they were very convenient to easily implement UI animation. According to the number of discussion about these 2 methods, I think they are useful, but we should ret

Re: [Pharo-dev] Crazy Smalltalk code snippets

Hello, The pharo continuations were ported from seaside because several people were using seaside continuations in non seaside related projects. I wouldn't rely on assigning the receiver on thisContext because it's a bit buggy. See: ByteSymbol>>bar thisContext receiver: #foo. ^ self 10 timesRe

Re: [Pharo-dev] Just found, i can compile this:

2014-03-18 18:31 GMT+01:00 Max Leske : > > On 18.03.2014, at 18:17, Camille Teruel wrote: > > > On 18 mars 2014, at 17:02, Clément Bera wrote: > > Hello, > > For blockClosures it is normal, block closure arguments have always been > assignable since smalltalk-80. &

Re: [Pharo-dev] Just found, i can compile this:

Hello, For blockClosures it is normal, block closure arguments have always been assignable since smalltalk-80. We could add a warning to discourage it, but we cannot forbid it, or we will not be able to load lots of frameworks and libraries that use it. So 12419

Re: [Pharo-dev] EyeTreeInspector not ready for prime-time

Hello, EyeInspector>>#limit1 and limit2 are here to limit the size of collection shown. In the old inspector the limits were 100 and 10, which means you could see the first 100 and the last 10 elements. We put more in the EyeInspector because even for 10 elements it was not lagging. But we did

Re: [Pharo-dev] Sort by property

at in the end I implemented my own collection. It will be a real alternative when we will have clean blocks. (For that we need to merge with Cog's trunk which includes merging Spur)... 2014-03-11 10:45 GMT+01:00 Yuriy Tymchuk : > > On 11 Mar 2014, at 10:19, Clément Bera wrote: > >

Re: [Pharo-dev] Sort by property

Hello, [ Note: So in the default Pharo the method is named #sort: not #sortByProp: or #sortBy: but it's a detail ] I like this idea because I also have always the problem. So I would like to be able to do: projects sort: #creationDate The implementation would be, in a similar fashion to how Sym

[Pharo-dev] Bug in valueWithin:onTimeout: ?

Hello guys, Yesterday I had this problem that at startup a pharo image has several process running at priority 40. The problem is that my tests (run from command line) trigger #valueWithin:onTimeout: and the protected block (the block calling #valueWithin:onTimeout:) would always timed out for the

Re: [Pharo-dev] What happened with petitmarkdown?

Hey, Camillo moved all his repo on github and deleted the ones from smalltalkhub. 2014-03-07 8:10 GMT+01:00 Damien Cassou : > Try on github > On Mar 6, 2014 1:27 PM, "Stephan Eggermont" wrote: > >> Camillo, >> >> While fixing some ci builds, I noticed that at least some of your >> smalltalkhub

Re: [Pharo-dev] AST-Interpreter on CI is green

Thanks for fixing it. Tthe tests are green but last time I tried the regression tests (package AST-Interpreter-PharoTest) were failing. 2014-03-06 13:18 GMT+01:00 Stephan Eggermont : > The build was red, referring to dh83/ast-Interpreter (empty). > Changed the config to use Pharo/AST-Interprete

Re: [Pharo-dev] How can I tell the compiler to accept assignment as underscore?

Well this is a parser problem. The parser should mark as an assignment AST node the code with the underscore and everything would work fine. Now I don't really understand RBParser ... 2014-03-03 7:53 GMT+01:00 Pharo4Stef : > Hi > > How can I tell the compiler to accept assignment as underscore?

Re: [Pharo-dev] Status of the VM?

Hey, It's fun because I looked at the JVM list and most point looked irrelevant as you described. It seems that the only thing we miss is the GC hook: we could have a selector in special object array to call at each GC on the 'Smalltalk' object to trigger a method in the image that would be by de

Re: [Pharo-dev] Status of the VM?

Hello, This is true but this is a work in progress. Right now this feature is not stable. I will keep you in touch. I think in May I may have something stable enough (I will work with Eliot on April) but it will not be on the default VM. It will be available in the default pharo VM at some point b

Re: [Pharo-dev] Q: Restart the image

Hello, One possibility is to save, then open again the current image with OSProcess, lastly close the first image. This would work for sure. The code would look like: Smalltalk snapshot: true andQuit: false. OSProcess executeInCommandLine: './pharo myImage.image'. Smalltalk snapshot: false andQu

Re: [Pharo-dev] LargePositiveInteger indexIfCompact isZero (inconsistency)

Hello, Try : Smalltalk compactClassesArray at: 5 put: nil. LargePositiveInteger becomeUncompact. LargePositiveInteger becomeCompactSimplyAt: 5. then: LargePositiveInteger indexIfCompact. is correct. Same script is needed for LargeNegativeInteger. I think this bug is due to the introduction

Re: [Pharo-dev] Log of the february dev meeting

Hello, 2014-02-23 14:51 GMT+01:00 Alexandre Bergel : > Hi! > > What is PharoS? > For marketing, Cog VM => Pharo VM Stack VM => PharoS VM > > Alexandre > > > Le 22-02-2014 à 7:44, Pharo4Stef a écrit : > > > > HI guys > > > > we did not have a full team meeting since nov so here is the log of

Re: [Pharo-dev] What will change in Pharo with Spur the new Cog memory manager ...

better than they used to due to the lack of full GC pauses. Now that's the theory we need to make it real and this summer we will see... > > > > > On Feb 6, 2014, at 12:48 PM, Clément Bera wrote: > > Hello pharoers, > > The new Cog memory manager, Spur, is simply *

[Pharo-dev] What will change in Pharo with Spur the new Cog memory manager ...

Hello pharoers, The new Cog memory manager, Spur, is simply *amazing*. I saw at FOSDEM that some of you were interested in it, but unfortunately you were lacking information about it. I wrote a one page article that sums up Spur's new features so every one can know what will be better. There's no

Re: [Pharo-dev] OpalCompiler and Semantic analyzer

Arf you are too fast to fix bugs we don't have time to review :-) I guess Marcus or I will have a look friday afternoon, if possible before. Regards. 2014-02-05 Nicolai Hess : > 2014-02-03 Nicolai Hess : > > Can someone with some background knowledget on the opal compiler, >> look at my fix fo

[Pharo-dev] Smalltalk job

Hiring now! Searching for a Smalltalk Developer - 6 month (renewable) contract with a major direct client in Omaha Nebraska! Call or email Natalie Wharton: # 630.465.7833 nwhar...@cssus.net Major qualifications, * 3+ years of Smalltalk, preferably VisualWorks * 3+ years of relational database, eit

Re: [Pharo-dev] When code performs super...

Right, that's why there's #perform:withArguments:inSuperclass: . Amazingly, #perform:withArguments:inSuperclass: works only if the superclass is in the lookup chain but does not necessarily requires the direct superclass. Let's say A inherits from B inherits from C. A>>foo ^ #c B>>foo ^

Re: [Pharo-dev] subscript out of bounds in protocol creation

I had the same problem. I had to reload my project from a fresh image to solve it. Very hard to reproduce. In addition, after editing a few method you cannot anymore edit the class comment (you need to open another Nautilus to do it). 2014/1/31 Jordi Delgado > Hi, > > I realized that sometimes

Re: [Pharo-dev] bugs with blocks

I remembered this situation was true in a bug report. Seemingly it is when you do context sourceNode on a dead context. 2014/1/27 Nicolai Hess > 2014-01-27 Camille Teruel > > >> On 27 janv. 2014, at 10:44, Camille Teruel >> wrote: >> >> >> On 27 ja

Re: [Pharo-dev] bugs with blocks

Hello, I don't think this line was there by mistake. In some cases, the activePC with this code is lower than the startpc and then the debugger shows an error 'no ast node found at this pc' and cannot properly highlight the current executed code because the pc is outside the method bytecode. I rem

Re: [Pharo-dev] Null Object Pattern

Hello, specific messages (control flow oriented messages) are inlined and you cannot override them (same problem in the old and the new compiler). In Opal we introduced some kind of settings to force the compiler not to inline messages when it is not needed. This can be done at method level with a

Re: [Pharo-dev] logCr in SpecDebugger

No. Please remove it. 2014/1/9 Esteban Lorenzano > Hi, > > I found this in SpecDebugger>>#updateCodeFromContext: > > ... > self logCr: aContext receiver class. > ... > > is there any any reason? > > Esteban > >

Re: [Pharo-dev] Can we override == in Pharo ?

ry. Anyway it didn't provide a lot of performance (just removed 1 indirection). 2014/1/6 Frank Shearar > On 6 January 2014 11:11, Nicolai Hess wrote: > > 2014/1/6 Clément Bera > >> > >> Hello, > >> > >> here I have a class > >> >

[Pharo-dev] Can we override == in Pharo ?

Hello, here I have a class A>>== ^ true Now: a := A new. b := A new. a == b "Answers false" a perform: #== with: b "Answers true" Do I have to remove the usage of the byte code for #== in the compiler to be able to override == ?

Re: [Pharo-dev] FFI loadable in Pharo 3.0

Yeah Camillo Bruni made a compatibility package for FileDirectory to be able to move from Pharo 1.4 to Pharo 2+ easily. I don't remember where it is... I've just checked repos of the teams Pharo and Pharo extras on smalltalk hub and there's a project named* FileSystemLegacy*

[Pharo-dev] FFI loadable in Pharo 3.0

Hello, https://pharo.fogbugz.com/f/cases/12438/Old-FFI-Check-that-it-is-parsed-correctly-and-works I was fixing this bug with Guille today. You can load FFI with the Configuration browser. Please try to load, use it and review the issue. We also added the new configuration in the old metacello

Re: [Pharo-dev] [OT] Data structure visualizations

This is amazing. These visualizations, Breadth-First Search and Depth-First Search, are really cool. I use them all the time and learnt them from a compiler book, but in the book you cannot see things moving around :). 2013/12/18 Sebastian Sastre > Making those visual doesn't look that bad huh

Re: [Pharo-dev] Smalltalk in a C World

How can people even know Smalltalk MT still exist with their website and their communication ? I looked at other Smalltalks a while ago, for Smalltalk MT I clicked on "what's new" on their website and I got that: [image: Images intégrées 1] Then I thought this Smalltalk was dead (nothing new in

Re: [Pharo-dev] Open vs Closed issues visualised

Does that mean we closed around 2000 issues since May ? And all the time there were around 100 issues opened ? 2013/12/5 Marcus Denker > start is may this year... > <>

Re: [Pharo-dev] Opal hook?

It didn't halt on your machine because you didn't copy and paste the code that halts (i guess I wrote too much code in the mail so it was not clear). You copied the code that I explicitly said that doesn't halt because the error is raised at compilation time. This code halts (copy, paste and run i

Re: [Pharo-dev] CompiledMethod>>#= is broken

Marcus/Esteban I opened the bug and it is ready to integrate. https://pharo.fogbugz.com/f/cases/12331/Fixed-CompiledMethod 2013/12/3 Eliot Miranda > > > > On Tue, Dec 3, 2013 at 11:27 AM, Eliot Miranda wrote: > >> >> >> >> On Tue, Dec 3, 2013 at 9:49 AM, Oscar Nierstrasz < >> oscar.nierstr...@g

Re: [Pharo-dev] explore is broken

It works in 30615 but is broken in 30616. No one knows about it yet I guess because 30616 is from today. The bug is from the one of the 30616 change. Can someone with a good Spec knowledge have a look at it ? 2013/12/3 Oscar Nierstrasz @ gmail > > There is something wrong with the EyeTreeInsp

Re: [Pharo-dev] Opal hook?

* In your case, while loading from Monticello the code is compiled and evaluated in non interactive mode. Therefore it cannot trigger the default action of OCUndeclaredVariableWarning which is a UI event. So it sets by default the unknown global to: Undeclared at: varName asSymbol put: nil.

Re: [Pharo-dev] Opal hook?

Then for your project replace ProtoObject by StubRootClass in UndefinedObject>>subclass:instanceVariableNames:classVariableNames: poolDictionaries:category: it will work. An alternative is to catch OCSemanticWarning or its subclass OCUndeclaredVariableWarning while loading the new classes and exe

[Pharo-dev] Spec table problem

This example I used to have does not work any more in the latest Pharo 3: tree := TreeModel new. tree openWithSpec. tree columns: (Array with: (TreeColumnModel new displayBlock: [:node | node content first asString ]; headerLabel: 'Name'; yourself) with: (TreeColumnModel new displayBlock: [:node

Re: [Pharo-dev] Versionner CI?

The jobs's on Rmod: https://ci.inria.fr/rmod/job/Versionner/ 2013/12/3 Sean P. DeNigris > I was surprised there was no job on community contributions... > > > > - > Cheers, > Sean > -- > View this message in context: > http://forum.world.st/Versionner-CI-tp4726899.html > Sent from the Pharo

Re: [Pharo-dev] Opal hook?

Well if the class does not exists it calls the method on UndefinedObject (UndeclaredBinding). And you have: UndefinedObject>>subclass: nameOfClass instanceVariableNames: instVarNames classVariableNames: classVarNames poolDictionaries: poolDictnames category: category "Calling this method is now

Re: [Pharo-dev] Stepping through with GLORP Proxies

at 11:44 AM, Clément Bera wrote: > >> One thing with Pharo 3.0 is that the debugger is quite different than it >> used to be. >> >> It is now split into a model (DebugSession + DebugContext) and the view, >> SpecDebugger. I don't know what Eliot does have to chan

Re: [Pharo-dev] Stepping through with GLORP Proxies

One thing with Pharo 3.0 is that the debugger is quite different than it used to be. It is now split into a model (DebugSession + DebugContext) and the view, SpecDebugger. I don't know what Eliot does have to change but the new code may require some extra work due to the debugger being different.

Re: [Pharo-dev] Stepping through with GLORP Proxies

Hello, 2013/11/30 Eliot Miranda > > > > On Fri, Nov 29, 2013 at 2:22 PM, Esteban A. Maringolo < > emaring...@gmail.com> wrote: > >> 2013/11/29 Eliot Miranda : >> > On Fri, Nov 29, 2013 at 1:06 PM, Marcus Denker >> > wrote: >> >> On 29 Nov 2013, at 22:03, Eliot Miranda >> wrote: >> >> > Does th

Re: [Pharo-dev] [Review needed] fix for Pharo2 "text highlighting incorrect"

Are you talking about text highlighting in the debugger or is this not related ? 2013/11/28 Goubier Thierry > > > Le 27/11/2013 20:36, Stéphane Ducasse a écrit : > > >> That's me >>> >>> the solution provided doesn't work very well either. >>> >>> I would need to spend time on the code used t

Re: [Pharo-dev] [Vm-dev] Frequent SegFaults in PharoVM with Pharo 3.0

loops on all objects should not create an object (even a context) ...). If we really want that we will invest time. But right now it is not a priority. > > > On 25.11.2013, at 18:42, Eliot Miranda wrote: > > > > > On Mon, Nov 25, 2013 at 9:37 AM, Sven Van Caekenberghe wrote:

Re: [Pharo-dev] Nautilus no longer guards against changed methods

I lost a lot of changes because of that too. Very boring bug. 2013/11/26 Stephan Eggermont > Chris wrote: > >Sean wrote: > >> In general in UIs, he best approach is to do what the user requests > without > >> hesitation, and make everything undoable. > > > >Ah, thanks for saying that. People n

Re: [Pharo-dev] The Second Coming of Java article

To have Java running on top of Pharo (which means on top of Cog), you would need to have as they did in STX, a JIT compatible with java bytecode, an interpreter for java bytecode, runtime objects such as JavaContext, ... It is at least 1 year of work for an expert in virtual machines (I think there

Re: [Pharo-dev] VM with fragmented memory

Eliot do you think we could earn performance on Cog just by editing its settings ? I mean for example the settings: - number of PICs maximum case - JIT cache size - ... If we had something (like a job on a build server) that would try all the values in a range possible for each setting, I mean fo

Re: [Pharo-dev] [Vm-dev] Frequent SegFaults in PharoVM with Pharo 3.0

Yeah you cannot compile without inlining specific messages. You can disable inlining of #timesRepeat: at image level because we added it for fun to see if it was easy to do in Opal. Now all other optimizations were in the old compiler and are mandatories. However, you can now in Opal disable these

Re: [Pharo-dev] VM with fragmented memory

Hello, To answer your question, V8 definitely supports memory segments. I don't know about papers but in the code each segment is an instance of Heap (see heap.cc and heap.h in the source). The 2 young spaces are in another contiguous segment of 8Mb. Each segment of V8 are one of this kind (all i

Re: [Pharo-dev] is this ok?

Well this had been here for a while. I discovered it because it was triggered :). But it is very rare that this is triggered. Now when I look into the latest Pharo 3, this halt is not present. So I guess Andrei fixed it when we switched to the new debugger. 2013/11/22 Esteban Lorenzano > in th

Re: [Pharo-dev] Tuning Opal Optimizations

This mechanism does not work with Monticello. On my builds I have for this case something similar to: ./pharo $JOB_NAME.image config $REPO ConfigurationOfMyProject --install=bleedingEdge ./pharo $JOB_NAME.image eval --save 'SmalltalkImage compilerClass: OpalCompiler. Compiler recompileAll.' 2

Re: [Pharo-dev] Multithreading

to work with that I want to know all the rest that > can be useful. > > uko > > On 20 Nov 2013, at 19:21, Clément Bera wrote: > > Hello, > > What do you mean by multithreading ? > Do you mean Semaphore and Process, Cog Multithreading, the Island VM > plugin ? > >

Re: [Pharo-dev] Tuning Opal Optimizations

2013/11/20 Eliot Miranda > > On Wed, Nov 20, 2013 at 8:47 AM, Nicolas Cellier < > nicolas.cellier.aka.n...@gmail.com> wrote: > >> The only thing that annoyed me is that I failed to discover the >> incantation thru sender/implementor chain because some messages are >> constructed... >> > > that's

Re: [Pharo-dev] Multithreading

Hello, What do you mean by multithreading ? Do you mean Semaphore and Process, Cog Multithreading, the Island VM plugin ? 2013/11/20 Yuriy Tymchuk > Hi everyone, is there any chapter on multithreading in Pharo books? If not > maybe I’ll write something about that, but any material will be usef

[Pharo-dev] Fwd: Fwd: [Pharo-users] State of Flamel?

users] State of Flamel? To: Camille Teruel Cc: Pharo Development List Hi, I will see this and do and update. I'm with to much work and didn't see the email before (thanks Camille for the FW!) 2013/11/14 Camille Teruel > > > Begin forwarded message: > > *From: *Clém

[Pharo-dev] Fwd: [Pharo-users] State of Flamel?

Anyone ? -- Forwarded message -- From: Stephan Eggermont Date: 2013/11/14 Subject: Re: [Pharo-users] State of Flamel? To: pharo-us...@lists.pharo.org Anyone?

Re: [Pharo-dev] PharoV20.source

Hello, Currently the idea is to put the source file as a compressed AST in the image. The status is: - standard AST is 300Mb for the whole image, which is too much - standard AST with nodes shared between RBMethodNodes (made by Camille) is 16Mb, so already half the size of the current sources - s

Re: [Pharo-dev] help needed with fixing the SpecDebugger

e assessment case study. > > Cheers, > Doru > > > > > On Tue, Nov 12, 2013 at 9:50 AM, Clément Bera wrote: > >> Camillo we should have a look together. >> >> Are you at work today ? >> >> >> 2013/11/11 Tudor Girba >> >&

Re: [Pharo-dev] Unexpected block variable change of value

e place to insert the breakpoint was SpecLayout>>privateAsArray > not SpecRowLayout>>privateAsArray. > > regards, Ben > > > Clément Bera wrote: > > There is a bug left in double nested blocks in the debugger (some variables > then shows incorrect value). > >

Re: [Pharo-dev] Remove Class Category

Hello, I would look at: SystemOrganizer>>removeCategory: and you access it with: Smalltalk organization But I'm not sure it will help you. 2013/11/11 Jimmie Houchin > Hello, > > I am wanting to write a method which uninstalls all of the Classes which I > have created. > > I have one which l

Re: [Pharo-dev] help needed with fixing the SpecDebugger

Camillo we should have a look together. Are you at work today ? 2013/11/11 Tudor Girba > Hi, > > I need a bit of help with the issue of the SpecDebugger relying on the > default inspector being implemented in Spec. > > I investigated a bit, but now I am stuck. Details here: > https://pharo.fog

Re: [Pharo-dev] Unexpected block variable change of value

There is a bug left in double nested blocks in the debugger (some variables then shows incorrect value). Retry with the old compiler (world menu>settings>compiler>Compiler) and see if this is fixed. 2013/11/11 Max Leske > Not sure if it’s related to your issue but I’ve been seeing swapped > t

Re: [Pharo-dev] Text fixed Bug? emergency evaluator comes up in 3.0

Hello, *1) I asssume that my task is to test it? If the test would be ok, should I click on resolve in Fog Buz?* So basically when you resolved your bug, you added a slice and put the status fix review needed. Then, the monkey (which is a script) took the latest pharo image, added your slice an

Re: [Pharo-dev] Bringing external documentation internally , Deep Into Pharo , PBE

How do you want to bring it ? With class comments, method with comment only ? I guess it is not a problem as long as it does not take too much memory (I mean as long as it is not a Mb). 2013/11/5 kilon alios > Is this a problem ? I want to bring external documentation inside the > Pharo image,

Re: [Pharo-dev] Duplicate IVs | Bug or feature?

Hey, This is a feature but it had side effect problems. For instance, in the inspector you can see twice the instance variable of that name, 1 being nil and the other one having the correct value. Therefore in Pharo 3.0 with the new class builder / object layout this feature was removed. Now your

Re: [Pharo-dev] Losing instance variable addition

Basically here we discuss how to introduce in Pharo stateful class extension and stateful traits. I like these features a lot because it means I would be able to reuse the same class differently depending on the context and the surrounding classes. But if we overuse that we will definitely go into

Re: [Pharo-dev] CI

I tried. Got *Error #500* error :Empty or too short HTTP message: '' I think this is due to yesterday maintenance. It will be fixed soon. For further informations, mails from the CI guys (both sent yesterday): mail1 Dear users, A maintenance has to be performed on the network hardware of the Cl

Re: [Pharo-dev] Unwind error during termination

(Igor speaking with Clement) Another, tangent. I feel extremely wrong with given piece of code (however it works): [ ^ 2 ] ensure: [ ^ 5 ] my point, that you cannot return from same context twice, and what happens here is really weird. Or even more weird: [ ^ 2 ] ifCurtailed: [ ^ 5 ] or

Re: [Pharo-dev] Are there still halos in Pharo 3.0?

Well I use them all the time. I press shift then while shift is still pressed I select an area and all morphics inside are trapped in the halo. Very useful to delete multiple morphics at once. 2013/10/29 Nicolas Cellier > Thanks Esteban, > It works perfectly. > I would have sweared I've tried t

Re: [Pharo-dev] Unwind error during termination

OK I'll wait for another use case or until it happened to me. Like a usecase from a fresh image. It's just it may be due to the new inspector, new debugger or new compiler. Just wondering. 2013/10/24 Eliot Miranda > > > > On Thu, Oct 24, 2013 at 12:10 AM, Clément Bera

Re: [Pharo-dev] Unwind error during termination

I will try to find some time to look at this problem. Though it is not an easy one it will take some time to be fixed. 2013/10/24 > ** > Clément Bera wrote: > > Hello, > > I'm interested. > > Please send me the image in private mail not to overload the m

Re: [Pharo-dev] Fwd: Epicea

Hey Martin, Epicea looks really cool. I can't wait to have it in Pharo 3.0. Some questions however: - Can we use Epicea to recover lost changes ? I mean let's say you have an image with a lot of work inside, then it crashes before you save the image. How do you then recover lost changes with Epi

Re: [Pharo-dev] Unwind error during termination

Hello, I'm interested. Please send me the image in private mail not to overload the mailing list with large attachment. Alternatively, give me a place where I can download it. The steps to reproduce are: open the image, execute 1halt, close debugger ? Best, 2013/10/22 > ** > For a while no

Re: [Pharo-dev] Question about Opal

Hello. anAST methodNode methodClass: aClass. anAST doSemanticAnalysis. You can create the method in RBProgramNode to directly call it if you need it: RBProgramNode>>doSemanticAnalysisIn: aClass self methodNode methodClass: aClass. self doSemanticAnalysis. If you make a slice with this e

Re: [Pharo-dev] ShortRunArray not in Pharo 3.0 anymore, leading to problems with FFI-Kernel-tbn.25

I guess we can put back ShortRunArray, RunArray and the 3rd one. It was in Ballon, but there were no users in the image, so I removed them. We need to support FFI without NativeBoost I guess, or we would need to reimplement all what was done with FFI in NativeBoost. 2013/10/9 p...@highoctane.be

Re: [Pharo-dev] Please contributors fill up this form...

Is the mail display on the website a joke on purpose ? For example, I get on my screen: $@ join: #('guillermopolito' 'gmail.com') instead of: guillermopol...@gmail.com I don't know if it is nice to have that non smalltalker may read this page and my not understand. Best, 2013/10/9 Sven Van Caek

Re: [Pharo-dev] SmalltalkHub red

I'd say something related to RPackage instead of packageInfo. Esteban can give you a clue. 2013/10/9 Yuriy Tymchuk > So SmalltalkHub went red for about a week ago > https://ci.inria.fr/pharo-contribution/job/SmalltalkHub/. The issue is > related to grease stuff, because while configuration is l

Re: [Pharo-dev] [Job] One time Pharo job

I didn't get it, what company does want this consultant ? 2013/10/9 Marcus Denker > I have no other information about this: > > Job Description > - > I need a part time freelancing consultant versed in Pharo (a version of > smalltalk) for a preliminary analysis of a commerci

Re: [Pharo-dev] Pharo Sprint Lille 18th October

Who will spend its day integrating fixes ? (If not Marcus) 2013/10/8 Stéphane Ducasse > 06 30 93 66 73 in case of problem > > stef > > On Oct 8, 2013, at 5:08 PM, Marcus Denker wrote: > > > > > On Oct 8, 2013, at 4:07 PM, p...@highoctane.be wrote: > > > >> Booking the date right away. > >> > >

Re: [Pharo-dev] [update 3.0] #30456

Is it me or recently there was many more updates on Pharo than it used to be ? Last week I saw 9 to 15 updates per day instead of the usual 3. Do we have even more contributors ? 2013/10/6 Marcus Denker > 30456 > - > > 11789 Trivial Critic clean in *Completion > https://pharo.fogbug

Re: [Pharo-dev] What is WeakActionSequence?

This is a good question I was always wondering. I think it is related to event triggered in DependentFields of Object. It triggers several events. Weak because somehow there are weak event handled without weak references, probably due to the lack of ephemerons. (in some case the activation of the

Re: [Pharo-dev] About configuration of image projects

That's really cool. I guess it could be merged with the kernel bootstrap of Guille in order to create a full Pharo image from source. :) 2013/10/1 Stéphane Ducasse > Hi guys > > I started to work on creating configuration for all the projects inside > the image > > RB > Spec > Zinc > Ring > OPA

Re: [Pharo-dev] How to find a not defined class in my image?

Hello, Smalltalk at: #MyClassName => raise KeyNotFound Error if MyClassName does not exist => answers MyClassName if the class exists 2013/9/23 Sabine Knöfel > Hi, > > I am looking for a way to find out, if I have Classes referenced in my > image > which are not defined. > > I do this because

[Pharo-dev] bytecode table

Hey, Yesterday I printed the bytecode set of Pharo / Squeak (named SqueakV3PlusClosure) in a nice way to have a better overview. Perhaps some people will be interested in it. You can print it on a A3. Best, PS: Thanks Guille for the page layout, margins and stuff. ByteCode.pdf Description: Ad

Re: [Pharo-dev] About Morphic Documentation

2013/9/19 kilon > This is why I insist on collecting things on one place, inside pharo. Web > is > all over the place, its great for finding information and for getting > people > work together , but not great learning things you are not familiar with. > > Why not having the documentation the sam

Re: [Pharo-dev] Debugger 'thisContext' variable name change to 'self'

Hello, Actually I ported this inspector to Spec and I forgot to change the label. To me this is a bug. I opened bug 11576 . A slice is in inbox. I guess it will be in Pharo 3 before the end of the day. Thanks for the feedback :) Clement 2013/9/1

Re: [Pharo-dev] Compilation code in grease not compatible with Pharo 3.0

I didn't check (I'm not on my laptop) but I would say the problem is that CompiledMethodWithNode does not exist any more. Something like that would fix it: GRPharoPlatform>>compile: aString into: aClass classified: aSymbol "The trick here is to be as silently a possible so that the package is

Re: [Pharo-dev] Debugger recursion

Hello, Are you on Pharo 2 or 3 ? In Pharo 2, debugging or inspecting with ProtoObject subclasses resulted in infinite loops or image crashes. I tried to have a look with the new debugger and inspectors in Pharo 3 but there is still some work to do. 2013/8/24 jan.struz > Stéphane Ducasse wrote

Re: [Pharo-dev] doLayoutIn: killing the image

try to switch to the old debugger and retry. Smalltalk tools register: Debugger as: #debugger. might be related to the image crash. Le 15 août 2013 10:45, "Stéphane Ducasse" a écrit : > probably that show: invokes somehow doLayoutIn: > > Stef > > On Aug 15, 2013, at 10:23 AM, Stéphane Ducasse >

Re: [Pharo-dev] Uniformizing Pharo

2013/8/14 Igor Stasenko > i wonder, if we can modify the compiler, so that when it sees that > method's selector has well known name, it categorizing method > automatically under right category :) > (dunno however, what to do about existing code, when you recompiling it) > This is possible but I

Re: [Pharo-dev] [rmod] Link between Spec model and Morph ?

2013/8/13 Erwan Douaille > Hi, > > Does anyone can explain me how/where the link is ? > I guess its related to AbstractSpec subclasses, but i don't know how does > it work. > > I will be at lab the whole week. > > > 2013/8/12 Clément Bera > A spec model (Comp

Re: [Pharo-dev] Questions about spec

I've just realized there was the MultiColumnListModel. Sorry for this mail. 2013/8/13 Clément Bera > Hey guys, > > How do you detect when the user scroll in an element of a window in spec ? > I would like to use the event 'whenListScroll:' or something like that

Re: [Pharo-dev] Questions about spec

I've just realized there was the MultiColumnListModel. Sorry for this mail. 2013/8/13 Clément Bera > Hey guys, > > How do you detect when the user scroll in an element of a window in spec ? > I would like to use the event 'whenListScroll:' or something like that

[Pharo-dev] Questions about spec

Hey guys, How do you detect when the user scroll in an element of a window in spec ? I would like to use the event 'whenListScroll:' or something like that but I don't find it. How then can I set the scrolled value of another list to keep them in sync ? Lastly, is there a plan to create some kind

Re: [Pharo-dev] Updating the Pharo Contributors listing

Hello Sven, here is mine. PharoContributor new name: 'Clément Béra'; id: 'clementbera'; email: 'b era.clem...@gmail.com'; website: 'http://clementbera.wordpress.com/'; description: 'Working at Inria on Pharo compiler, runtime environment and debugging tools'; yourself 2013/8/12 Luc

Re: [Pharo-dev] [update 3.0] #30331

Wow ! That's a lot :) Pharo's improving. 2013/8/12 Stéphane Ducasse > 30331 > - > > - issue 11312 Kernel packages are extending non-kernel packages > https://pharo.fogbugz.com/default.asp?11312 > > - issue 11182 Button should have default state to false > https://pharo.fogbu

<    1   2   3   4   5   >