Hi Mariano!
Love it, great work!
Love objects StOMPing, rSTing, Fueling around between images at runtime.
Do you have examples how to realize realtime mirroring (HA) with it?
tnx in advance, Guido Stepken
Am 07.01.2012 23:25 schrieb Mariano Martinez Peck marianop...@gmail.com
:
Hi guys. Now
On 01/08/2012 02:05 AM, Gerry Weaver wrote:
Hello All,
Thank you for all of your responses. They are really helping me get a better
picture of Pharo, the environment, and the community.
I really like the idea of a REPL type interface. If I understand correctly, all
of the functionality that
Of course, but I'd check for the class equality first, because it's faster
(yeah, i know you turned off inlining of #class, but Cog doesn't care about
that ;)).
Are you sure Cog doesn't care? I think it does. From what I can see in Cog
code the entry point to inline #class is from the
All,
what's the best way (at the moment in the future) to call external
libraries from Pharo. I'm a bit confused at the moment will all the
stuff going around FFI, NativeBoost ...
Is there maybe an abstraction layer above all those native-call
mechanisms somewhere?
Best Regards,
Udo
2012/1/8 Göran Krampe go...@krampe.se:
On 01/08/2012 02:05 AM, Gerry Weaver wrote:
Hello All,
Thank you for all of your responses. They are really helping me get a
better picture of Pharo, the environment, and the community.
I really like the idea of a REPL type interface. If I understand
for each bug we assess whether it is important or not for the previous version
and if this is the case
we batch some changes for the previous version.
Now this is a lot of work and really few people help or seem concerned so we do
as much as we
can and it makes sense.
Now I guess that this is
On Jan 8, 2012, at 2:05 AM, Gerry Weaver wrote:
Hello All,
Thank you for all of your responses. They are really helping me get a better
picture of Pharo, the environment, and the community.
I really like the idea of a REPL type interface. If I understand correctly,
all of the
And you know the one we want :).
I love this Tony Hoare quote:
There are two ways of constructing a software design:
One way is to make it so simple that there are obviously no deficiencies
and the other is to make it so complicated that there are no obvious
deficiencies.
--
View this
Mariano
should not we get some fixes for FS?
Stef
On Jan 7, 2012, at 11:25 PM, Mariano Martinez Peck wrote:
Hi guys. Now you can use FileSystem streams for Fuel. Fuel only needs one
small package 'FuelFileSystem' which has just 3 extension methods, and that's
all ;)
There is also
Hi Udo
indeed this is a bit the mess :).
As soon as athens1.0 is out (planned for the end of the month). We will ask
igor to clean the system. Our idea
is to provide one API where we can plug the two infrastructures
NativeBoost (we are writing a documentation too but I should pair write
This class should be removed. By not defining any method (instance and class
side), it is useless.
Alexandre
On 7 Jan 2012, at 23:26, s...@clipperadams.com wrote:
100 classes done
796 classes remaining
Continuing in Compression...
Today: TarArchiveMember
Comment Of The Day
Hi Janko, Mariano:
On 04 Jan 2012, at 23:34, Janko Mivšek wrote:
http://www.squeaksource.com/WebCodeStats.html
I derived the following from your WebCodeStats:
ClassStats.st
Description: Binary data
I needed a bit more flexibility in terms of what to measure.
Monticello package are to
did you check
aconcagua ?
because it is the basis for Chalten (or the inverse) and support units
Stef
On Jan 8, 2012, at 6:21 AM, Ben Coman wrote:
I am implementing a model defined with quantity data having {value,
multiplier, unit} where
multiplier is m, c, k, M, etc
On Sat, Jan 7, 2012 at 2:05 PM, Henrik Sperre Johansen
henrik.s.johan...@veloxit.no wrote:
On 07.01.2012 13:20, Stéphane Ducasse wrote:
sounds like :)
Stef
On Jan 7, 2012, at 1:10 PM, Mariano Martinez Peck wrote:
FSReadStream next: count
| result |
result := ByteArray new:
As for the API:
1) There's no next: into: (which returns the amount read). It's really the
only way to do buffers without garbage allocations.
Hi Henry. One of the extensions I needed to add to FSReadStream in order to
make it work with Fuel was exatly #next:into:
The method is:
next:
On Sun, Jan 8, 2012 at 1:30 PM, Stéphane Ducasse
stephane.duca...@inria.frwrote:
Mariano
should not we get some fixes for FS?
fixes fixes fixes there is just only one, and it was the one of #next: I
reported in http://forum.world.st/Bug-in-FileSystem-td4272729.html
I can provide such fix.
Hi guys. Some time ago Henry spot to us a small improvement for WriteStream
nextPutAll: that we are using in Fuel, but I think it can be general.
Henry comment was exactly:
*Also: For variableBytes classes, if you rewrite:
WriteStream
nextPutAll: aCollection
| newEnd |
collection
On Sun, Jan 8, 2012 at 11:15 AM, Guido Stepken gstep...@googlemail.comwrote:
Hi Mariano!
Love it, great work!
Love objects StOMPing, rSTing, Fueling around between images at runtime.
Do you have examples how to realize realtime mirroring (HA) with it?
No I don't. But I guess we have the
On Jan 8, 2012, at 2:55 PM, Mariano Martinez Peck wrote:
Not exactly the same, but just to show you, in ESUG 2011 I showed how I could
serialize a living debugger from one image, open it in another one, and
continue debugging from there...having the state and everything. Then I also
Yes it makes big differences when you mix ByteString/ByteArray for example...
Or shouldn't we just let #replaceFrom:to:with:startingAt: do the job ?
That's what I did in my own image in #next:putAll:startingAt:, I
completely removed the test and it seems to work well.
I then let #nextPutAll:
Concerning my changes, I think they can be applied as they are for 1.3.
I will test that this evening
Ben
On Jan 8, 2012, at 1:23 PM, Stéphane Ducasse wrote:
for each bug we assess whether it is important or not for the previous
version and if this is the case
we batch some changes for
That is awesome.
Do you know where does Nick commit his code ?! Is it in usable state
without too much preconditions (ie. no custom VM or other weirdies)?
Not exactly the same, but just to show you, in ESUG 2011 I showed how I
could serialize a living debugger from one image, open it in
I'm also a bit lost between all the different options (plugins,
NativeBoost, FFI, Alien).
Thanks for the clarification !
Will this interface handle callbacks ?
On 08/01/12 04:37, Stéphane Ducasse wrote:
Hi Udo
indeed this is a bit the mess :).
As soon as athens1.0 is out (planned for the
On Sun, Jan 8, 2012 at 6:05 PM, Francois Stephany tulipe.mouta...@gmail.com
wrote:
That is awesome.
Do you know where does Nick commit his code ?! Is it in usable state
without too much preconditions (ie. no custom VM or other weirdies)?
Hi Francois. For Nick I say he may use Fuel as well
Yep, Esteban's setup is a bit what I have now, rST and remote tools are
what I want.
If we had a bounty system I would even pay for this. =)
On 08/01/12 09:26, Mariano Martinez Peck wrote:
On Sun, Jan 8, 2012 at 6:05 PM, Francois Stephany
tulipe.mouta...@gmail.com
On Sun, Jan 8, 2012 at 6:31 PM, Francois Stephany tulipe.mouta...@gmail.com
wrote:
Yep, Esteban's setup is a bit what I have now, rST and remote tools are
what I want.
Put it in the queue ;)
If we had a bounty system I would even pay for this. =)
On 08/01/12 09:26, Mariano Martinez
fstephany wrote
I'm also a bit lost between all the different options (plugins,
NativeBoost, FFI, Alien).
I also found this confusing, so let me tell my recent experience and my
conclusion.
I have written bindings to the SDL game programming library for use with
Pharo. SDL is
I was more curious about the process for the minor releases
than pushing to get that particular fix into 1.3. It is somewhat cosmetic.
Still thanks again.
Benjamin wrote:
Concerning my changes, I think they can be applied as they are for 1.3.
I will test that this evening
Ben
On Jan 8,
Hallo Francois,
The most stable package for distributed (or remote if you prefer)
computing is rST in http://squeaksource.org/rST/
at the moment this is your best bet.
I had provided some fixes in the past, but decided to experiment with a
smaller code base,
because *rST could not handle our
What I don't understand is why in Squeak it does work.
Because #pointsTo: is not used in Squeak (yet). As usual I dug deeper than
I should have, so I'll publish a few changes soon.
Ok, you are right. Squeak #inboundPointersExcluding: is using
#instVarsInclude: rather than #pointsTo. And
thanks for the feedback.
We will come back you soon :)
Because we should get FFI and NativeBoost fully working :).
Stef
On Jan 8, 2012, at 7:29 PM, ncalexan wrote:
fstephany wrote
I'm also a bit lost between all the different options (plugins,
NativeBoost, FFI, Alien).
I also found
Hi,
Guido Stepken wrote:
Google has unified development for handy and tablet 4.0. They have introduced
scalable, animated tiles, reacting on events, coming from analysing contents
of about 100 different protocols streaming
through the machine. Google even collects barometer and temperature
101 classes done
795 classes remaining
Continuing in Compression...
Today: ZLibReadStream
Comment Of The Day Contest - One Day One Comment
Rules:
#1: Each day a not commented class is elected. Each day the best comment will
be integrated with name of the author(s).
#2: If you cannot
Stef,
Absent the NB experience, +1 to the comments below. FFI has pretty much just
worked for me. We need double arrays. Callbacks would be great. One thing I
strongly recommend is to favor #moduleName over pragmas listing the library -
imagine changing 2000+ GSL calls if the library name
can you give an example that I understand
One thing I strongly recommend is to favor #moduleName over pragmas listing
the library - imagine changing 2000+ GSL calls if the library name changes =:0
Tx
On Jan 8, 2012, at 9:18 PM, Schwab,Wilhelm K wrote:
Stef,
Absent the NB experience, +1
On Sun, Jan 8, 2012 at 9:25 PM, Stéphane Ducasse
stephane.duca...@inria.frwrote:
can you give an example that I understand
One thing I strongly recommend is to favor #moduleName over pragmas
listing the library - imagine changing 2000+ GSL calls if the library name
changes =:0
Bill: that
Hi
Ok, I'm not pretending this isn't a stupid idea, I'm just curios.
Suppose I want to build something that would allow me to load compiled
classes (without sources) into the VM. How would you approach something
like this? What things need special care (bindings, symbols, load order, …)?
Agreed, except for thinking that changing all of the module names is not a big
deal :) An external library subclass is the way to go. I know this already
exists in FFI, but the evolving chapter on Spock does not mention it - it
should not only mention it, but recommend it, IMHO.
Stef, does
Hi Stef. I have answered what I think several times, but I will try to do
one last shoot ;)
I agree to what you say and I have some things to say and some questions:
1) For the implementation point of view, there must be an agreement between
the jenkins and the ConfigurationOf. Several things
tx!
Now I understand what you mean.
On Jan 8, 2012, at 9:52 PM, Mariano Martinez Peck wrote:
On Sun, Jan 8, 2012 at 9:25 PM, Stéphane Ducasse stephane.duca...@inria.fr
wrote:
can you give an example that I understand
One thing I strongly recommend is to favor #moduleName over pragmas
On Sun, Jan 8, 2012 at 10:03 PM, Philippe Marschall kus...@gmx.net wrote:
Hi
Ok, I'm not pretending this isn't a stupid idea, I'm just curios.
Suppose I want to build something that would allow me to load compiled
classes (without sources) into the VM. How would you approach something
like
On Sun, Jan 8, 2012 at 10:13 PM, Schwab,Wilhelm K bsch...@anest.ufl.eduwrote:
Agreed, except for thinking that changing all of the module names is not
a big deal :)
Why not? how many smalltalk lines of code do you think it could take to
automate that? ;)
An external library subclass is
Isn't there a pragma or something to mark an expected failure ?
On 08/01/12 13:20, Mariano Martinez Peck wrote:
3) What happens with tests? do we only accept 100% green tests as ok?
In Fuel for example, we like to create tests before the real code. And
moreover, we create tests to demonstrate
On Sun, Jan 8, 2012 at 10:51 PM, Francois Stephany
tulipe.mouta...@gmail.com wrote:
Isn't there a pragma or something to mark an expected failure ?
Indeed :) thanks for the reminder.
Well, forget about that item. Still the question of what happens if 80% of
the tests are green. Ok or broken?
Why do it (automated or not) 2000 times when it can be done once? Think of the
wasted time and change log bloat. Would you like to do it every time you move
from Windows to Linux and back? Say it once. The superiority of #moduleName
is clear.
From:
On Sun, Jan 8, 2012 at 11:26 PM, Schwab,Wilhelm K bsch...@anest.ufl.eduwrote:
Why do it (automated or not) 2000 times when it can be done once?
I don't understand. Why should I need to change the module name so
frequently? I have been working with squeakDBX since 4 years and we never
needed
I am just the messenger: the library names are different on the various
platforms, and the names can change over time (especially on Linux).
From: pharo-project-boun...@lists.gforge.inria.fr
[pharo-project-boun...@lists.gforge.inria.fr] on behalf of Mariano
On Sun, Jan 8, 2012 at 11:53 PM, Schwab,Wilhelm K bsch...@anest.ufl.eduwrote:
I am just the messenger: the library names are different on the various
platforms,
Yes, but that's not a problem with the solution I have just mentioned. No
need to change anything.
and the names can change over
On Sun, Jan 8, 2012 at 5:46 AM, Mariano Martinez Peck marianop...@gmail.com
wrote:
Hi guys. Some time ago Henry spot to us a small improvement for
WriteStream nextPutAll: that we are using in Fuel, but I think it can be
general. Henry comment was exactly:
*Also: For variableBytes classes,
It's not a problem at all, because the correct solution is supported - it just
needs better exposure in the Spock chapter.
\
From: pharo-project-boun...@lists.gforge.inria.fr
[pharo-project-boun...@lists.gforge.inria.fr] on behalf of Mariano Martinez
Peck
That happens anyway if you don't have the sources handy. However, the
bytecode compiler is so simple that reverse engineering of the code is
automatic. You just loose the local var names and everything is referred
to as t1, t2, t3, etc. Instance variable names are hardwired into the
Hi,
How can I get an account on Jenkins so I could set up build jobs for
CogDroid? Such way, everybody interested could easily get access to
the latest builds. Also, people who wish to experiment with derived
versions (built on top of the core VM Java+native libraries) would be
able to do it
Hi,
As CogDroid has undergone more testing on both ARM and x86 platforms,
I am pleased to announce that CogDroid is now Beta.
I have made two testing builds available:
http://www.golubovsky.org/userdirs/golubovsky/CogDroid-beta/CogDroid-debug.apk
for ARM, and
53 matches
Mail list logo
