April 2010 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] FFI - structure pointer

by Andreas Raab

On 4/3/2010 6:36 AM, Schwab,Wilhelm K wrote: > Andreas, John, anybody, > > I need to find the address of a "function" (it is in fact a global structure pointer somewhere in memory) and pass it to another function. > > Suppose the structure is called Type and the function allocate_one(). I call the function something like > > allocateOne:type size:anInt > <cdecl: SomeOtherStruct* 'allocate_one' ( Type* long )> > > > but I am having an awful time getting the pointer to Type. Given that dlsym() will return a pointer to it, how can I represent that in Smalltalk? I have tried variations on > > "Indirectly call dlsym()" > address := Library default getProcAddress:'name_of_global_struct'. > > "try to create Type* from the resulting address" > type := Type fromHandle:address. > type := Type fromHandle:address getHandle. > type := ExternalData fromHandle:address type:Type externalType asPointerType. > > Something := Library default allocateOne:type size:2. > > and it either complains about bad arguments during the call or segment faults. Any ideas or similar examples? The return type of getProcAddress: is likely wrong. It should be declared to return void* which will cause it to return an ExternalData. With an ExternalData your second variant "Type fromHandle: data getHandle" will work. Cheers, - Andreas

April 3, 2010

Re: [Pharo-project] [For Testing] RC3 One-Click

by Mariano Martinez Peck

On Sat, Apr 3, 2010 at 1:42 PM, Lukas Renggli <renggli(a)gmail.com> wrote: > >> > - There is a problem in the tests of RBInternalSpellChecker in Linux > >> > and > >> > Windows, when you are not connected to internet. There are 13 errors > >> > tests. > >> > The SpellChecker uses the MacOS library, but for Linux and Windows it > >> > uses > >> > its own. But...it needs to download the file. Thus, it fails if you > are > >> > off-line. The place is in > >> > RBInternalSpellChecker >> downloadData > >> > And of course, self url is > >> > 'http://www.lukas-renggli.ch/smalltalk/rb-spelling.dat'. > >> > As now with Metacello configurations, it is easy to select if you want > >> > to > >> > download the tests or not, I would put that file somehow in the image > >> > (part > >> > of the test package). The file is 2.1 MB on disk. > >> > But maybe there is a reason not to do this. Lukas ? > >> > >> The file contains a spelling-dictionary for platforms without a spell > >> checker primitive (Windows, Linux). If the file is in there, the spell > >> check does not try to download it. So maybe it would make sense for > >> the Metacello configuration to evaluate "RBInternalSpellChecker new" > >> to force the download of the dictionary and cache it next to the > >> image? > > > > Yes, that sounds ok. And then, I deliver the PharoDev image with that > file, > > isn't it ? > > Yes, you can, if you want to make it independent of the internet. > > Ok...done in ConfigurationOfRefactoringBrowser-MarianoMartinezPeck.22 (ConfigurationOfRefactoringBrowser project version: '1.3-baseline') load > The problem is that the wordlist cannot be reasonably integrated with > the source code. It grows the image and the package code unreasonably. > > yes, understandable. > Lukas > > -- > Lukas Renggli > www.lukas-renggli.ch > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

April 3, 2010

Re: [Pharo-project] [For Testing] RC3 One-Click

by laurent laffont

> > > - In linux there are 2 failing test: > TestIdenting >> testNewLineLeaveSpacesOnOldLine > TestIdenting >> testCR2 > They are not new. I even try to ask help and Laurent too some time ago. I > would like someone to analyze them. If it is a problem of the test, I would > remove them. If there is nothing wrong with the test, I would try to analyze > how to fix it. > > These fails comes from the /FreeTypeBitBltSimulation patch ( http://lolgzs.free.fr/pharo/FreeTypeBitBltSimulation.1.cs) included in Exupery VM from pharo web site. That's why I've not included it in the VM source I've done. Laurent Laffont

April 3, 2010

[Pharo-project] CodeCritics questions

by HernÃ¡n Morales Durand

Hi, For Code Critics in OB users, if you select Refactor -> Code critics, the lint checks starts automatically.... -But it seems to start in background on all image? (the toolbar says "on Smalltalk") instead of the selected class category in the OB. It is probably a bug? -There is a percentage indicator but I don't know if refers to the currently selected lint category or all lints plus transformations... -It would be cool to start the lints on demand in a selected category? What do you think? Cheers, HernÃ¡n

April 3, 2010

[Pharo-project] Linux VM microbenchmarks

by laurent laffont

Hi, Thanks to people who send the results of tinyBenchmarks for various CPU, here's the report. What I want to know is whether these results are crap or "normal". It seems that all people succeed in compiling the VM with the source provided. So it may be a candidate for Pharo 1.0 ? The procedure to build the VM was: wget http://lolgzs.free.fr/pharo/squeak-vm/Squeak-3.11.3.2135-pharo-src.tar.gz tar -xvzf Squeak-3.11.3.2135-pharo-src.tar.gz cd Squeak-3.11.3.2135-pharo-src/ mkdir build && cd build ../unix/cmake/configure --CFLAGS="-O2" make The results: Intel(R) Core(TM)2 CPU 6600 @ 2.40GHz 64 bits =============================================== 432 M bytecodes/sec; 13 M sends/sec Intel(R) Core(TM)2 Duo CPU T8300 @ 2.40GHz 64 bits =============================================== 424 M bytecodes/sec; 13 M sends/sec Intel(R) Core(TM)2 Duo CPU T7500 @ 2.20GHz 32 bits =============================================== 389 M bytecodes/sec; 10.5 M sends/sec Intel(R) Core(TM)2 CPU T7200 @ 2.00GHz 32 bits =============================================== 330 M bytecodes/sec; 9.2 M sends/sec Intel(R) Core(TM)2 CPU 4300 @ 1.80GHz 64 bits (CFLAGS = -O3) =============================================== 331 M bytecodes/sec; 8.9 M sends/sec Intel(R) Core(TM)2 CPU 4300 @ 1.80GHz 64 bits (CFLAGS = -O2) =============================================== 106 M bytecodes/sec; 3.4 M sends/sec Intel(R) Core(TM)2 CPU 6420 @ 2.13GHz 32 bits =============================================== 220 M bytecodes/sec; 7.6 M sends/sec Intel(R) Pentium(R) 4 CPU 3.00GHz 32 bits =============================================== 93 M bytecodes/sec; 5.5 M sends/sec AMD Athlon(tm) 64 Processor 3000+ =============================================== 87 M bytecodes/sec; 4.5 M sends/sec Laurent Laffont

April 3, 2010

Re: [Pharo-project] [BetaTesting] [ANN] Pharo-1.0-10517-rc4dev10.04.1

by Stan Shepherd

hi Mariano, I get (Ubuntu 9.04) 9176 run, 9152 passes, 20 expected failures, 4 failures, 0 errors, 0 unexpected passes [1] : 'MCInitializationTest>>#testWorkingCopy' [2] : 'MCSnapshotTest>>#testInstanceReuse' [3] : 'TestIndenting>>#testCR2' [4] : 'TestIndenting>>#testNewLineLeaveSpacesOnOldLine' ...Stan -- View this message in context: http://n4.nabble.com/BetaTesting-ANN-Pharo-1-0-10517-rc4dev10-04-1-tp174923… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

April 3, 2010

Re: [Pharo-project] CollabActive book :)

by StÃ©phane Ducasse

I tried to find how to add a new user but I failed. I will ask doru ;( Stef On Apr 3, 2010, at 2:38 PM, laurent laffont wrote: > So if you want to be an editor you are more than welcome! > Just ask > > I ask :) > > Laurent Laffont. > > > > Stef > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

April 3, 2010

Re: [Pharo-project] Collection

by Tristan Bourgois

Hi, I am student who work on the project. I was afforded a thesis which has roughly the same project. They had the idea to redo the hierarchy of collections. So why not do not do it? I am not an expert but, perhaps we can simplify it? This is the thesis in spanish: http://n4.nabble.com/file/n1750153/Reingenier-a_de_Jerarqu-as_Polim-rficas_… Reingenier-a_de_Jerarqu-as_Polim-rficas_Utilizando_Traits_-_Tesis_de_Licenciatura_-_Acciaresi_Cla.pdf . (you can find the presentation of the new hierarchy at page 3) If you agree with the reimplementation of the hierarchy of collections you can propose ideas! :) Tristan Bourgois -- View this message in context: http://n4.nabble.com/Collection-tp1590427p1750153.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

April 3, 2010

Re: [Pharo-project] squeakToUTF-8 and related?

by Michael Rueger

On 4/3/2010 1:09 PM, Levente Uzonyi wrote: > This sounds really inefficient. Did you remove the primitive send from > ByteString >> #at:put:, or the following works, breaking the above > constraint? > > (ByteString basicNew: 1) at: 1 put: (Character value: 128) Apologies, it's actually 256 of course. Confused it with ASCII/Latin1 compatibility. (ByteString basicNew: 1) at: 1 put: (Character value: 256); yourself will return a WideString. Michael

April 3, 2010

[Pharo-project] FFI - structure pointer

by Schwab,Wilhelm K

Andreas, John, anybody, I need to find the address of a "function" (it is in fact a global structure pointer somewhere in memory) and pass it to another function. Suppose the structure is called Type and the function allocate_one(). I call the function something like allocateOne:type size:anInt <cdecl: SomeOtherStruct* 'allocate_one' ( Type* long ) > but I am having an awful time getting the pointer to Type. Given that dlsym() will return a pointer to it, how can I represent that in Smalltalk? I have tried variations on "Indirectly call dlsym()" address := Library default getProcAddress:'name_of_global_struct'. "try to create Type* from the resulting address" type := Type fromHandle:address. type := Type fromHandle:address getHandle. type := ExternalData fromHandle:address type:Type externalType asPointerType. Something := Library default allocateOne:type size:2. and it either complains about bad arguments during the call or segment faults. Any ideas or similar examples? Bill

April 3, 2010