January 2012 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] Now you can use Fuel with FileSystem

by StÃ©phane Ducasse

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 showed how I can save the state when an error happens (PharoDebug.fuel in addition to PharoDebug.log) into a file and debug it later on in the same or another image. In fact, Esteban Lorenzano was trying that for a real app. Instead of sending logs the client send a .fuel of the serialized context. gorgeous :) I want that :) Stef

Jan. 8, 2012

Re: [Pharo-project] Now you can use Fuel with FileSystem

by Mariano Martinez Peck

On Sun, Jan 8, 2012 at 11:15 AM, Guido Stepken <gstepken(a)googlemail.com>wrote: > 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 bases/infrastructure for that. From what I can tell you with Fuel, you can export contexts, closures, classes, traits, compiled methods, etc. So at least from the serialization point of view, that should be working. 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 showed how I can save the state when an error happens (PharoDebug.fuel in addition to PharoDebug.log) into a file and debug it later on in the same or another image. In fact, Esteban Lorenzano was trying that for a real app. Instead of sending logs the client send a .fuel of the serialized context. Dave Lewis said Fuel could be used for RemoteTask: http://wiki.squeak.org:8080/squeak/6176 Nick Papoylias (PhD just next to my desk haha) is working with rST and he may use Fuel as well for the serialization part. But not sure what he will exactly do with rST. He have several things in mind like remote debugging :) Maybe someone has done something more. That's all I know. Cheers > tnx in advance, Guido Stepken > Am 07.01.2012 23:25 schrieb "Mariano Martinez Peck" < > marianopeck(a)gmail.com>: > > 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 'FuelFileSystemTests' which let's you run all fuel tests >> using FS. If you want to do that, change FLSerializationTest >> setUp to >> send #useFileSystemFileStream rather than #useStandardFileStream and >> that's all. >> To install: >> >> Gofer new >> squeaksource: 'MetacelloRepository'; >> package: 'ConfigurationOfFuel'; >> load. >> >> (ConfigurationOfFuel project version: #bleedingEdge) load: 'withFS'. >> >> An example: >> >> | sourceArray loadedArray serializer stream materializer | >> sourceArray := >> Array >> with: 'a string' >> with: Transcript >> with: [ Transcript show: 'a string' ]. >> "Create a file and serialize on it" >> stream := (FSLocator imageDirectory / 'example.fuel') writeStream. >> serializer := FLSerializer newDefault. >> serializer serialize: sourceArray on: stream. >> stream close. >> "Load from the file" >> stream := (FSLocator imageDirectory / 'example.fuel') readStream. >> materializer := FLMaterializer newDefault. >> loadedArray := (materializer materializeFrom: stream) root. >> >> Cheers >> >> -- >> Mariano >> http://marianopeck.wordpress.com >> >> -- Mariano http://marianopeck.wordpress.com

Jan. 8, 2012

[Pharo-project] Small improvement for WriteStream >> nextPutAll:

by Mariano Martinez Peck

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 class instSpec == aCollection class instSpec ifFalse: [^ super nextPutAll: aCollection ]. newEnd := position + aCollection size. newEnd > writeLimit ifTrue: [self growTo: newEnd + 10]. collection replaceFrom: position+1 to: newEnd with: aCollectionstartingAt: 1. position := newEnd. ^ aCollection You can now pass all variableByte classes (Like ByteString) directly to a stream with a ByteArray collection, and the replaceFrom:to:with:* *startingAt: primitive will work correctly, just like the file primitive does This means you don't need special Serializers for these either, using f.ex. clunky nextStringPutAll: methods with manual asByteArray conversions.* So...if you agree, I can commit the patch. Let me know. -- Mariano http://marianopeck.wordpress.com

Jan. 8, 2012

Re: [Pharo-project] Now you can use Fuel with FileSystem

by Mariano Martinez Peck

On Sun, Jan 8, 2012 at 1:30 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>wrote: > 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. Then for Fuel I also needed #next:into: which is not implemented. I can added, but I am waiting our stream guru Henry/Nicolas approbal ;) As soon as they appear, I will submit them. 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 'FuelFileSystemTests' which let's you run all fuel tests > using FS. If you want to do that, change FLSerializationTest >> setUp to > send #useFileSystemFileStream rather than #useStandardFileStream and > that's all. > > To install: > > > > Gofer new > > squeaksource: 'MetacelloRepository'; > > package: 'ConfigurationOfFuel'; > > load. > > > > (ConfigurationOfFuel project version: #bleedingEdge) load: 'withFS'. > > > > An example: > > > > | sourceArray loadedArray serializer stream materializer | > > sourceArray := > > Array > > with: 'a string' > > with: Transcript > > with: [ Transcript show: 'a string' ]. > > "Create a file and serialize on it" > > stream := (FSLocator imageDirectory / 'example.fuel') writeStream. > > serializer := FLSerializer newDefault. > > serializer serialize: sourceArray on: stream. > > stream close. > > "Load from the file" > > stream := (FSLocator imageDirectory / 'example.fuel') readStream. > > materializer := FLMaterializer newDefault. > > loadedArray := (materializer materializeFrom: stream) root. > > > > Cheers > > > > -- > > Mariano > > http://marianopeck.wordpress.com > > > > > -- Mariano http://marianopeck.wordpress.com

Jan. 8, 2012

Re: [Pharo-project] Bug in FileSystem

by Mariano Martinez Peck

> >> 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: number into: aCollection | count | count := handle at: position read: aCollection startingAt: 1 count: number. position := position + count. ^ count < aCollection size ifTrue: [aCollection first: count] ifFalse: [aCollection] I didn't understand what you meant by "It's really the only way to do buffers without garbage allocations" So...should I integrate this method #next:into: as it is together to the fix to #read: > 2) FSHandle >>at: offset read: buffer startingAt: start count: count is a > weirdly named selector for what it does imho... > Doesn't #at: offset read: count into: buffer startingAt: start make more > sense? > > Cheers, > Henry > > -- Mariano http://marianopeck.wordpress.com

Jan. 8, 2012

Re: [Pharo-project] Bug in FileSystem

by Mariano Martinez Peck

On Sat, Jan 7, 2012 at 2:05 PM, Henrik Sperre Johansen < henrik.s.johansen(a)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: count. >>> handle at: position read: result startingAt: 1 count: count. >>> position := position + 1. >>> ^ result >>> >>> >>> shouldn't be >>> >>> FSReadStream>> next: count >>> | result | >>> result := ByteArray new: count. >>> handle at: position read: result startingAt: 1 count: count. >>> position := position + count. >>> ^ result >>> >>> At least with that (among some extensions) Fuel tests pass with FS :) >>> >>> Cheers >>> >>> -- >>> Mariano >>> http://marianopeck.wordpress.**com <http://marianopeck.wordpress.com> >>> >>> >> Still wrong though, I think... > It doesn't handle the case where you try to read past end of stream. > > next: count > ^self nextInto: (ByteArray new: count) > > would probably be better. > > Indeed. > Cheers, > Henry > > > -- Mariano http://marianopeck.wordpress.com

Jan. 8, 2012

Re: [Pharo-project] [squeak-dev] Quantities and Units

by StÃ©phane Ducasse

> 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 > unit is V, A, Hz, W, etc > > So I am looking for what quantities/units packages are around before trying to write my own. > > I have downloaded [1] and had a poke around there with the tests. Are there any further examples around of how to use it and to define new units? I notice that Voltage=Joules/Columb is not defined. > > Is anyone have any familiar with ports of packages mentioned here [2] [3] [4] from other platforms? > > cheers, Ben > > [1] http://www.squeaksource.com/Units.html > [2] http://www.cincomsmalltalk.com/publicRepository/Quantities.html > [3] http://www.smalltalking.net/goodies/Dolphin/ (scroll to bottom) > [4] http://comments.gmane.org/gmane.comp.lang.smalltalk.squeak.general/55894 > >

Jan. 8, 2012

Re: [Pharo-project] linesOfCode or another simple/understandable metric vaguely related to 'effort'

by Stefan Marr

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: I needed a bit more flexibility in terms of what to measure. Monticello package are to coarse grained, and I needed to handle extension methods separately, too. To have another number in addition to LOC, I also added the number of bytecodes. That number is less volatile to comments and white spaces. Thus, it should correlate slightly better with the 'complexity' aspect of the code. While LOC represents, as good as it can, 'maintainability'. Disclaimer: It is neither polished nor beautiful, and at least the #isOmniSelector call is specific to my stuff. But, well, might be useful start for someone out there. Best regards Stefan -- Stefan Marr Software Languages Lab Vrije Universiteit Brussel Pleinlaan 2 / B-1050 Brussels / Belgium http://soft.vub.ac.be/~smarr Phone: +32 2 629 2974 Fax: +32 2 629 3525

Jan. 8, 2012

Re: [Pharo-project] [COTDC] 101 - TarArchiveMember

by Alexandre Bergel

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, sean(a)clipperadams.com wrote: > 100 classes done > 796 classes remaining > Continuing in Compression... > > Today: TarArchiveMember > > > 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 comment it, deprecate it. > Results: http://code.google.com/p/pharo/wiki/CommentOfTheDayContest > > p.s. this message was sent from a pharo image. Did you know you could easily do that?! > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Jan. 8, 2012

Re: [Pharo-project] Best way for FFI in Pharo

by StÃ©phane Ducasse

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 with igor so it goes slowly :( With nativeBoost you can simply invoke C functions. For example the cairo binding is a good example to show how it works. The chapter is on the pharobooks inria gforge svn, I can send it to you if you want. FFI (when esteban arrives I would like to write the other chapter) and makes sure that FFI works also like a charm on all the platforms. Stef > 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 > >

Jan. 8, 2012