November 2016 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Running on Ubuntu?

by Chris Muller

Hey Igor, I was just messing around with this the other day; Levente had the tersest incantation which worked on my fresh 14.04.4 install: sudo dpkg --add-architecture i386 sudo apt-get update sudo apt-get install libuuid1:i386 libglu1-mesa:i386 libsm6:i386 (Documented at http://wiki.squeak.org/squeak/6134) On Tue, Nov 22, 2016 at 10:46 AM, Igor Stasenko <siguctua(a)gmail.com> wrote: > > > On 22 November 2016 at 16:50, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >> >> Igor, >> >> For future reference, >> >> > On 22 Nov 2016, at 11:17, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >> > >> > (this is what I use for headless) >> > >> > sudo dpkg --add-architecture i386 >> > sudo apt-get update >> > sudo apt-get install libc6:i386 >> > sudo apt-get install libssl1.0.0:i386 >> > sudo apt-get install libfreetype6:i386 >> >> On a fresh Ubuntu 16.04.1 LTS 64-bit I did the above >> >> > (you might need more for full UI) >> >> And then just one other install >> >> sudo apt-get install libgl1-mesa-glx:i386 >> >> which installed lots of dependencies. >> >> After that I was able to run the download >> >> get.pharo.org/60+vm >> >> in UI mode (using pharo-ui). >> >> Sven >> > ohh.. wait 6.0 is on the sight.. and i was mangling with 5.0.. > yeah, that explains why it needs 32-bit libs and all that mess :) > > > -- > Best regards, > Igor Stasenko.

Nov. 24, 2016

Re: [Pharo-dev] Breaking the 4GB barrier with Pharo 6 64-bit

by Thierry Goubier

Le 23/11/2016 Ã 20:11, phil(a)highoctane.be a Ã©crit : > > > On Wed, Nov 23, 2016 at 4:16 PM, Thierry Goubier > <thierry.goubier(a)gmail.com <mailto:thierry.goubier@gmail.com>> wrote: > > > > 2016-11-23 15:46 GMT+01:00 phil(a)highoctane.be > <mailto:phil@highoctane.be> <phil(a)highoctane.be > <mailto:phil@highoctane.be>>: > > Thanks Thierry. > > Please also see that with new satellites, the resolution is ever > increasing (e.g. > Sentinel http://m.esa.int/Our_Activities/Observing_the_Earth/Copernicus/Overview4 > <http://m.esa.int/Our_Activities/Observing_the_Earth/Copernicus/Overview4>) > > > It has allways been so. Anytime you reach a reasonable size, they > send a new satellite with higher res / larger images :) > > > > I understand the tile thing and indeed a lot of the algos work > on tiles, but there are other ways to do this and especially > with real time geo queries on custom defined polygons, you go > only so far with tiles. A reason why we are using GeoTrellis > backed by Accumulo in order to pump data very fast in random order. > > > But that mean you're dealing with preprocessed / graph georeferenced > data (aka openstreetmap type of data). If you're dealing with > raster, your polygons are approximated by a set of tiles (with a > nice tile size well suited to your network / disk array). > > I had reasonable success a long time ago (1991, I think), for > Ifremer, with an unbalanced, sort of quadtree based decomposition > for highly irregular curves on the seabed. Tree node size / tile > size was computed to be exactly equal to the disk block size on a > very slow medium. That sort of work is in the line of a geographic > index for a database: optimise query accesses to geo-referenced > objects... what is hard, and probably what you are doing, is > combining geographic queries with graph queries (give me all houses > in Belgium within a ten minutes bus + walk trip to a primary school)(*) > > (*) One can work that out on a raster for speed. This is what GRASS > does for example. > > (**) I asked a student to accelerate some raster processing on a > very small FPGA a long time ago. Once he had understood he could > pipeline the design to increase the frequency, he then discovered > that the FPGA would happily grok data faster than the computer bus > could provide it :) leaving no bandwith for the data to be written > back to memory. > > > Yes, but network can be pretty fast with bonded Ethernet interfaces > these days. You mean they are not using HPC interconnects ? > We are adding 30+ servers to the cluster at the moment just to > deal with the sizes as there is a project mapping energy > landscape https://vito.be/en/land-use/land-use/energy-landscapes > <https://vito.be/en/land-use/land-use/energy-landscapes>. This > thing is throwing YARN containers and uses CPU like, > intensively. It is not uncommon for me to see their workload > eating everything for a serious amount of CPU seconds. > > > Only a few seconds ? > > > CPU-seconds, that the cluster usage unit for CPU. > http://serverfault.com/questions/138703/a-definition-for-a-cpu-second > So, says couple millions of them on a 640 core setup. CPU power is the > limiting factor in these workloads it seems. If I understand well, the cluster has enough memory to load in RAM all the data, then. > It would be silly not to plug Pharo into all of this > infrastructure I think. > > > I've had quite bad results with Pharo on compute intensive code > recently, so I'd plan carefully how I use it. On that sort of > hardware, in the projects I'm working on, 1000x faster than Pharo on > a single node is about an expected target. > > > Sure, but lower level C/C++ things are run from Python or Java, so Pharo > will not do worse. The good bit about Pharo is that one can ship a > preloaded image and that is easier than sending gigabyte (!) sized > uberjars around, that Java will unzip before running, also true with > Python myriad of dependencies. An image file appears super small then. Agreed. Pharo 64bits is interesting there because it installs a lot better than the 32bits version. And as far as I could see, at least as stable as the 32bits version for my needs. > Especially given the PhD/Postdoc/brainiacs per square meter > there. If you have seen the Lost TV show, well, it kind of feels > working there at that place. Especially given that is is kind of > hidden in the woods. > > Maybe you could have interesting interactions with them. These > guys also have their own nuclear reactor and geothermal drilling. > > > I'd be interested, because we're working a bit on high performance > parallel runtimes and compilation for those. If one day you happen > to be ready to talk about it in our place? South of Paris, not too > hard to reach by public transport :) > > Sure, that would be awesome. But Q1Y17 then because my schedule is > pretty packed at the moment. I can show you the thing over the web from > my side, so you can see where are in terms of systems. I guess you are > much more advanced but one of the goals of the project here is to be > pretty approachable and gather a community that will cross pollinate > algos and datasets for network effects. Ok. We can arrange that; I'm also quite busy until year end ;) The goal here is also to make such high performance systems more usable, but, on average, the targeted system is a bit more HPC-oriented (dedicated interconnects, nodes with GPUs or Xeon Phi). We also have some interesting work going on with microservers (highly-packed, high-efficiency servers with lower power cpus, ARM, FPGAs). Thierry

Nov. 23, 2016

Re: [Pharo-dev] IDNA / punycode for Zinc?

by phil＠highoctane.be

I am always amazed about the cool things I can learn from this list. Phil On Wed, Nov 23, 2016 at 4:59 PM, Max Leske <maxleske(a)gmail.com> wrote: > :) Nice. > > > > > On 23 Nov 2016, at 16:51, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > > > https://pharo.fogbugz.com/f/cases/19383/IDNA-punycode-for-Zinc > > > > After loading > > > > Name: Punycode-dTriangle.8 > > Author: dTriangle > > Time: 26 August 2013, 10:19:11.728 am > > UUID: 6493a3ee-43bb-44f0-86a8-5aa47a9b42ff > > Ancestors: Punycode-dTriangle.7 > > > > I can do the following > > > > 'http://Ã¼ni.ch <http://xn--ni-wka.ch>' asUrl. > > > > "http://xn--ni-wka.ch/" > > > > 'http://Ã¼ni.ch <http://xn--ni-wka.ch>' asUrl retrieveContents > includesSubstring: 'Ãni'. > > > > "true" > > > > Done ;-) > > > > Thank you, https://twitter.com/osashimitabenai, well done ! > > > > Sven > > > >> On 23 Nov 2016, at 15:43, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > >> > >> > >>> On 23 Nov 2016, at 15:36, Max Leske <maxleske(a)gmail.com> wrote: > >>> > >>> Great! > >>> > >>> Thereâs a punycode implementation on smalltalkhub ( > http://smalltalkhub.com/#!/~dTriangle/Punycode) but it needs some > polishing. > >> > >> Wow, that looks good, it even has ZnUrl integration, so we're done ;-) > >> > >> There are no tests though. > >> > >> How come we never heard of this ? > >> > >> Last commit was in 2013, hopefully the author is still around. > >> > >>> Should I open an issue on FogBugz so we donât forget? > >> > >> Yes, OK. > >> > >>> Max > >>> > >>>> On 23 Nov 2016, at 15:00, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > >>>> > >>>> Max, > >>>> > >>>>> On 23 Nov 2016, at 14:34, Max Leske <maxleske(a)gmail.com> wrote: > >>>>> > >>>>> Hi (Sven), > >>>>> > >>>>> Zinc canât currently handle unicode domain names (e.g. http://Ã¼ni.ch > <http://xn--ni-wka.ch>). Are there any plans to implement punycode / IDNA > conversion for Zinc? Or is there an explicit reason not to support it? I > see that # parseHostPort: expects the host portion to be percent escaped, > what is the use case for this? I have never seen a percent escaped host > portion. Usually the host portion is either pure ASCII, unicode or punycode > (in my experience at least). > >>>>> > >>>>> Just curious, as I just added IDNA conversion to one of our > applications (I just let python perform the conversion: > https://docs.python.org/2/library/codecs.html#module-encodings.idna) > >>>>> > >>>>> Cheers, > >>>>> Max > >>>> > >>>> Yes, that would be nice to have. > >>>> > >>>> Just for future reference, we are talking about the following > (IDN(A)): > >>>> > >>>> https://en.wikipedia.org/wiki/Internationalized_domain_name > >>>> https://en.wikipedia.org/wiki/Punycode > >>>> https://tools.ietf.org/html/rfc3490 > >>>> https://www.charset.org/punycode > >>>> > >>>> Normal DNS hostnames are ASCII only (or used to be like that anyway), > that is why it is (currently) implemented like that. > >>>> > >>>> Sven > >>>> > >>>> > >>> > >> > > > > > > >

Nov. 23, 2016

Re: [Pharo-dev] Breaking the 4GB barrier with Pharo 6 64-bit

by phil＠highoctane.be

On Wed, Nov 23, 2016 at 4:16 PM, Thierry Goubier <thierry.goubier(a)gmail.com> wrote: > > > 2016-11-23 15:46 GMT+01:00 phil(a)highoctane.be <phil(a)highoctane.be>: > >> Thanks Thierry. >> >> Please also see that with new satellites, the resolution is ever >> increasing (e.g. Sentinel http://m.esa.int/Our_ >> Activities/Observing_the_Earth/Copernicus/Overview4) >> > > It has allways been so. Anytime you reach a reasonable size, they send a > new satellite with higher res / larger images :) > > >> >> I understand the tile thing and indeed a lot of the algos work on tiles, >> but there are other ways to do this and especially with real time geo >> queries on custom defined polygons, you go only so far with tiles. A reason >> why we are using GeoTrellis backed by Accumulo in order to pump data very >> fast in random order. >> > > But that mean you're dealing with preprocessed / graph georeferenced data > (aka openstreetmap type of data). If you're dealing with raster, your > polygons are approximated by a set of tiles (with a nice tile size well > suited to your network / disk array). > > I had reasonable success a long time ago (1991, I think), for Ifremer, > with an unbalanced, sort of quadtree based decomposition for highly > irregular curves on the seabed. Tree node size / tile size was computed to > be exactly equal to the disk block size on a very slow medium. That sort of > work is in the line of a geographic index for a database: optimise query > accesses to geo-referenced objects... what is hard, and probably what you > are doing, is combining geographic queries with graph queries (give me all > houses in Belgium within a ten minutes bus + walk trip to a primary > school)(*) > > (*) One can work that out on a raster for speed. This is what GRASS does > for example. > > (**) I asked a student to accelerate some raster processing on a very > small FPGA a long time ago. Once he had understood he could pipeline the > design to increase the frequency, he then discovered that the FPGA would > happily grok data faster than the computer bus could provide it :) leaving > no bandwith for the data to be written back to memory. > Yes, but network can be pretty fast with bonded Ethernet interfaces these days. > > >> >> We are adding 30+ servers to the cluster at the moment just to deal with >> the sizes as there is a project mapping energy landscape >> https://vito.be/en/land-use/land-use/energy-landscapes. This thing is >> throwing YARN containers and uses CPU like, intensively. It is not uncommon >> for me to see their workload eating everything for a serious amount of CPU >> seconds. >> > > Only a few seconds ? > CPU-seconds, that the cluster usage unit for CPU. http://serverfault.com/questions/138703/a-definition-for-a-cpu-second So, says couple millions of them on a 640 core setup. CPU power is the limiting factor in these workloads it seems. > > >> >> It would be silly not to plug Pharo into all of this infrastructure I >> think. >> > > I've had quite bad results with Pharo on compute intensive code recently, > so I'd plan carefully how I use it. On that sort of hardware, in the > projects I'm working on, 1000x faster than Pharo on a single node is about > an expected target. > Sure, but lower level C/C++ things are run from Python or Java, so Pharo will not do worse. The good bit about Pharo is that one can ship a preloaded image and that is easier than sending gigabyte (!) sized uberjars around, that Java will unzip before running, also true with Python myriad of dependencies. An image file appears super small then. > > >> >> Especially given the PhD/Postdoc/brainiacs per square meter there. If you >> have seen the Lost TV show, well, it kind of feels working there at that >> place. Especially given that is is kind of hidden in the woods. >> >> Maybe you could have interesting interactions with them. These guys also >> have their own nuclear reactor and geothermal drilling. >> > > I'd be interested, because we're working a bit on high performance > parallel runtimes and compilation for those. If one day you happen to be > ready to talk about it in our place? South of Paris, not too hard to reach > by public transport :) > > Sure, that would be awesome. But Q1Y17 then because my schedule is pretty packed at the moment. I can show you the thing over the web from my side, so you can see where are in terms of systems. I guess you are much more advanced but one of the goals of the project here is to be pretty approachable and gather a community that will cross pollinate algos and datasets for network effects. Phil > Thierry > > > >> Phil >> >> >> >> On Wed, Nov 23, 2016 at 1:30 PM, Thierry Goubier < >> thierry.goubier(a)gmail.com> wrote: >> >>> Hi Phil, >>> >>> 2016-11-23 12:17 GMT+01:00 philippe.back(a)highoctane.be < >>> philippe.back(a)gmail.com>: >>> >>>> [ ...] >>>> >>>> It is really important to have such features to avoid massive GC pauses. >>>> >>>> My use case is to load the data sets from here. >>>> https://www.google.be/url?sa=t&source=web&rct=j&url=http://p >>>> roba-v.vgt.vito.be/sites/default/files/Product_User_Manual.p >>>> df&ved=0ahUKEwjwlOG-4L7QAhWBniwKHZVmDZcQFggpMAI&usg=AFQjCNGR >>>> ME9ZyHWQ8yCPgAQBDi1PUmzhbQ&sig2=eyaT4DlWCTjqUdQGBhFY0w >>>> >>> I've used that type of data before, a long time ago. >>> >>> I consider that tiled / on-demand block loading is the way to go for >>> those. Work with the header as long as possible, stream tiles if you need >>> to work on the full data set. There is a good chance that: >>> >>> 1- You're memory bound for anything you compute with them >>> 2- I/O times dominates, or become low enough to don't care (very fast >>> SSDs) >>> 3- It's very rare that you need full random access on the complete array >>> 4- GC doesn't matter >>> >>> Stream computing is your solution! This is how the raster GIS are >>> implemented. >>> >>> What is hard for me is manipulating a very large graph, or a sparse very >>> large structure, like a huge Famix model or a FPGA layout model with a full >>> design layed out on top. There, you're randomly accessing the whole of the >>> structure (or at least you see no obvious partition) and the structure is >>> too large for the memory or the GC. >>> >>> This is why I had a long time ago this idea of a in-memory working-set / >>> on-disk full structure with automatic determination of what the working set >>> is. >>> >>> For pointers, have a look at the Graph500 and HPCG benchmarks, >>> especially the efficiency (ratio to peak) of HPCG runs, to see how >>> difficult these cases are. >>> >>> Regards, >>> >>> Thierry >>> >> >> >

Nov. 23, 2016

[pharo-project/pharo-core]

by GitHub

Branch: refs/tags/60303 Home: https://github.com/pharo-project/pharo-core

Nov. 23, 2016

[pharo-project/pharo-core] fe6296: 60303

by GitHub

Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: fe62961ace16b96be8e62c61593e0e68924cf2d0 https://github.com/pharo-project/pharo-core/commit/fe62961ace16b96be8e62c61… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2016-11-23 (Wed, 23 Nov 2016) Changed paths: M Alien.package/AlienWeakTable.class/instance/adding/add_finalizing_.st M ConfigurationOfFuel.package/ConfigurationOfFuel.class/class/accessing/project.st R ConfigurationOfFuel.package/ConfigurationOfFuel.class/class/development support/DevelopmentSupport.st R ConfigurationOfFuel.package/ConfigurationOfFuel.class/class/metacello tool support/isMetacelloConfig.st R ConfigurationOfFuel.package/ConfigurationOfFuel.class/class/private/addHacks.st A ConfigurationOfFuel.package/ConfigurationOfFuel.class/class/private/bootstrapMetacelloFrom_.st A ConfigurationOfFuel.package/ConfigurationOfFuel.class/class/private/bootstrapPackage_from_.st A ConfigurationOfFuel.package/ConfigurationOfFuel.class/class/private/ensureGoferVersion_repositoryUrl_.st A ConfigurationOfFuel.package/ConfigurationOfFuel.class/class/private/ensureMetacello_.st A ConfigurationOfFuel.package/ConfigurationOfFuel.class/class/private/retry_.st A ConfigurationOfFuel.package/ConfigurationOfFuel.class/class/private/retry_retryCount_.st A ConfigurationOfFuel.package/ConfigurationOfFuel.class/class/unloading Metacello/unloadMetacello.st A ConfigurationOfFuel.package/ConfigurationOfFuel.class/instance/accessing/customProjectAttributes.st M ConfigurationOfFuel.package/ConfigurationOfFuel.class/instance/accessing/project.st A ConfigurationOfFuel.package/ConfigurationOfFuel.class/instance/accessing/projectClass.st A ConfigurationOfFuel.package/ConfigurationOfFuel.class/instance/accessing/project_.st M ConfigurationOfFuel.package/ConfigurationOfFuel.class/instance/baselines-1/baseline192_.st M ConfigurationOfFuel.package/ConfigurationOfFuel.class/instance/baselines-1/baseline193_.st M ConfigurationOfFuel.package/ConfigurationOfFuel.class/instance/baselines-1/baseline194_.st M ConfigurationOfFuel.package/ConfigurationOfFuel.class/instance/baselines-2/baseline200_.st M ConfigurationOfFuel.package/ConfigurationOfFuel.class/instance/baselines-2/baseline210_.st A ConfigurationOfFuel.package/ConfigurationOfFuel.class/instance/baselines-2/baseline218_.st A ConfigurationOfFuel.package/ConfigurationOfFuel.class/instance/baselines-helpers/fuelPlatform_.st M ConfigurationOfFuel.package/ConfigurationOfFuel.class/instance/symbolic versions/development_.st M ConfigurationOfFuel.package/ConfigurationOfFuel.class/instance/symbolic versions/stable_.st A ConfigurationOfFuel.package/ConfigurationOfFuel.class/instance/versions-2/version218_.st A ConfigurationOfFuelPlatform.package/ConfigurationOfFuelPlatform.class/README.md A ConfigurationOfFuelPlatform.package/ConfigurationOfFuelPlatform.class/class/accessing/project.st A ConfigurationOfFuelPlatform.package/ConfigurationOfFuelPlatform.class/class/development support/validate.st A ConfigurationOfFuelPlatform.package/ConfigurationOfFuelPlatform.class/class/loading/loadAll.st A ConfigurationOfFuelPlatform.package/ConfigurationOfFuelPlatform.class/class/private/baseConfigurationClassIfAbsent_.st A ConfigurationOfFuelPlatform.package/ConfigurationOfFuelPlatform.class/class/private/bootstrapMetacelloFrom_.st A ConfigurationOfFuelPlatform.package/ConfigurationOfFuelPlatform.class/class/private/bootstrapPackage_from_.st A ConfigurationOfFuelPlatform.package/ConfigurationOfFuelPlatform.class/class/private/ensureGoferVersion_repositoryUrl_.st A ConfigurationOfFuelPlatform.package/ConfigurationOfFuelPlatform.class/class/private/ensureMetacello.st A ConfigurationOfFuelPlatform.package/ConfigurationOfFuelPlatform.class/class/private/ensureMetacelloBaseConfiguration.st A ConfigurationOfFuelPlatform.package/ConfigurationOfFuelPlatform.class/class/private/ensureMetacello_.st A ConfigurationOfFuelPlatform.package/ConfigurationOfFuelPlatform.class/class/private/retry_.st A ConfigurationOfFuelPlatform.package/ConfigurationOfFuelPlatform.class/class/private/retry_retryCount_.st A ConfigurationOfFuelPlatform.package/ConfigurationOfFuelPlatform.class/class/unloading Metacello/unloadMetacello.st A ConfigurationOfFuelPlatform.package/ConfigurationOfFuelPlatform.class/definition.st A ConfigurationOfFuelPlatform.package/ConfigurationOfFuelPlatform.class/instance/accessing/addCustomProjectAttribute_.st A ConfigurationOfFuelPlatform.package/ConfigurationOfFuelPlatform.class/instance/accessing/customProjectAttributes.st A ConfigurationOfFuelPlatform.package/ConfigurationOfFuelPlatform.class/instance/accessing/loadAll.st A ConfigurationOfFuelPlatform.package/ConfigurationOfFuelPlatform.class/instance/accessing/project.st A ConfigurationOfFuelPlatform.package/ConfigurationOfFuelPlatform.class/instance/accessing/projectClass.st A ConfigurationOfFuelPlatform.package/ConfigurationOfFuelPlatform.class/instance/accessing/project_.st A ConfigurationOfFuelPlatform.package/ConfigurationOfFuelPlatform.class/instance/baselines/baseline_.st A ConfigurationOfFuelPlatform.package/ConfigurationOfFuelPlatform.class/instance/helpers/fuelRepository_.st A ConfigurationOfFuelPlatform.package/ConfigurationOfFuelPlatform.class/instance/helpers/pharoPackagesAndGroups_.st A ConfigurationOfFuelPlatform.package/ConfigurationOfFuelPlatform.class/instance/helpers/squeakPackagesAndGroups_.st A ConfigurationOfFuelPlatform.package/ConfigurationOfFuelPlatform.class/instance/private/addPostloadHacks.st A ConfigurationOfFuelPlatform.package/ConfigurationOfFuelPlatform.class/instance/private/platformAttributes.st A ConfigurationOfFuelPlatform.package/ConfigurationOfFuelPlatform.class/instance/symbolic versions/default_.st A ConfigurationOfUnifiedFFI.package/ConfigurationOfUnifiedFFI.class/instance/versions/v0%5F24%5F3_.st M FFI-Kernel.package/ExternalObject.class/class/class initialization/initialize.st A FuelPlatform-Core.package/FLExtensionWrapper.class/README.md A FuelPlatform-Core.package/FLExtensionWrapper.class/class/instance-creation/fromPragma_.st A FuelPlatform-Core.package/FLExtensionWrapper.class/definition.st A FuelPlatform-Core.package/FLExtensionWrapper.class/instance/accessing/isSource.st A FuelPlatform-Core.package/FLExtensionWrapper.class/instance/accessing/isSource_.st A FuelPlatform-Core.package/FLExtensionWrapper.class/instance/accessing/method.st A FuelPlatform-Core.package/FLExtensionWrapper.class/instance/accessing/method_.st A FuelPlatform-Core.package/FLExtensionWrapper.class/instance/accessing/selector_.st A FuelPlatform-Core.package/FLExtensionWrapper.class/instance/accessing/targetClass.st A FuelPlatform-Core.package/FLExtensionWrapper.class/instance/accessing/targetClass_.st A FuelPlatform-Core.package/FLExtensionWrapper.class/instance/initialize-release/initializeWithPragma_.st A FuelPlatform-Core.package/FLExtensionWrapper.class/instance/initialize-release/readArgumentsFrom_.st A FuelPlatform-Core.package/FLExtensionWrapper.class/instance/initialize-release/readIsSourceFrom_argumentNames_argumentValues_.st A FuelPlatform-Core.package/FLExtensionWrapper.class/instance/initialize-release/readSelectorFrom_argumentNames_argumentValues_.st A FuelPlatform-Core.package/FLExtensionWrapper.class/instance/initialize-release/readTargetClassFrom_argumentNames_argumentValues_.st A FuelPlatform-Core.package/FLExtensionWrapper.class/instance/initialize-release/selector.st A FuelPlatform-Core.package/FLExtensionWrapper.class/instance/operations/install.st A FuelPlatform-Core.package/FLExtensionWrapper.class/instance/private/compileInTarget.st A FuelPlatform-Core.package/FLExtensionWrapper.class/instance/private/copySelector_ofMethod_toClass_.st A FuelPlatform-Core.package/FLExtensionWrapper.class/instance/private/copyToTarget.st A FuelPlatform-Core.package/FLExtensionWrapper.class/instance/private/extensionProtocolName.st A FuelPlatform-Core.package/FLExtensionWrapper.class/instance/private/renameAndCompileInTarget.st A FuelPlatform-Core.package/FLPlatform.class/README.md A FuelPlatform-Core.package/FLPlatform.class/class/accessing/current.st A FuelPlatform-Core.package/FLPlatform.class/class/accessing/extensionCategoryName.st A FuelPlatform-Core.package/FLPlatform.class/class/accessing/extensionProtocolName.st A FuelPlatform-Core.package/FLPlatform.class/class/accessing/hacksCategoryName.st A FuelPlatform-Core.package/FLPlatform.class/class/class initialization/initialize.st A FuelPlatform-Core.package/FLPlatform.class/class/operations/addHacks.st A FuelPlatform-Core.package/FLPlatform.class/class/operations/checkForUpdates.st A FuelPlatform-Core.package/FLPlatform.class/class/private-convenience/removeModifications.st A FuelPlatform-Core.package/FLPlatform.class/class/private-convenience/reset.st A FuelPlatform-Core.package/FLPlatform.class/class/private-extensions/addExtensions.st A FuelPlatform-Core.package/FLPlatform.class/class/private-extensions/extensionPragmas.st A FuelPlatform-Core.package/FLPlatform.class/class/private-hacks-metacello/fixMetacello.st A FuelPlatform-Core.package/FLPlatform.class/class/private-hacks/basicAddHacks.st A FuelPlatform-Core.package/FLPlatform.class/class/private/detectPlatform.st A FuelPlatform-Core.package/FLPlatform.class/class/private/getConfigurationVersion.st A FuelPlatform-Core.package/FLPlatform.class/class/private/updateConfigurationVersion.st A FuelPlatform-Core.package/FLPlatform.class/class/testing/isResponsibleForCurrentPlatform.st A FuelPlatform-Core.package/FLPlatform.class/definition.st A FuelPlatform-Core.package/FLPlatform.class/instance/accessing-compiler/renamedMethodCopyOf_selector_.st A FuelPlatform-Core.package/FLPlatform.class/instance/accessing-files/deleteFileNamed_.st A FuelPlatform-Core.package/FLPlatform.class/instance/accessing-files/fileNamed_readStreamDo_.st A FuelPlatform-Core.package/FLPlatform.class/instance/accessing-files/fileNamed_writeStreamDo_.st A FuelPlatform-Core.package/FLPlatform.class/instance/accessing-system/absolutePathOf_.st A FuelPlatform-Core.package/FLPlatform.class/instance/accessing-system/imageName.st A FuelPlatform-Core.package/FLPlatform.class/instance/accessing-system/useAuthor_during_.st A FuelPlatform-Core.package/FLPlatform.class/instance/accessing/versionNumber.st A FuelPlatform-Core.package/FLPlatform.class/instance/operations/addHacks.st A FuelPlatform-Core.package/FLPlatform.class/instance/testing/isBigEndian.st A FuelPlatform-Core.package/FLPlatform.class/instance/testing/isPharo.st A FuelPlatform-Core.package/FLPlatform.class/instance/testing/isSpur.st A FuelPlatform-Core.package/FLPlatform.class/instance/testing/isSqueak.st A FuelPlatform-Pharo-06.package/FLPharo6Platform.class/README.md A FuelPlatform-Pharo-06.package/FLPharo6Platform.class/class/private-hacks/addHacks.st A FuelPlatform-Pharo-06.package/FLPharo6Platform.class/class/testing/isResponsibleForCurrentPlatform.st A FuelPlatform-Pharo-06.package/FLPharo6Platform.class/definition.st A FuelPlatform-Pharo-06.package/FLPharo6Platform.class/instance/accessing-files/deleteFileNamed_.st A FuelPlatform-Pharo-06.package/FLPharo6Platform.class/instance/accessing-files/fileNamed_readStreamDo_.st A FuelPlatform-Pharo-06.package/FLPharo6Platform.class/instance/accessing-files/fileNamed_writeStreamDo_.st A FuelPlatform-Pharo-06.package/FLPharo6Platform.class/instance/testing/isBigEndian.st A FuelPlatform-Pharo-Core.package/FLPharoPlatform.class/README.md A FuelPlatform-Pharo-Core.package/FLPharoPlatform.class/class/private-hacks/basicAddHacks.st A FuelPlatform-Pharo-Core.package/FLPharoPlatform.class/class/testing/addNativeBoostComponents.st A FuelPlatform-Pharo-Core.package/FLPharoPlatform.class/class/testing/addPackageManifest.st A FuelPlatform-Pharo-Core.package/FLPharoPlatform.class/class/testing/isResponsibleForCurrentPlatform.st A FuelPlatform-Pharo-Core.package/FLPharoPlatform.class/definition.st A FuelPlatform-Pharo-Core.package/FLPharoPlatform.class/instance/accessing-compiler/renamedMethodCopyOf_selector_.st A FuelPlatform-Pharo-Core.package/FLPharoPlatform.class/instance/accessing-system/absolutePathOf_.st A FuelPlatform-Pharo-Core.package/FLPharoPlatform.class/instance/accessing-system/imageName.st A FuelPlatform-Pharo-Core.package/FLPharoPlatform.class/instance/accessing-system/useAuthor_during_.st A FuelPlatform-Pharo-Core.package/FLPharoPlatform.class/instance/testing/isPharo.st A FuelPlatform-Pharo-Core.package/FLPharoPlatform.class/instance/testing/isSpur.st R FuelPlatform.package/FLExtensionWrapper.class/README.md R FuelPlatform.package/FLExtensionWrapper.class/class/instance-creation/fromPragma_.st R FuelPlatform.package/FLExtensionWrapper.class/definition.st R FuelPlatform.package/FLExtensionWrapper.class/instance/accessing/isSource.st R FuelPlatform.package/FLExtensionWrapper.class/instance/accessing/isSource_.st R FuelPlatform.package/FLExtensionWrapper.class/instance/accessing/method.st R FuelPlatform.package/FLExtensionWrapper.class/instance/accessing/method_.st R FuelPlatform.package/FLExtensionWrapper.class/instance/accessing/selector_.st R FuelPlatform.package/FLExtensionWrapper.class/instance/accessing/targetClass.st R FuelPlatform.package/FLExtensionWrapper.class/instance/accessing/targetClass_.st R FuelPlatform.package/FLExtensionWrapper.class/instance/initialize-release/initializeWithPragma_.st R FuelPlatform.package/FLExtensionWrapper.class/instance/initialize-release/readArgumentsFrom_.st R FuelPlatform.package/FLExtensionWrapper.class/instance/initialize-release/readIsSourceFrom_argumentNames_argumentValues_.st R FuelPlatform.package/FLExtensionWrapper.class/instance/initialize-release/readSelectorFrom_argumentNames_argumentValues_.st R FuelPlatform.package/FLExtensionWrapper.class/instance/initialize-release/readTargetClassFrom_argumentNames_argumentValues_.st R FuelPlatform.package/FLExtensionWrapper.class/instance/initialize-release/selector.st R FuelPlatform.package/FLExtensionWrapper.class/instance/operations/install.st R FuelPlatform.package/FLExtensionWrapper.class/instance/private/compileInTarget.st R FuelPlatform.package/FLExtensionWrapper.class/instance/private/copySelector_ofMethod_toClass_.st R FuelPlatform.package/FLExtensionWrapper.class/instance/private/copyToTarget.st R FuelPlatform.package/FLExtensionWrapper.class/instance/private/extensionProtocolName.st R FuelPlatform.package/FLExtensionWrapper.class/instance/private/renameAndCompileInTarget.st R FuelPlatform.package/FLPharo6Platform.class/README.md R FuelPlatform.package/FLPharo6Platform.class/class/private-hacks/addHacks.st R FuelPlatform.package/FLPharo6Platform.class/class/testing/isResponsibleForCurrentPlatform.st R FuelPlatform.package/FLPharo6Platform.class/definition.st R FuelPlatform.package/FLPharo6Platform.class/instance/accessing-files/deleteFileNamed_.st R FuelPlatform.package/FLPharo6Platform.class/instance/accessing-files/fileNamed_readStreamDo_.st R FuelPlatform.package/FLPharo6Platform.class/instance/accessing-files/fileNamed_writeStreamDo_.st R FuelPlatform.package/FLPharo6Platform.class/instance/testing/isBigEndian.st R FuelPlatform.package/FLPharoPlatform.class/README.md R FuelPlatform.package/FLPharoPlatform.class/class/private-hacks/basicAddHacks.st R FuelPlatform.package/FLPharoPlatform.class/class/testing/addNativeBoostComponents.st R FuelPlatform.package/FLPharoPlatform.class/class/testing/addPackageManifest.st R FuelPlatform.package/FLPharoPlatform.class/class/testing/isResponsibleForCurrentPlatform.st R FuelPlatform.package/FLPharoPlatform.class/definition.st R FuelPlatform.package/FLPharoPlatform.class/instance/accessing-compiler/renamedMethodCopyOf_selector_.st R FuelPlatform.package/FLPharoPlatform.class/instance/accessing-system/absolutePathOf_.st R FuelPlatform.package/FLPharoPlatform.class/instance/accessing-system/imageName.st R FuelPlatform.package/FLPharoPlatform.class/instance/accessing-system/useAuthor_during_.st R FuelPlatform.package/FLPharoPlatform.class/instance/testing/isPharo.st R FuelPlatform.package/FLPharoPlatform.class/instance/testing/isSpur.st R FuelPlatform.package/FLPlatform.class/README.md R FuelPlatform.package/FLPlatform.class/class/accessing/current.st R FuelPlatform.package/FLPlatform.class/class/accessing/extensionCategoryName.st R FuelPlatform.package/FLPlatform.class/class/accessing/extensionProtocolName.st R FuelPlatform.package/FLPlatform.class/class/accessing/hacksCategoryName.st R FuelPlatform.package/FLPlatform.class/class/class initialization/initialize.st R FuelPlatform.package/FLPlatform.class/class/operations/addHacks.st R FuelPlatform.package/FLPlatform.class/class/operations/checkForUpdates.st R FuelPlatform.package/FLPlatform.class/class/private-convenience/removeModifications.st R FuelPlatform.package/FLPlatform.class/class/private-convenience/reset.st R FuelPlatform.package/FLPlatform.class/class/private-extensions/addExtensions.st R FuelPlatform.package/FLPlatform.class/class/private-extensions/extensionPragmas.st R FuelPlatform.package/FLPlatform.class/class/private-hacks-metacello/fixMetacello.st R FuelPlatform.package/FLPlatform.class/class/private-hacks/basicAddHacks.st R FuelPlatform.package/FLPlatform.class/class/private/detectPlatform.st R FuelPlatform.package/FLPlatform.class/class/private/getConfigurationVersion.st R FuelPlatform.package/FLPlatform.class/class/private/updateConfigurationVersion.st R FuelPlatform.package/FLPlatform.class/class/testing/isResponsibleForCurrentPlatform.st R FuelPlatform.package/FLPlatform.class/definition.st R FuelPlatform.package/FLPlatform.class/instance/accessing-compiler/renamedMethodCopyOf_selector_.st R FuelPlatform.package/FLPlatform.class/instance/accessing-files/deleteFileNamed_.st R FuelPlatform.package/FLPlatform.class/instance/accessing-files/fileNamed_readStreamDo_.st R FuelPlatform.package/FLPlatform.class/instance/accessing-files/fileNamed_writeStreamDo_.st R FuelPlatform.package/FLPlatform.class/instance/accessing-system/absolutePathOf_.st R FuelPlatform.package/FLPlatform.class/instance/accessing-system/imageName.st R FuelPlatform.package/FLPlatform.class/instance/accessing-system/useAuthor_during_.st R FuelPlatform.package/FLPlatform.class/instance/accessing/versionNumber.st R FuelPlatform.package/FLPlatform.class/instance/operations/addHacks.st R FuelPlatform.package/FLPlatform.class/instance/testing/isBigEndian.st R FuelPlatform.package/FLPlatform.class/instance/testing/isPharo.st R FuelPlatform.package/FLPlatform.class/instance/testing/isSpur.st R FuelPlatform.package/FLPlatform.class/instance/testing/isSqueak.st M FuelTests.package/FLContextSerializationTest.class/instance/tests/testDoIt.st M Keymapping-KeyCombinations.package/KMSingleKeyCombination.class/instance/printing/printOn_.st M Keymapping-Tests.package/KMShortcutTest.class/instance/tests/testAsString.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60302.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60303.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60302.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60303.st M ScriptLoader60.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st M UnifiedFFI.package/FFIExternalStructure.class/class/accessing/structureAlignment.st R UnifiedFFI.package/extension/ByteArray/instance/readStringUTF8.st R UnifiedFFI.package/extension/ExternalData/instance/readStringUTF8.st Log Message: ----------- 60303 18330 Fuel still has platform classes in Pharo6 like FLPharo11Platform. https://pharo.fogbugz.com/f/cases/18330 19381 KMSingleKeyCombination should be not printed with forced uppercases https://pharo.fogbugz.com/f/cases/19381 19382 #add:finalizing: in AlienWeakTable sends unexistent message #copyGrownBy https://pharo.fogbugz.com/f/cases/19382 http://files.pharo.org/image/60/60303.zip

Nov. 23, 2016

Re: [Pharo-dev] IDNA / punycode for Zinc?

by Max Leske

:) Nice. > On 23 Nov 2016, at 16:51, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > https://pharo.fogbugz.com/f/cases/19383/IDNA-punycode-for-Zinc > > After loading > > Name: Punycode-dTriangle.8 > Author: dTriangle > Time: 26 August 2013, 10:19:11.728 am > UUID: 6493a3ee-43bb-44f0-86a8-5aa47a9b42ff > Ancestors: Punycode-dTriangle.7 > > I can do the following > > 'http://Ã¼ni.ch' asUrl. > > "http://xn--ni-wka.ch/" > > 'http://Ã¼ni.ch' asUrl retrieveContents includesSubstring: 'Ãni'. > > "true" > > Done ;-) > > Thank you, https://twitter.com/osashimitabenai, well done ! > > Sven > >> On 23 Nov 2016, at 15:43, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >> >> >>> On 23 Nov 2016, at 15:36, Max Leske <maxleske(a)gmail.com> wrote: >>> >>> Great! >>> >>> Thereâs a punycode implementation on smalltalkhub (http://smalltalkhub.com/#!/~dTriangle/Punycode) but it needs some polishing. >> >> Wow, that looks good, it even has ZnUrl integration, so we're done ;-) >> >> There are no tests though. >> >> How come we never heard of this ? >> >> Last commit was in 2013, hopefully the author is still around. >> >>> Should I open an issue on FogBugz so we donât forget? >> >> Yes, OK. >> >>> Max >>> >>>> On 23 Nov 2016, at 15:00, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >>>> >>>> Max, >>>> >>>>> On 23 Nov 2016, at 14:34, Max Leske <maxleske(a)gmail.com> wrote: >>>>> >>>>> Hi (Sven), >>>>> >>>>> Zinc canât currently handle unicode domain names (e.g. http://Ã¼ni.ch) Are there any plans to implement punycode / IDNA conversion for Zinc? Or is there an explicit reason not to support it? I see that #parseHostPort: expects the host portion to be percent escaped, what is the use case for this? I have never seen a percent escaped host portion. Usually the host portion is either pure ASCII, unicode or punycode (in my experience at least). >>>>> >>>>> Just curious, as I just added IDNA conversion to one of our applications (I just let python perform the conversion: https://docs.python.org/2/library/codecs.html#module-encodings.idna) >>>>> >>>>> Cheers, >>>>> Max >>>> >>>> Yes, that would be nice to have. >>>> >>>> Just for future reference, we are talking about the following (IDN(A)): >>>> >>>> https://en.wikipedia.org/wiki/Internationalized_domain_name >>>> https://en.wikipedia.org/wiki/Punycode >>>> https://tools.ietf.org/html/rfc3490 >>>> https://www.charset.org/punycode >>>> >>>> Normal DNS hostnames are ASCII only (or used to be like that anyway), that is why it is (currently) implemented like that. >>>> >>>> Sven >>>> >>>> >>> >> > >

Nov. 23, 2016

Re: [Pharo-dev] IDNA / punycode for Zinc?

by Sven Van Caekenberghe

https://pharo.fogbugz.com/f/cases/19383/IDNA-punycode-for-Zinc After loading Name: Punycode-dTriangle.8 Author: dTriangle Time: 26 August 2013, 10:19:11.728 am UUID: 6493a3ee-43bb-44f0-86a8-5aa47a9b42ff Ancestors: Punycode-dTriangle.7 I can do the following 'http://Ã¼ni.ch' asUrl. "http://xn--ni-wka.ch/" 'http://Ã¼ni.ch' asUrl retrieveContents includesSubstring: 'Ãni'. "true" Done ;-) Thank you, https://twitter.com/osashimitabenai, well done ! Sven > On 23 Nov 2016, at 15:43, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > >> On 23 Nov 2016, at 15:36, Max Leske <maxleske(a)gmail.com> wrote: >> >> Great! >> >> Thereâs a punycode implementation on smalltalkhub (http://smalltalkhub.com/#!/~dTriangle/Punycode) but it needs some polishing. > > Wow, that looks good, it even has ZnUrl integration, so we're done ;-) > > There are no tests though. > > How come we never heard of this ? > > Last commit was in 2013, hopefully the author is still around. > >> Should I open an issue on FogBugz so we donât forget? > > Yes, OK. > >> Max >> >>> On 23 Nov 2016, at 15:00, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >>> >>> Max, >>> >>>> On 23 Nov 2016, at 14:34, Max Leske <maxleske(a)gmail.com> wrote: >>>> >>>> Hi (Sven), >>>> >>>> Zinc canât currently handle unicode domain names (e.g. http://Ã¼ni.ch) Are there any plans to implement punycode / IDNA conversion for Zinc? Or is there an explicit reason not to support it? I see that #parseHostPort: expects the host portion to be percent escaped, what is the use case for this? I have never seen a percent escaped host portion. Usually the host portion is either pure ASCII, unicode or punycode (in my experience at least). >>>> >>>> Just curious, as I just added IDNA conversion to one of our applications (I just let python perform the conversion: https://docs.python.org/2/library/codecs.html#module-encodings.idna) >>>> >>>> Cheers, >>>> Max >>> >>> Yes, that would be nice to have. >>> >>> Just for future reference, we are talking about the following (IDN(A)): >>> >>> https://en.wikipedia.org/wiki/Internationalized_domain_name >>> https://en.wikipedia.org/wiki/Punycode >>> https://tools.ietf.org/html/rfc3490 >>> https://www.charset.org/punycode >>> >>> Normal DNS hostnames are ASCII only (or used to be like that anyway), that is why it is (currently) implemented like that. >>> >>> Sven >>> >>> >> >

Nov. 23, 2016

Re: [Pharo-dev] Breaking the 4GB barrier with Pharo 6 64-bit

by Thierry Goubier

2016-11-23 15:46 GMT+01:00 phil(a)highoctane.be <phil(a)highoctane.be>: > Thanks Thierry. > > Please also see that with new satellites, the resolution is ever > increasing (e.g. Sentinel http://m.esa.int/Our_Activities/Observing_the_ > Earth/Copernicus/Overview4) > It has allways been so. Anytime you reach a reasonable size, they send a new satellite with higher res / larger images :) > > I understand the tile thing and indeed a lot of the algos work on tiles, > but there are other ways to do this and especially with real time geo > queries on custom defined polygons, you go only so far with tiles. A reason > why we are using GeoTrellis backed by Accumulo in order to pump data very > fast in random order. > But that mean you're dealing with preprocessed / graph georeferenced data (aka openstreetmap type of data). If you're dealing with raster, your polygons are approximated by a set of tiles (with a nice tile size well suited to your network / disk array). I had reasonable success a long time ago (1991, I think), for Ifremer, with an unbalanced, sort of quadtree based decomposition for highly irregular curves on the seabed. Tree node size / tile size was computed to be exactly equal to the disk block size on a very slow medium. That sort of work is in the line of a geographic index for a database: optimise query accesses to geo-referenced objects... what is hard, and probably what you are doing, is combining geographic queries with graph queries (give me all houses in Belgium within a ten minutes bus + walk trip to a primary school)(*) (*) One can work that out on a raster for speed. This is what GRASS does for example. (**) I asked a student to accelerate some raster processing on a very small FPGA a long time ago. Once he had understood he could pipeline the design to increase the frequency, he then discovered that the FPGA would happily grok data faster than the computer bus could provide it :) leaving no bandwith for the data to be written back to memory. > > We are adding 30+ servers to the cluster at the moment just to deal with > the sizes as there is a project mapping energy landscape > https://vito.be/en/land-use/land-use/energy-landscapes. This thing is > throwing YARN containers and uses CPU like, intensively. It is not uncommon > for me to see their workload eating everything for a serious amount of CPU > seconds. > Only a few seconds ? > > It would be silly not to plug Pharo into all of this infrastructure I > think. > I've had quite bad results with Pharo on compute intensive code recently, so I'd plan carefully how I use it. On that sort of hardware, in the projects I'm working on, 1000x faster than Pharo on a single node is about an expected target. > > Especially given the PhD/Postdoc/brainiacs per square meter there. If you > have seen the Lost TV show, well, it kind of feels working there at that > place. Especially given that is is kind of hidden in the woods. > > Maybe you could have interesting interactions with them. These guys also > have their own nuclear reactor and geothermal drilling. > I'd be interested, because we're working a bit on high performance parallel runtimes and compilation for those. If one day you happen to be ready to talk about it in our place? South of Paris, not too hard to reach by public transport :) Thierry > Phil > > > > On Wed, Nov 23, 2016 at 1:30 PM, Thierry Goubier < > thierry.goubier(a)gmail.com> wrote: > >> Hi Phil, >> >> 2016-11-23 12:17 GMT+01:00 philippe.back(a)highoctane.be < >> philippe.back(a)gmail.com>: >> >>> [ ...] >>> >>> It is really important to have such features to avoid massive GC pauses. >>> >>> My use case is to load the data sets from here. >>> https://www.google.be/url?sa=t&source=web&rct=j&url=http://p >>> roba-v.vgt.vito.be/sites/default/files/Product_User_Manual.p >>> df&ved=0ahUKEwjwlOG-4L7QAhWBniwKHZVmDZcQFggpMAI&usg=AFQjCNGR >>> ME9ZyHWQ8yCPgAQBDi1PUmzhbQ&sig2=eyaT4DlWCTjqUdQGBhFY0w >>> >> I've used that type of data before, a long time ago. >> >> I consider that tiled / on-demand block loading is the way to go for >> those. Work with the header as long as possible, stream tiles if you need >> to work on the full data set. There is a good chance that: >> >> 1- You're memory bound for anything you compute with them >> 2- I/O times dominates, or become low enough to don't care (very fast >> SSDs) >> 3- It's very rare that you need full random access on the complete array >> 4- GC doesn't matter >> >> Stream computing is your solution! This is how the raster GIS are >> implemented. >> >> What is hard for me is manipulating a very large graph, or a sparse very >> large structure, like a huge Famix model or a FPGA layout model with a full >> design layed out on top. There, you're randomly accessing the whole of the >> structure (or at least you see no obvious partition) and the structure is >> too large for the memory or the GC. >> >> This is why I had a long time ago this idea of a in-memory working-set / >> on-disk full structure with automatic determination of what the working set >> is. >> >> For pointers, have a look at the Graph500 and HPCG benchmarks, especially >> the efficiency (ratio to peak) of HPCG runs, to see how difficult these >> cases are. >> >> Regards, >> >> Thierry >> > >

Nov. 23, 2016

Re: [Pharo-dev] About ~= and ~~

by ClÃ©ment Bera

Hi Do you mean you want to add this pragma "<primitive: 169>" in Object >> #~~ ? Or do you mean replacing #blockCopy: by #~~ in the special selectors to get it inlined by default like #== ? On Wed, Nov 23, 2016 at 2:39 PM, Aliaksei Syrel <alex.syrel(a)gmail.com> wrote: > Hi > > It is been a while... > So, do we want to replace ~~ with a primitive? :) > > Cheers > Alex > > > > -- > View this message in context: http://forum.world.st/About- > and-tp3898409p4924391.html > Sent from the Pharo Smalltalk Developers mailing list archive at > Nabble.com. > >

Nov. 23, 2016