July 2014 - Pharo-dev - lists.pharo.org

[pharo-project/pharo-core]

by GitHub

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

July 19, 2014

[pharo-project/pharo-core] 5197e7: 40101

by GitHub

Branch: refs/heads/4.0 Home: https://github.com/pharo-project/pharo-core Commit: 5197e7db16456cc7681952e72a34bcafc81d4fa7 https://github.com/pharo-project/pharo-core/commit/5197e7db16456cc7681952e7… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2014-07-19 (Sat, 19 Jul 2014) Changed paths: R Collections-Strings.package/String.class/instance/converting/asTimeStamp.st A Deprecated40.package/TimeStamp.class/README.md A Deprecated40.package/TimeStamp.class/class/instance creation/now.st A Deprecated40.package/TimeStamp.class/class/instance creation/readFrom_.st A Deprecated40.package/TimeStamp.class/definition.st A Deprecated40.package/TimeStamp.class/instance/printing/printOn_.st A Deprecated40.package/TimeStamp.class/instance/squeak protocol/asTimeStamp.st A Deprecated40.package/TimeStamp.class/instance/squeak protocol/species.st A Deprecated40.package/TimeStamp.class/instance/squeak protocol/storeOn_.st A Deprecated40.package/extension/DateAndTime/instance/asTimeStamp.st A Deprecated40.package/extension/String/instance/asTimeStamp.st R Kernel.package/DateAndTime.class/instance/converting/asTimeStamp.st R Kernel.package/TimeStamp.class/README.md R Kernel.package/TimeStamp.class/class/instance creation/now.st R Kernel.package/TimeStamp.class/class/instance creation/readFrom_.st R Kernel.package/TimeStamp.class/definition.st R Kernel.package/TimeStamp.class/instance/printing/printOn_.st R Kernel.package/TimeStamp.class/instance/squeak protocol/asTimeStamp.st R Kernel.package/TimeStamp.class/instance/squeak protocol/species.st R Kernel.package/TimeStamp.class/instance/squeak protocol/storeOn_.st R Metacello-TestsTutorial.package/MetacelloDevelopmentCycleTutorialTests.class/README.md R Metacello-TestsTutorial.package/MetacelloDevelopmentCycleTutorialTests.class/definition.st R Metacello-TestsTutorial.package/MetacelloDevelopmentCycleTutorialTests.class/instance/accessing/tempRepositories.st R Metacello-TestsTutorial.package/MetacelloDevelopmentCycleTutorialTests.class/instance/lessons/createConfiguration.st R Metacello-TestsTutorial.package/MetacelloDevelopmentCycleTutorialTests.class/instance/lessons/createDevelopment.st R Metacello-TestsTutorial.package/MetacelloDevelopmentCycleTutorialTests.class/instance/lessons/createNewBaseline.st R Metacello-TestsTutorial.package/MetacelloDevelopmentCycleTutorialTests.class/instance/lessons/createNewDevelopment.st R Metacello-TestsTutorial.package/MetacelloDevelopmentCycleTutorialTests.class/instance/lessons/releaseDevelopment.st R Metacello-TestsTutorial.package/MetacelloDevelopmentCycleTutorialTests.class/instance/lessons/validateAndSave.st R Metacello-TestsTutorial.package/MetacelloDevelopmentCycleTutorialTests.class/instance/private/alternatRepositoryName.st R Metacello-TestsTutorial.package/MetacelloDevelopmentCycleTutorialTests.class/instance/private/configurationName.st R Metacello-TestsTutorial.package/MetacelloDevelopmentCycleTutorialTests.class/instance/private/hasPackage_.st R Metacello-TestsTutorial.package/MetacelloDevelopmentCycleTutorialTests.class/instance/private/repositoryName.st R Metacello-TestsTutorial.package/MetacelloDevelopmentCycleTutorialTests.class/instance/private/version10CommonVersionSpecString.st R Metacello-TestsTutorial.package/MetacelloDevelopmentCycleTutorialTests.class/instance/private/version10DevelopmentVersionSpecString.st R Metacello-TestsTutorial.package/MetacelloDevelopmentCycleTutorialTests.class/instance/private/version10ReleaseVersionSpecString.st R Metacello-TestsTutorial.package/MetacelloDevelopmentCycleTutorialTests.class/instance/private/version11CommonVersionSpecString.st R Metacello-TestsTutorial.package/MetacelloDevelopmentCycleTutorialTests.class/instance/private/version11DevelopmentVersionSpecString.st R Metacello-TestsTutorial.package/MetacelloDevelopmentCycleTutorialTests.class/instance/private/versionCommonBaselineSpecString.st R Metacello-TestsTutorial.package/MetacelloDevelopmentCycleTutorialTests.class/instance/running/defaultTimeout.st R Metacello-TestsTutorial.package/MetacelloDevelopmentCycleTutorialTests.class/instance/running/runCase.st R Metacello-TestsTutorial.package/MetacelloDevelopmentCycleTutorialTests.class/instance/running/setUp.st R Metacello-TestsTutorial.package/MetacelloDevelopmentCycleTutorialTests.class/instance/running/tearDown.st R Metacello-TestsTutorial.package/MetacelloDevelopmentCycleTutorialTests.class/instance/running/tearDownPackages_.st R Metacello-TestsTutorial.package/MetacelloDevelopmentCycleTutorialTests.class/instance/tests/testCreateConfiguration.st R Metacello-TestsTutorial.package/MetacelloDevelopmentCycleTutorialTests.class/instance/tests/testCreateDevelopment.st R Metacello-TestsTutorial.package/MetacelloDevelopmentCycleTutorialTests.class/instance/tests/testCreateNewBaseline.st R Metacello-TestsTutorial.package/MetacelloDevelopmentCycleTutorialTests.class/instance/tests/testCreateNewDevelopment.st R Metacello-TestsTutorial.package/MetacelloDevelopmentCycleTutorialTests.class/instance/tests/testReleaseDevelopment.st R Metacello-TestsTutorial.package/MetacelloDevelopmentCycleTutorialTests.class/instance/tests/testValidateAndSave.st R Metacello-TestsTutorial.package/MetacelloTutorialTestCase.class/README.md R Metacello-TestsTutorial.package/MetacelloTutorialTestCase.class/definition.st R Metacello-TestsTutorial.package/MetacelloTutorialTestCase.class/instance/private/project.st R Metacello-TestsTutorial.package/MetacelloTutorialTestCase.class/instance/private/projectRefProject.st R Metacello-TestsTutorial.package/MetacelloTutorialTestCase.class/instance/tests-project ref/testProjectRef07.st R Metacello-TestsTutorial.package/MetacelloTutorialTestCase.class/instance/tests-project ref/testProjectRef10.st R Metacello-TestsTutorial.package/MetacelloTutorialTestCase.class/instance/tests-project ref/testProjectRef11.st R Metacello-TestsTutorial.package/MetacelloTutorialTestCase.class/instance/tests-project ref/testProjectRef12.st R Metacello-TestsTutorial.package/MetacelloTutorialTestCase.class/instance/tests-project ref/testProjectRef13.st R Metacello-TestsTutorial.package/MetacelloTutorialTestCase.class/instance/tests-project ref/testProjectRef14.st R Metacello-TestsTutorial.package/MetacelloTutorialTestCase.class/instance/tests/test01.st R Metacello-TestsTutorial.package/MetacelloTutorialTestCase.class/instance/tests/test02.st R Metacello-TestsTutorial.package/MetacelloTutorialTestCase.class/instance/tests/test03.st R Metacello-TestsTutorial.package/MetacelloTutorialTestCase.class/instance/tests/test04.st R Metacello-TestsTutorial.package/MetacelloTutorialTestCase.class/instance/tests/test05.st R Metacello-TestsTutorial.package/MetacelloTutorialTestCase.class/instance/tests/test06.st R Metacello-TestsTutorial.package/MetacelloTutorialTestCase.class/instance/tests/test07.st R Metacello-TestsTutorial.package/MetacelloTutorialTestCase.class/instance/tests/test07a.st R Metacello-TestsTutorial.package/MetacelloTutorialTestCase.class/instance/tests/test08.st R Metacello-TestsTutorial.package/MetacelloTutorialTestCase.class/instance/tests/test10a.st R Metacello-TestsTutorial.package/MetacelloTutorialTestCase.class/instance/tests/test10b.st R Metacello-TestsTutorial.package/MetacelloTutorialTestCase.class/instance/tests/test10c.st R Metacello-TestsTutorial.package/MetacelloTutorialTestCase.class/instance/tests/test10d.st R Metacello-TestsTutorial.package/MetacelloTutorialTestCase.class/instance/tests/test11.st R Metacello-TestsTutorial.package/MetacelloTutorialTestCase.class/instance/tests/test11Author.st R Metacello-TestsTutorial.package/MetacelloTutorialTestCase.class/instance/tests/test11Blessing.st R Metacello-TestsTutorial.package/MetacelloTutorialTestCase.class/instance/tests/test11Descripton.st R Metacello-TestsTutorial.package/MetacelloTutorialTestCase.class/instance/tests/test11Timestamp.st R Metacello-TestsTutorial.package/MetacelloTutorialTestCase.class/instance/tests/test12.st R Metacello-TestsTutorial.package/MetacelloTutorialTestCase.class/instance/tests/test13.st M Refactoring-Critics.package/RBBadMessageRule.class/instance/private/badSelectors.st R Refactoring-Tests-Core.package/RBBasicLintRuleTest.class/class/miscellaneous/badMessage.st R Refactoring-Tests-Core.package/RBBasicLintRuleTest.class/class/private/badSelectors.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/script101.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40101.st M ScriptLoader40.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 40101 13592 Small RB Tests cleanup https://pharo.fogbugz.com/f/cases/13592 13589 deprecated TimeStamp https://pharo.fogbugz.com/f/cases/13589 13590 TimeStamp has still instances https://pharo.fogbugz.com/f/cases/13590 13591 unload tests Metacello-TestsTutorial https://pharo.fogbugz.com/f/cases/13591 http://files.pharo.org/image/40/40101.zip

July 19, 2014

New Cog VMs available

by Eliot Miranda

... at http://www.mirandabanda.org/files/Cog/VM/VM.r3048. CogVM source as per VMMaker.oscog-eem.826/r3048 Fix the ZipPlugin (InflatePlugin&DeflatePlugin) to no longer depend on specific instance sizes for ReadStream and WriteStream which allows some leniency in redefining these classes. Fixes occasionaly Monticello commit bugs with large packages after loading Collections-eem.567. Fix compilation warnings in stringForCString: Add a -warnpid flag that causes warning to print the pid; useful in debugging multi-image tests (i.e. magma). Reimplement the backward count in interpreted methods, storing the count in IFrameFlags, hence eliminating the requirement that the jump happens consecutively N times in a single method with no backward jumps in any other method. The Chameneos benchmark has this pattern and so two methods don't get jitted. This eliminates lastBackwardJumpMethod & backwardJumpCount. Spur: Fix bad bug in remapObj: that confused the test for old vs new and hence tried to copyAndForward old objects. Fix bug in processWeaklings that could remember a weak object twice. Mark the methods used by SpurMemoryManager>>globalGarbageCollect as inline: #never for profiling. Spur Newspeak: Initialize numIRCs before checking for quick prims. -- best, Eliot

July 19, 2014

Re: [Pharo-dev] Current maintainer of PharoExtras/LDAP?

by Udo Schneider

> I did not check but I imagine you can commit now to the repo? I didn't try yet. I'm currently rolling my changes into the "official" Packages and doing some cleanup work (e.g. Tests their own package, Configuration updates). CU, Udo On 18.07.2014 13:45, stepharo wrote: > Excellent! > We loved such enhancements. > I did not check but I imagine you can commit now to the repo? > > Stef > > On 17/7/14 12:08, Udo Schneider wrote: >> > What are the changes ? >> SSL: >> * Addition of LDAPSConnection/LDAPSWorker and instance generation >> methods (e.g. LDAPSConnection>>#to:port:ssl:) to use Zodiac Sockets >> instead of regular sockets. Both classes support SSL and non-SSL >> connection. So it might be worth rolling them into the regular >> LDAPConnection/LDAPWorker >> AD: >> * Addition of LDAPSearchResultReference to handle ReferenceResults. >> W/o this even something simple like searching the RootDSE fails. >> * Addition of LDAP URLs (not working yet) to parse ReferenceResults >> * Some convenience methods to search/create/delete AD Users and >> Groups. Support for (Re)Setting Passwords ... this was quite PITA to >> figure out BTW ... >> Misc: >> * Spec based LDAP Browser (http://udos.s3.amazonaws.com/LDAPBrowser.png) >> >> Just a summary (omitting some bits and pieces like fetching RootDSEs, >> namingContexts ...) >> >> CU, >> >> Udo >> >> >> On 17.07.2014 09:30, Olivier Auverlot wrote: >>> LDAP is so important. Improving support for Active Directory and SSL >>> is really a good idea. >>> >>> I used the framework in many projects with Pharo 1.3 and 2.0. It >>> works very well. >>> >>>>> But I'm hitting a few issues now which would change the base packages. >>> >>> What are the changes ? >>> >>> Best regards >>> Olivier :-) >>> >>> Le 16 juil. 2014 Ã 19:47, stepharo a Ã©crit : >>> >>>> >>>> On 16/7/14 19:02, Udo Schneider wrote: >>>>> All, >>>>> >>>>> I'm currently making some changes to the LDAP package to make it >>>>> play nicer with ActiveDirectory and SSL. Up to now all those >>>>> changes were non-intrusive to the current packages. But I'm hitting >>>>> a few issues now which would change the base packages. >>>>> >>>>> What's the policy on this? >>>> Improving :) >>>> We need stronger and better libraries. >>>>> Keeping those changes in my own fork or submitting them to a >>>>> maintainer (who?). >>>> >>>> I gave you access to the PharoExtras repo. >>>> Just add tests and build the best LDAP you want :) >>>> Make sure that everything work well and suits your needs. >>>> I'm not sure that current design is good. At least when olivier >>>> auverlot showed to me I was skeptical about the chapter we/he wrote >>>> on it. >>>>> In addition ... as far as I can see the current package is Pharo >>>>> only (was Squeak). >>>>> If "Pharo-only" is o.k. I could for instance integrate my stuff for >>>>> LDAP-over-SSL in there directly (based on Zodiac). >>>> Excellent idea. >>>> Our goal is to make sure that people can make business. >>>>> >>>>> Thanks, >>>>> >>>>> Udo

July 18, 2014

Understanding Message Not Understood

by kilon alios

I want to find out in case of MNU what the wrong message is , its exact name ? You can also answer here http://stackoverflow.com/questions/24831610/how-to-find-which-was-the-wrong…

July 18, 2014

removing a trait from a class, breaks the saving to the package?

by stepharo

Apparently I cannot remove the trait TAbleToRotate from a class If - I copy SimpleButtonMorph - remove the use: clause from the class def - I cannot commit the package anymore. there is a problem in packageSet Esteban do you copy me :) Stef

July 18, 2014

Re: [Pharo-dev] PetitParser in 3.0?

by Martin McClure

On 07/18/2014 07:37 AM, stepharo wrote: > Hi martin > > in Moose (working on 3.0) all the tools are working so I do not know the > status of the published configuration but it should work. > Have a look at Moose and the configuration repo from there. Thanks, Stef (and Phil). I'll try loading from Moose. Regards, -Martin

July 18, 2014

Re: [Pharo-dev] Memory limit problems on Windows VM

by Oscar E. A. CallaÃº

Well, I fixed the problem by modifying the Pharo.exe file with the 4GB patch program (http://ntcore.com/4gb_patch.php) As mentioned before, I think the best solution is that Pharo vms must be compiled with the flag LARGEADDRESSAWARE, so more memory space is enabled for 64bits Windows OSs. Thanks guys Oscar On Thu, Jul 17, 2014 at 11:03 PM, Andres Valloud < avalloud(a)smalltalk.comcastbiz.net> wrote: > I worked on that switch before, and IIRC it's just a linker switch that > marks executables a certain way. So, if you have imagecfg.exe handy... > > http://support.microsoft.com/kb/297812 > > > On 7/17/14 19:25 , Oscar E. A. CallaÃº wrote: > >> Well. It seems that Pharo vms must be compiled with that option :/ >> >> Cheers >> >> >> On Wed, Jul 16, 2014 at 8:44 PM, <btc(a)openinworld.com >> <mailto:btc@openinworld.com>> wrote: >> >> __ >> Eliot Miranda wrote: >> >>> >>> >>> >>> On Wed, Jul 16, 2014 at 2:21 PM, Oscar E. A. CallaÃº >>> <oscar.apollo(a)gmail.com <mailto:oscar.apollo@gmail.com>> wrote: >>> >>> Hi, >>> >>> I'm using Windows 8.1 (update1) 64bits with 4GB of physical >>> RAM. I only need 1.5GB of RAM, so I think I don't need to >>> configure my OS to take /3GB of RAM. >>> >>> >>> Well my experience (and others) is that one can't grow the heap >>> much above 1.1 Gb without using the /3Gb switch on Windows XP. I >>> can't talk for 8.1. But if 8.x also limits memory to 2Gb/process >>> unless the /3Gb switch is in effect then yes, you'll need to use >>> the /3Gb switch. >>> >>> HTH >>> Eliot >>> >>> >>> Cheers >>> >>> On Wednesday, July 16, 2014, Eliot Miranda wrote: >>> >>> Hi Oscar, >>> >>> >>> On Wed, Jul 16, 2014 at 9:11 AM, Oscar E. A. CallaÃº >>> <oscar.apollo(a)gmail.com> wrote: >>> >>> Hi guys, >>> >>> I'm running some experiments in Pharo. My data >>> is aprox. 1.3GB. When I load my image on Mac, >>> everything works perfectly. But, when I try to load >>> the same image on Windows, I get this error: >>> >>> Unable to commit memory (1326649344 bytes requested) >>> >>> I tried the Pharo VM, cogMT and NBcog with and >>> without the option >>> >>> AddressSpaceLimit = 2048 >>> >>> in the ini file >>> >>> Please help. >>> >>> What OS are you using? Have you read e.g. >>> http://msdn.microsoft.com/en-us/library/windows/hardware/ >>> dn613959(v=vs.85).aspx >>> <http://msdn.microsoft.com/en-us/library/windows/hardware/ >>> dn613959%28v=vs.85%29.aspx>? >>> >>> >>> >> Here are some additional links... >> >> /LARGEADDRESSAWARE (Handle Large Addresses) >> http://msdn.microsoft.com/en-us/library/wz223b1z.aspx >> >> Memory Limits for Windows and Windows Server Releases >> http://msdn.microsoft.com/en-us/library/windows/desktop/ >> aa366778(v=vs.85).aspx >> I learnt something new reading this article. For Win 8.1 64-bit, the >> /3GB switch is not applicable or required. However the >> /LARGEADDRESSAWARE linker option is critical for both 32-bit and >> 64-bit VMs. Its only the default setting that changes between >> compiling 32-bit or 64-bit applications. Some extracts... >> >> Limits on memory and address space depend on whether the >> IMAGE_FILE_LARGE_ADDRESS_AWARE value of the LOADED_IMAGE structure >> and 4-gigabyte tuning (4GT) are in use. >> IMAGE_FILE_LARGE_ADDRESS_AWARE is set or cleared by using the >> /LARGEADDRESSAWARE linker option. 4-gigabyte tuning (4GT), also >> known as application memory tuning, or the /3GB switch, is a >> technology (**only applicable to 32 bit systems**) that alters the >> amount of virtual address space available to user mode applications. >> >> On x64-bit MS Windows, User-Mode virtual address space for each >> 32-bit process >> 4 GB with IMAGE_FILE_LARGE_ADDRESS_AWARE set >> 2 GB with IMAGE_FILE_LARGE_ADDRESS_AWARE cleared (default) >> >> On x64-bit MS Windows, User-Mode virtual address space for each >> 64-bit process >> 8 TB With IMAGE_FILE_LARGE_ADDRESS_AWARE set (default): >> 2 GB with IMAGE_FILE_LARGE_ADDRESS_AWARE cleared >> >> cheers -ben >> >> >>> -- >>> best, >>> Eliot >>> >>> >>> >>> >>> -- >>> best, >>> Eliot >>> >> >> >> >

July 18, 2014

Re: [Pharo-dev] PetitParser in 3.0?

by Stephan Eggermont

Esteban wrote: >Pharo has a stable version, 3. >Bug fix releases are that: bug fixes, and does not break any compatibility. That is the goal, but not currently the result. >Again, not true. We released Pharo3 with no yellow/red tests. The test runner in ci behaves different from the test runner in-image. We used to have non-deterministic tests, I haven't checked if they ar wall gone. Running the test runner in all Pharo 3 builds shows failures and errors. (Mac Mavericks 10.9.3, vm356) 30852 30851 30850 30849 30848

July 18, 2014

Re: [Pharo-dev] PetitParser in 3.0?

by stepharo

Hi martin in Moose (working on 3.0) all the tools are working so I do not know the status of the published configuration but it should work. Have a look at Moose and the configuration repo from there. Stef On 18/7/14 04:15, Martin McClure wrote: > On 07/17/2014 04:37 PM, Sean P. DeNigris wrote: >> Martin McClure-2 wrote >>> Anyone using PetitParser in Pharo 3.0? >> Yes! >> >> 1. Open the Config Browser from the World menu >> 2. Right click in the list pane and switch to the ss3 meta repo >> 3. Load the PP config >> 4. ConfigurationOfPetitParser project stableVersion load: 'Core' >> >> HTH > Thanks a bunch, Sean! > > That loads in the latest 3.0 image, and the test pass. > > I gather that the GUI tools have not been ported forward? > > Regards, > > -Martin > >

July 18, 2014