- Pharo-users - lists.pharo.org

Re: [Pharo-users] Copy array of float to GPU memory

by cheikhou

Hello Ronie. thanks for your response. >Sorry for the late answering. I needed to check some stuffs. no problem. >What kind of error are you getting? a NativeBoost error or incorrect results? Yes I were getting incorrect result. But when I use methods like asCLFloatArray and asFlotArrayFromCL it works. > For completeness, I just added the following new methods. Nice! I am sure that it makes OpenCL package more and more robust and enable friendly programming on GPU. >Unlike passing an IntegerArray or a FloatArray, these are method are creating a new array, looping over all >elements and doing marshalling/unmarshalling. These methods can be very inefficient. Be careful when >using them. Yes thanks a lot Ronie I will be careful to this. @Ben Cormas Look at this link http://forum.world.st/Using-VirtualGPU-td4826028.html ----- Cheikhou -- View this message in context: http://forum.world.st/Use-array-of-float-to-GPU-memory-tp4831970p4832335.ht… Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

June 14, 2015

Re: [Pharo-users] storeOn: and literal limits

by stepharo

storeOn: is old because it will not handle cycles and other. So I would simply use Ston. Stef Le 14/6/15 06:20, Sean P. DeNigris a Ã©crit : > Thierry Goubier wrote >> There is some code in SmaCC to handle that. > Would it make sense to extract? > > > > ----- > Cheers, > Sean > -- > View this message in context: http://forum.world.st/storeOn-and-literal-limits-tp4832255p4832324.html > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. > >

June 14, 2015

Re: [Pharo-users] storeOn: and literal limits

by Thierry Goubier

Le 14/06/2015 06:20, Sean P. DeNigris a Ã©crit : > Thierry Goubier wrote >> There is some code in SmaCC to handle that. > > Would it make sense to extract? I'd try if it works for you first :) Code is there: https://github.com/ThierryGoubier/SmaCC/blob/d5371fbf3298fcf8a0053d5c122db7… https://github.com/ThierryGoubier/SmaCC/blob/90257788f495cc8bb3900f64115cca… https://github.com/ThierryGoubier/SmaCC/blob/90257788f495cc8bb3900f64115cca… Thierry

June 14, 2015

Re: [Pharo-users] storeOn: and literal limits

by Sean P. DeNigris

Thierry Goubier wrote > There is some code in SmaCC to handle that. Would it make sense to extract? ----- Cheers, Sean -- View this message in context: http://forum.world.st/storeOn-and-literal-limits-tp4832255p4832324.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

June 14, 2015

Re: [Pharo-users] If comments seperate from the source code and have your own comments

by Stephan Eggermont

On 13/06/15 20:35, lb wrote: > AnnoApp is a tool for writting your own comment for > Package\Tag\Class\Method. seperating from source code file. > Your own annotation can be save out as a file use AnnoEditor. > The output file can be read back to (new) image according the name of > Package\Tag\Class\Method if the names still in the (new version) image. > AnnoEdit can mark or delete the annotations that do not exist in the Image. Well done! Nicely integrated in Nautilus, and a nice separate editor. Stephan

June 13, 2015

Re: [Pharo-users] If comments seperate from the source code and have your own comments

by lb

Thank you Paul and Stepharo. AnnoApp is a tool for writting your own comment for Package\Tag\Class\Method. seperating from source code file. Your own annotation can be save out as a file use AnnoEditor. The output file can be read back to (new) image according the name of Package\Tag\Class\Method if the names still in the (new version) image. AnnoEdit can mark or delete the annotations that do not exist in the Image. for Pharo4.0, MCHttpRepository location: 'http://smalltalkhub.com/mc/LiangBing64/AnnoApp/main' user: '' password: '' Best Regarts! Liangbing At 2015-06-14 00:31:05, "Paul DeBruicker" <pdebruic(a)gmail.com> wrote: >Hi Liang, > >I like that adding Annos don't make the package with the code I'm annotating >dirty. > >How do I move Annos from one image to another? > >The help is in Chinese, is there anything there that a person would need >that they couldn't figure out from reading hte code? I found the >AnnoEditor, which seems nice. > > >Have you put this up on smalltalkhub yet? > > >Thanks for sharing > >Paul > > > > >BingLiang wrote >> Hi, >> >> >> I know the comment is very important for reading source code and it is >> also important to write your own comment after understand somethings. >> I created a rough annotation application----AnnoApp for Nautilus, please >> give me good advice to improve it. >> Attached are the monticello files. >> Thank you in advance! >> >> >> Liang >> >> >> PS >> I love Smalltalk and I love Pharo. >> >> >> >> >> >> AnnoApp-Pharo4.0.mcz (36K) >> <http://forum.world.st/attachment/4832260/0/AnnoApp-Pharo4.0.mcz> >> AnnoApp-Pharo5.0 50113.mcz (36K) >> <http://forum.world.st/attachment/4832260/1/AnnoApp-Pharo5.0%2050113.mcz> > > > > > >-- >View this message in context: http://forum.world.st/If-comments-seperate-from-the-source-code-and-have-yo… >Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. >

June 13, 2015

Re: [Pharo-users] storeOn: and literal limits

by Thierry Goubier

Le 13/06/2015 16:06, Sean P. DeNigris a Ã©crit : > Does anything exist to handle uses of #storeOn: that bump into the literal > limit? E.g. that splits the offending constructor method into several > methods? Thanks. There is some code in SmaCC to handle that. Thierry

June 13, 2015

Re: [Pharo-users] Mac Squeak binary virtual machine for Squeak 3.10.2

by stepharo

Le 11/6/15 17:00, Stephan Eggermont a Ã©crit : > On 10/06/15 20:36, Trygve Reenskaug wrote: >> In which way is the Pharo technology that underlies Moose more complex >> than BabyIDE? Porting BabyIDE from Squeak 3.10 to 4.5 was hard because >> it extends the Squeak Parser and debugger and that this is unknown >> territory to me. There remains, of course, minor problems and bugs >> caused >> by changes in the various services offered by the Squeak kernel. > > Porting BabyIDE to Pharo is hard because: > - we now have a different compiler and debugger > - BabyIDE uses parts of Morphic that we changed and/or removed. > - Nautilus doesn't easily support changing the syntax highlighter > > As key developers of Moose are also key developers of Pharo, > a smooth transformation is something that should be expected > or at least hoped for. This is not true. But I have something else than arguing... > On the other hand, BabyIDE is much smaller than Moose. > >> you do not appear to appreciate the need that programmers (your >> customers) have for a stable programming language. > > We try to provide for both the need to have a stable environment > and the need to innovate and try new things. There is an inherent > conflict there that we try to resolve by providing a continuous > integration environment where we can get fast feedback on breaking > changes. It works pretty well for the projects that have an active > maintainer. > > Stephan Eggermont > > > >

June 13, 2015

Re: [Pharo-users] If comments seperate from the source code and have your own comments

by stepharo

Le 13/6/15 17:02, lb a Ã©crit : > Hi, > > I know the comment is very important for reading source code and it is > also important to write your own comment after understand somethings. > I created a rough annotation application----AnnoApp for Nautilus, > please give me good advice to improve it. > Attached are the monticello files. > Thank you in advance! > > Liang > > PS > I love Smalltalk and I love Pharo. Thanks > > > >

June 13, 2015

Re: [Pharo-users] If comments seperate from the source code and have your own comments

by Paul DeBruicker

Hi Liang, I like that adding Annos don't make the package with the code I'm annotating dirty. How do I move Annos from one image to another? The help is in Chinese, is there anything there that a person would need that they couldn't figure out from reading hte code? I found the AnnoEditor, which seems nice. Have you put this up on smalltalkhub yet? Thanks for sharing Paul BingLiang wrote > Hi, > > > I know the comment is very important for reading source code and it is > also important to write your own comment after understand somethings. > I created a rough annotation application----AnnoApp for Nautilus, please > give me good advice to improve it. > Attached are the monticello files. > Thank you in advance! > > > Liang > > > PS > I love Smalltalk and I love Pharo. > > > > > > AnnoApp-Pharo4.0.mcz (36K) > <http://forum.world.st/attachment/4832260/0/AnnoApp-Pharo4.0.mcz> > AnnoApp-Pharo5.0 50113.mcz (36K) > <http://forum.world.st/attachment/4832260/1/AnnoApp-Pharo5.0%2050113.mcz> -- View this message in context: http://forum.world.st/If-comments-seperate-from-the-source-code-and-have-yo… Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

June 13, 2015