tests are red :-)
(not that much because we only took Moose-Ttests*)
1005 run, 969 passes, 0 skipped, 1 expected failures, 13 failures, 22
errors, 0 unexpected passes
Nicolas Anquetil -- RMod research team (Inria)
I moved glamour to STHub
- config updated to create a baseline for pharo1.4 pointing to STHub for as
many packages as possible (roassal, Metacello, BDD is still in SS)
- loaded the baseline in 1.4 pharo...all tests green...
- created a baseline for pharo 2.0...loaded in 2.0 and ran tests, here are
357 run, 246 passes, 0 skipped, 12 expected failures, 0 failures, 99
errors, 0 unexpected passes
- I wanted to define #stable and #development but since these are already
defined with specific version info, I didn't modify these.
Doru, can you have look for the definition of symbolic versions?
I thought that we had something like that in Moose.
Begin forwarded message:
> From: Serge Stinckwich <serge.stinckwich(a)gmail.com>
> Subject: [Pharo-project] Time Series in Smalltalk
> Date: February 20, 2013 10:28:10 PM GMT+01:00
> To: Pharo Development <pharo-project(a)lists.gforge.inria.fr>
> Reply-To: Pharo-project(a)lists.gforge.inria.fr
> Hi all,
> I'm looking for a time series library available in Smalltalk.
> Something like Python Time Series Analysis : http://pytseries.sourceforge.net/
> Pandas: http://pandas.pydata.org/
> Thank you.
> Serge Stinckwich
> UCBN & UMI UMMISCO 209 (IRD/UPMC)
> Every DSL ends up being Smalltalk
I sent this mail yesterday but strangely no received it, so here it is
With Nicolas, we have created a first baseline of Moose based on the
projects in STHub. The baseline baseline47STHub: corresponds to the old
Loading the baseline on 1.4 works fine, here are the test results:
998 run, 991 passes, 1 expected failures, 6 failures, 0 errors, 0
For each proj moved to SThub, we have tried to define two symbolic versions:
#stable: a specific version of a proj at the time of move to STHub
#bleedingEdge: load the latest packages of a proj.
Moose-Algos is moved to SThub.
Created a new baseline that loads from SThub.
Create a bleedingEdge symbolic version that loads the latest dev
Created a version in #stable for both 1.4 and pharo 2.0.
For pharo1.4-> All tests green
For pharo 2.0- > All tests green
I'm wondering if it's possible to configure the MSE importer of Moose to
import elements that satisfy some conditions (e.g., [ :element | element
In fact, I need to import only packages/namespaces and their classes from
MSE files. Why? because I want to load many many moose models (software
versions) in one image and I'm interested in few information within those
models (e.g., packages and their classes --without methods, attributes,
references, invocations, etc.).
By reading FMMSEParser and FMParseClientFilter, I found that we may set a
filter that specify the name of elements to import. Yet I'm not sure about
However, I did not find any api that we may use to set a filter that
specify the type of elements to import.
Is there a such api?
if no, is it "possible" to implement it? any suggestions?
It would be great if we can set a block filter: e.g., [ :element |
element isFamixScopingEntity and: [ element isStub not ] ]