- Pharo-dev - lists.pharo.org

Re: [Pharo-project] [NativeBoost] pass an array of args to external function

by Sven Van Caekenberghe

On 08 Nov 2012, at 20:29, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > I told you several time, do you think that a guy do not understand what is a pointer because he does not know how to write it > in C? > Give a chance to professionals to learn. We are not talking about explaining what is a pointer, but explaining the > potential problems and challenges > > With your reasoning, I should stop programming because there are so many things that I did not learn in school > and I would not have no chance to learn from this community. So with that reasoning I should better stop working in Smalltalk > and look for another language! I think he meant it as a general warning ;-) The things is, as long as its pure Smalltalk, you are protected by a very good dynamic type system that cannot really be broken, i.e. the object illusion is kept (bounds checking, blah blah â¦) But once you start using C pointers, you can very easily do something wrong. It might be a very subtle error and it might not manifest itself immediately, alas there won't be a Debugger popping up, just a coredump. Pharo is actually pretty/very stable in day to day use, it should stay that way. Sven -- Sven Van Caekenberghe http://stfx.eu Smalltalk is the Red Pill

Nov. 8, 2012

Re: [Pharo-project] [Pharo-users] Recovering Changes from a broken image

by StÃ©phane Ducasse

On Nov 8, 2012, at 9:03 PM, Sven Van Caekenberghe wrote: > Hi, > > One of the cool things of Smalltalk's images/changes file is that you can do a World Menu > Tools > Recover lost changesâ¦ to get back most [1] of your code in case your image/OS/machine suddenly crashed or you forgot to save your image or commit your Monticello packages. > > But we all have encountered the situation where the image is broken, saved in such a state that it no longer starts up properly. In that case your code might seem lost forever. > > No, it is not ! > > Two days ago I had this problem myself and I remembered something Marcus said some time ago: you can access the changes file of one (in casu your broken image) from another (working) image to select/recover the changes you want. It worked perfectly. > > The easiest procedure it to copy the .changes file from the broken image and rename its extension to .cs and then open it from a World Menu > Tools > File Browser and open a Changes browser on it. We should add a recover from another image shortcut. > > I found this very useful. This is a really important technique to be aware of. > > Sven > > [1] Sadly, not everything is logged in the changes file: creation of new classes, method deletions are not recorded. Yes we should change that. Ezequiel started to work on a new description of changes. > > -- > Sven Van Caekenberghe > http://stfx.eu > Smalltalk is the Red Pill > > > >

Nov. 8, 2012

Re: [Pharo-project] [NativeBoost] pass an array of args to external function

by StÃ©phane Ducasse

jimmie ***THANKS*** I'm in the same situation even if I read several lectures and books on C. So I want a tutorials that takes us into account and I'm sure that this is faisable. Just need care, love and time. STef On Nov 8, 2012, at 8:58 PM, Jimmie Houchin wrote: > On 11/8/2012 1:30 PM, StÃ©phane Ducasse wrote: >>> And you can be pretty sure that most pharoers (including myself) have >>> a pretty vague notion about malloc/free, combined with the internals >>> of an third party C library, that makes a pretty unstable field. >>> >>> Again, no silver bullets here, but less arrogance and more examples! >> +1 >> but we can learn and learn fast with a good tutorial that puts the right amount >> of information in perspective. >> >> Stef > I am aperson who has no background in C or similar languages, but would like to learn how to use NB to be able to access methods in DLLs. > > My question is, without becoming a C programmer, what is a sufficient level of knowledge of C to be able to use NB well? > > What is a good path to acquiring a sufficient level of knowledge? > > Thanks for any information. > > Jimmie >

Nov. 8, 2012

[Pharo-project] Recovering Changes from a broken image

by Sven Van Caekenberghe

Hi, One of the cool things of Smalltalk's images/changes file is that you can do a World Menu > Tools > Recover lost changesâ¦ to get back most [1] of your code in case your image/OS/machine suddenly crashed or you forgot to save your image or commit your Monticello packages. But we all have encountered the situation where the image is broken, saved in such a state that it no longer starts up properly. In that case your code might seem lost forever. No, it is not ! Two days ago I had this problem myself and I remembered something Marcus said some time ago: you can access the changes file of one (in casu your broken image) from another (working) image to select/recover the changes you want. It worked perfectly. The easiest procedure it to copy the .changes file from the broken image and rename its extension to .cs and then open it from a World Menu > Tools > File Browser and open a Changes browser on it. I found this very useful. This is a really important technique to be aware of. Sven [1] Sadly, not everything is logged in the changes file: creation of new classes, method deletions are not recorded. -- Sven Van Caekenberghe http://stfx.eu Smalltalk is the Red Pill

Nov. 8, 2012

Re: [Pharo-project] [NativeBoost] pass an array of args to external function

by Jimmie Houchin

On 11/8/2012 1:30 PM, StÃ©phane Ducasse wrote: >> And you can be pretty sure that most pharoers (including myself) have >> a pretty vague notion about malloc/free, combined with the internals >> of an third party C library, that makes a pretty unstable field. >> >> Again, no silver bullets here, but less arrogance and more examples! > +1 > but we can learn and learn fast with a good tutorial that puts the right amount > of information in perspective. > > Stef I am aperson who has no background in C or similar languages, but would like to learn how to use NB to be able to access methods in DLLs. My question is, without becoming a C programmer, what is a sufficient level of knowledge of C to be able to use NB well? What is a good path to acquiring a sufficient level of knowledge? Thanks for any information. Jimmie

Nov. 8, 2012

Re: [Pharo-project] What did you guys do to startup-time ?

by StÃ©phane Ducasse

Thanks Miloslav This is strange because we are not really satisfied from this point of view. There are a lot of cleaning to do to get a snappy morphic. Stef > Who snuffed the poor guy ? I donât know what magic (yea, i know, not just one magic, bunch of magix really ;-) you did but ... I downloaded Pharo 2.0 to give it a whirl (I love smalltalk and keep playing with it / write an app in it every once in a while), unzipped it, doble clicked the binary and the window jumped me so fast i nearly fell of my chair (a positive WTF moment ;-). > > And not just old Mr. Startup Time, you killed Lady Delay too. I remember squeak / older pharo versions feeling a bit sluggish (a slight delay between clicking and the menu popping up / whatever), but now it is blazing fast. > > Just saying âGreat workâ would be an understatement / denigration. > > * rausm deeply bows in silent awe

Nov. 8, 2012

Re: [Pharo-project] New command line option: load updates

by StÃ©phane Ducasse

Cool! I like the noise of the falling of large bash scripts. The lesser the better Stef > Hi, > > There is now a command line option to load updates. > > To test it: > > wget --quiet -qO - http://pharo.gforge.inria.fr/ci/ciPharo20NBCog.sh | bash > > ./vm.sh Pharo.image update > > What is does it to load updates, then snapshot and quit. > > The idea is to use this in the new CI setup so we don't need any external scripts. > > -- > Marcus Denker -- http://marcusdenker.de > >

Nov. 8, 2012

Re: [Pharo-project] [update 2.0] #20386

by Pavel Krivanek

:-) you were faster.. with the same code ;-) -- Pavel On Thu, Nov 8, 2012 at 8:29 PM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > oops! fix in inbox :) > > On Nov 8, 2012, at 8:13 PM, Pavel Krivanek <pavel.krivanek(a)gmail.com> wrote: > >> On Thu, Nov 8, 2012 at 5:59 PM, Marcus Denker <marcus.denker(a)inria.fr> wrote: >>> [update 2.0] #20386 >>> 20386 >>> ----- >>> >>> Issue 6933: Fixing the fact that typing ... >>> http://code.google.com/p/pharo/issues/detail?id=6933 >>> >>> Issue 6853: Monticello merge conflicts on reordered package names >>> http://code.google.com/p/pharo/issues/detail?id=6853 >>> >>> Issue 6760: Traits dont get repackaged >>> http://code.google.com/p/pharo/issues/detail?id=6760 >>> >> >> it seems that something is wrong with this Traits fix, when I try to >> load tests to the Pharo Kernel, I started to got this error: >> >> 10 UndefinedObject(Object)>>doesNotUnderstand: #category >> 11 Trait class>>named:uses:category:env: >> 12 Trait class>>named:uses:category: >> 13 UndefinedObject>>DoIt >> >> The full stack: >> >> Error: >> MessageNotUnderstood: receiver of "category" is nil >> 68 >> 1 [:t2 | >> | t3 | >> t3 := FileStream forceNewFileNamed: 'PharoDebug.log'. >> t3 nextPutAll: 'Error:'; >> cr. >> t3 nextPutAll: t2 asString; >> cr. >> t3 nextPutAll: thisContext stack size asString; >> cr. >> thisContext stack copy >> withIndexDo: [:t4 :t5 | [t3 nextPutAll: t5 asString; >> space; >> nextPutAll: t4 asString; >> cr] >> ifError: [:t6 | t3 nextPutAll: t6 asString; >> cr]]. >> t3 close. >> Smalltalk exitFailure] in UndefinedObject>>DoIt >> 2 BlockClosure>>cull: >> 3 BlockClosure>>cull:cull: >> 4 [:ex | errorHandlerBlock cull: ex description cull: ex receiver] in >> BlockClosure>>ifError: >> 5 BlockClosure>>cull: >> 6 [self exceptionHandlerBlock cull: exception] in >> MethodContext(ContextPart)>>handleSignal: >> 7 BlockClosure>>ensure: >> 8 MethodContext(ContextPart)>>handleSignal: >> 9 MessageNotUnderstood(Exception)>>signal >> 10 UndefinedObject(Object)>>doesNotUnderstand: #category >> 11 Trait class>>named:uses:category:env: >> 12 Trait class>>named:uses:category: >> 13 UndefinedObject>>DoIt >> 14 Compiler>>evaluate:in:to:notifying:ifFail:logged: >> 15 Compiler class>>evaluate:for:notifying:logged: >> 16 Compiler class>>evaluate:for:logged: >> 17 Compiler class>>evaluate:logged: >> 18 DoItDeclaration>>import >> 19 [:decl | value := decl import] in CodeImporter>>evaluateDeclarations >> 20 OrderedCollection>>do: >> 21 CodeImporter>>evaluateDeclarations >> 22 CodeImporter class>>evaluateReadStream: >> 23 [:t2 | >> CodeImporter evaluateReadStream: (t2 , '.st') asFileReference readStream. >> FileStream stdout nextPutAll: t2 , ' loaded'; >> lf] in ['SUnit-Core >> SUnit-Tests >> CollectionsTests >> Announcements-Tests-Core >> CompilerTests >> CompressionTests >> FileSystem-Tests-AnsiStreams >> FileSystem-Tests-Core >> FileSystem-Tests-Disk >> FileSystem-Tests-Memory >> KernelTests >> Multilingual-Tests >> Ring-Tests-Kernel >> Ring-Tests-Containers >> Tests-Bugs >> Tests-CodeImport >> Tests-Compression >> Tests-Exceptions >> Tests-Files >> Tests-Finalization >> Tests-Localization >> Tests-Object Events >> Tests-ObjectsAsMethods >> Tests-Release >> FooSharedPool >> Tests-System >> Tests-System-CommandLine >> Tests-SystemChangeNotification >> Tests-SystemTests-Support >> Tests-Traits >> Tests-Traits-MOP >> Tests-VM >> HudsonBuildTools' >> linesDo: [:t2 | >> CodeImporter evaluateReadStream: (t2 , '.st') asFileReference readStream. >> FileStream stdout nextPutAll: t2 , ' loaded'; >> lf]. >> FileStream stdout nextPutAll: 'Load tests finished'; >> lf. >> SmalltalkImage current snapshot: true andQuit: true] in UndefinedObject>>DoIt >> 24 [:start :endWithoutDelimiters :end | aBlock >> value: (self copyFrom: start to: endWithoutDelimiters)] in >> ByteString(String)>>linesDo: >> 25 ByteString(String)>>lineIndicesDo: >> 26 ByteString(String)>>linesDo: >> 27 ['SUnit-Core >> SUnit-Tests >> CollectionsTests >> Announcements-Tests-Core >> CompilerTests >> CompressionTests >> FileSystem-Tests-AnsiStreams >> FileSystem-Tests-Core >> FileSystem-Tests-Disk >> FileSystem-Tests-Memory >> KernelTests >> Multilingual-Tests >> Ring-Tests-Kernel >> Ring-Tests-Containers >> Tests-Bugs >> Tests-CodeImport >> Tests-Compression >> Tests-Exceptions >> Tests-Files >> Tests-Finalization >> Tests-Localization >> Tests-Object Events >> Tests-ObjectsAsMethods >> Tests-Release >> FooSharedPool >> Tests-System >> Tests-System-CommandLine >> Tests-SystemChangeNotification >> Tests-SystemTests-Support >> Tests-Traits >> Tests-Traits-MOP >> Tests-VM >> HudsonBuildTools' >> linesDo: [:t2 | >> CodeImporter evaluateReadStream: (t2 , '.st') asFileReference readStream. >> FileStream stdout nextPutAll: t2 , ' loaded'; >> lf]. >> FileStream stdout nextPutAll: 'Load tests finished'; >> lf. >> SmalltalkImage current snapshot: true andQuit: true] in UndefinedObject>>DoIt >> 28 BlockClosure>>on:do: >> 29 BlockClosure>>ifError: >> 30 UndefinedObject>>DoIt >> 31 Compiler>>evaluate:in:to:notifying:ifFail:logged: >> 32 Compiler class>>evaluate:for:notifying:logged: >> 33 Compiler class>>evaluate:for:logged: >> 34 Compiler class>>evaluate:logged: >> 35 DoItDeclaration>>import >> 36 [:decl | value := decl import] in CodeImporter>>evaluate >> 37 OrderedCollection>>do: >> 38 CodeImporter>>evaluate >> 39 [codeImporter evaluate] in BasicCodeLoader>>installSourceFile: >> 40 BlockClosure>>on:do: >> 41 BasicCodeLoader>>handleErrorsDuring:reference: >> 42 BasicCodeLoader>>installSourceFile: >> 43 [:reference | self installSourceFile: reference] in [sourceFiles >> do: [:reference | self installSourceFile: reference]] in >> BasicCodeLoader>>installSourceFiles >> 44 OrderedCollection>>do: >> 45 [sourceFiles >> do: [:reference | self installSourceFile: reference]] in >> BasicCodeLoader>>installSourceFiles >> 46 BlockClosure>>ensure: >> 47 BasicCodeLoader>>installSourceFiles >> 48 BasicCodeLoader>>activate >> 49 BasicCodeLoader class(CommandLineHandler class)>>activateWith: >> 50 DefaultCommandLineHandler>>handleSubcommand >> 51 DefaultCommandLineHandler>>handleArgument: >> 52 DefaultCommandLineHandler>>activate >> 53 [self new activate] in DefaultCommandLineHandler class>>startUp: >> 54 BlockClosure>>cull: >> 55 [each cull: resuming] in [:each | self >> logStartUpErrorDuring: [each cull: resuming] >> into: errors >> tryDebugger: self isInteractive] in >> SmalltalkImage>>executeDeferredStartupActions: >> 56 BlockClosure>>on:do: >> 57 SmalltalkImage>>logStartUpErrorDuring:into:tryDebugger: >> 58 [:each | self >> logStartUpErrorDuring: [each cull: resuming] >> into: errors >> tryDebugger: self isInteractive] in >> SmalltalkImage>>executeDeferredStartupActions: >> 59 OrderedCollection>>do: >> 60 SmalltalkImage>>executeDeferredStartupActions: >> 61 SmalltalkImage>>startupImage:snapshotWorked: >> 62 SmalltalkImage>>snapshot:andQuit: >> 63 [self snapshot: true andQuit: true] in >> SmalltalkImage>>privSaveImageWithCleanup >> 64 BlockClosure>>on:do: >> 65 BlockClosure>>ifError: >> 66 SmalltalkImage>>privSaveImageWithCleanup >> 67 [self privSaveImageWithCleanup] in SmalltalkImage>>saveImageInNewContext >> 68 [self value. >> Processor terminateActive] in BlockClosure>>newProcess >> > >

Nov. 8, 2012

Re: [Pharo-project] [Pharo-consortium] [Pharo-users] Pharo consortium agreement

by StÃ©phane Ducasse

On Nov 8, 2012, at 4:03 AM, Igor Stasenko wrote: > On 6 November 2012 15:36, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >> Very good that there is progress on this front ! >> >> Even better news about Igor ;-) >> > i always asking myself, if this horse worth its bets. > Thank you, Stephane & others for putting trust in me more than i do :) As a thank, write a tutorial and doc on FFI and NativeBoost with a lot of documented examples ;D > >> Indeed: thank you INRIA for sponsoring Pharo. >> >> I will read the document this evening. >> >> -- >> Sven Van Caekenberghe >> http://stfx.eu >> Smalltalk is the Red Pill >> >> >> >> On 06 Nov 2012, at 17:24, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: >> >>> Dear Pharoers >>> >>> Here is the result of the work we did around the consortium for Pharo for about 2 years. We took into account all your remarks over the years >>> and we think that the result is good and corresponds to what the community can support. >>> This consortium is important for Pharo's future and it will help us to deliver a system to help you making business. >>> Our goal is to be able to collect fundings to pay at least one full time engineer. >>> >>> The idea is that all the consortium members will sign the same agreement. We will not handle modifications per partners. >>> Now since we are starting the process if you spot some glitches on the form let us know. We can discuss and fully stabilize one version. >>> >>> We suggest to read the document. >>> - If you agree to sign it and send it to us (in two copies if you do it by surface mail at >>> INRIA - S. Ducasse - Pharo, 40, avenue Halley, Parc Scientifique de la Haute Borne, >>> BÃ¢t.A, Park Plaza, Villeneuve d'Ascq, FR-59650, France.), so that we sign it too. >>> - Don't forget to complete your legal mention on first page and your contact details on article 14 before signing. :) >>> >>> We will launch soon two web sites: >>> - one for the Pharo user association and >>> - one for the Pharo consortium. >>> >>> >>> A side note: we will communicate about it later and separately but Inria decided to support the consortium by paying one extra year to Igor Stasenko. >>> This is around 60 Keuros in addition to the year of Esteban Lorenzano and previous years of Igor. >>> >>> I really want to thank Inria for the constant support and the work of S. Karpf, P. Moreau and S. Perin. >>> >>> Stef >>> >>> <2012-11-06-consortium PHARO.pdf> >>> >>> >>> >>> >>> ------------------------ >>> Dr. StÃ©phane Ducasse -- Directeur de Recherche (Senior Researcher) >>> INRIA - USTL - CNRS UMR 8022 >>> stephane.ducasse(a)inria.fr >>> http://stephane.ducasse.free.fr >>> http://rmod.lille.inria.fr/ >>> **NEW ***Tel 00 33 (0)3 59 35 87 52 - Fax 33 3 59 57 78 50 >>> >>> 40, avenue Halley, Parc Scientifique de la Haute Borne, >>> BÃ¢t.A, Park Plaza, Villeneuve d'Ascq, FR-59650, France. >>> >>> >>> >>> >>> >>> >>> >> >> > > > > -- > Best regards, > Igor Stasenko. > > _______________________________________________ > Pharo-consortium mailing list > Pharo-consortium(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-consortium

Nov. 8, 2012

Re: [Pharo-project] PluggableListMorph error, how to debug ?

by StÃ©phane Ducasse

>> >> > Debugging UI code is one of those places you probably want to insert a haltOnce instead, or risk losing the image :) and event :) and shortcut code :)

Nov. 8, 2012