Re: [Pharo-users] storeOn: and literal limits
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/d5371fbf3298fcf8a0053d5c122db76b08b0b7ca/SmaCC-Development.package/SmaCCSmalltalkCodeGenerator.class/instance/splitTree..st https://github.com/ThierryGoubier/SmaCC/blob/90257788f495cc8bb3900f64115cca8272a13c06/SmaCC-Development.package/SmaCCSmalltalkCodeGenerator.class/instance/splitSpecificRewriter.st https://github.com/ThierryGoubier/SmaCC/blob/90257788f495cc8bb3900f64115cca8272a13c06/SmaCC-Development.package/SmaCCSmalltalkCodeGenerator.class/instance/splitTree.toLimit..st Thierry
[Pharo-users] storeOn: and literal limits
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. - Cheers, Sean -- View this message in context: http://forum.world.st/storeOn-and-literal-limits-tp4832255.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.
Re: [Pharo-users] HTML Parser w. custom nodes
Peter Kenny wrote allows the specification of a node factory to provide custom handling of nodes Sound like exactly what I had in mind! Although, now that I've played with it, I realize that most of the web scraping use cases that I've encountered seem like they could really benefit from a PetitParser style tool, where one could specify the output for each rule (e.g. `dataRowRule == [ code translating the node/element into a domain object ]`, and so parse the markup directly to domain objects... - Cheers, Sean -- View this message in context: http://forum.world.st/HTML-Parser-w-custom-nodes-tp4832169p4832257.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.
Re: [Pharo-users] Use array of float to GPU memory
sounds interesting, but what is the context of this? Is this built into Pharo, what version? Or what library? Those methods are not built into Pharo. They are present in the OpenCL bindings ( http://smalltalkhub.com/#!/~ronsaldo/OpenCL ), and I don't think they are very efficient in my opinion. See my answer to the original question for more information. Greetings, Ronie 2015-06-12 22:22 GMT-03:00 Ben Coman b...@openinworld.com: On Fri, Jun 12, 2015 at 10:38 PM, cheikhou cheikho...@gmail.com wrote: Finally I have found a useful method called asCLFloatArray that converts float arrays of CPU as CL float arrays of GPU. The reverse action is possible by using asFloatArrayFromCL.(from GPU to CPU memory) sounds interesting, but what is the context of this? Is this built into Pharo, what version? Or what library? cheers -ben
Re: [Pharo-users] If comments seperate from the source code and have your own comments
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 applicationAnnoApp 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) lt;http://forum.world.st/attachment/4832260/0/AnnoApp-Pharo4.0.mczgt; AnnoApp-Pharo5.0 50113.mcz (36K) lt;http://forum.world.st/attachment/4832260/1/AnnoApp-Pharo5.0%2050113.mczgt; -- View this message in context: http://forum.world.st/If-comments-seperate-from-the-source-code-and-have-your-own-comments-tp4832260p4832274.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.
Re: [Pharo-users] Mac Squeak binary virtual machine for Squeak 3.10.2
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
Re: [Pharo-users] If comments seperate from the source code and have your own comments
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 applicationAnnoApp 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
Re: [Pharo-users] If comments seperate from the source code and have your own comments
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 pdebr...@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 applicationAnnoApp 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) lt;http://forum.world.st/attachment/4832260/0/AnnoApp-Pharo4.0.mczgt; AnnoApp-Pharo5.0 50113.mcz (36K) lt;http://forum.world.st/attachment/4832260/1/AnnoApp-Pharo5.0%2050113.mczgt; -- View this message in context: http://forum.world.st/If-comments-seperate-from-the-source-code-and-have-your-own-comments-tp4832260p4832274.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.
Re: [Pharo-users] storeOn: and literal limits
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
