- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Some methods missing in Behavior

by Marcus Denker

This is is fixed in Pharo4... is this important enough for a back port? If yes, please submit a slice... On Sat, Oct 11, 2014 at 10:22 AM, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > On 10 Oct 2014, at 15:25, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > > On 10 Oct 2014, at 14:36, jdelgado(a)lsi.upc.edu wrote: > > Yes, evaluate: > > (Behavior new) compile: 'thisIsATest ^2' > > ah, that indeed should workâ¦ I will check and fix it in Pharo3 and Pharo4 > > > For Pharo4: > > https://pharo.fogbugz.com/f/cases/14215/Fix-for-Behavior-new-compile > -- -- Marcus Denker -- denker(a)acm.org http://www.marcusdenker.de

Oct. 16, 2014

[pharo-project/pharo-core]

by GitHub

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

Oct. 16, 2014

[pharo-project/pharo-core] 59c34d: 40308

by GitHub

Branch: refs/heads/4.0 Home: https://github.com/pharo-project/pharo-core Commit: 59c34db35428e6688d27a182ab1bc4195fb13d53 https://github.com/pharo-project/pharo-core/commit/59c34db35428e6688d27a182… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2014-10-16 (Thu, 16 Oct 2014) Changed paths: M OpalCompiler-Core.package/AbstractCompiler.class/class/settings/compilerSettingsOn_.st M OpalCompiler-Core.package/CCompilationContext.class/class/initialize/initialize.st M OpalCompiler-Core.package/CCompilationContext.class/instance/accessing/bytecodeGeneratorClass.st M OpalCompiler-Core.package/CompilationContext.class/class/initialize/initialize.st M OpalCompiler-Core.package/CompilationContext.class/instance/accessing/bytecodeGeneratorClass.st A OpalCompiler-Core.package/IRAbstractBytecodeGenerator.class/instance/results/addProperties_.st A OpalCompiler-Core.package/IRAbstractSqueakV3PlusClosuresBytecodeGenerator.class/README.md A OpalCompiler-Core.package/IRAbstractSqueakV3PlusClosuresBytecodeGenerator.class/class/initialize/bytecodeTableFrom_.st A OpalCompiler-Core.package/IRAbstractSqueakV3PlusClosuresBytecodeGenerator.class/class/initialize/initializeBytecodeTable.st A OpalCompiler-Core.package/IRAbstractSqueakV3PlusClosuresBytecodeGenerator.class/class/initialize/initializeSpecialConstants.st A OpalCompiler-Core.package/IRAbstractSqueakV3PlusClosuresBytecodeGenerator.class/class/initialize/specialConstants.st A OpalCompiler-Core.package/IRAbstractSqueakV3PlusClosuresBytecodeGenerator.class/definition.st A OpalCompiler-Core.package/IRAbstractSqueakV3PlusClosuresBytecodeGenerator.class/instance/instructions/blockReturnTop.st A OpalCompiler-Core.package/IRAbstractSqueakV3PlusClosuresBytecodeGenerator.class/instance/instructions/popTop.st A OpalCompiler-Core.package/IRAbstractSqueakV3PlusClosuresBytecodeGenerator.class/instance/instructions/pushConsArray_.st A OpalCompiler-Core.package/IRAbstractSqueakV3PlusClosuresBytecodeGenerator.class/instance/instructions/pushDup.st A OpalCompiler-Core.package/IRAbstractSqueakV3PlusClosuresBytecodeGenerator.class/instance/instructions/pushInstVar_.st A OpalCompiler-Core.package/IRAbstractSqueakV3PlusClosuresBytecodeGenerator.class/instance/instructions/pushLiteralVariable_.st A OpalCompiler-Core.package/IRAbstractSqueakV3PlusClosuresBytecodeGenerator.class/instance/instructions/pushLiteral_.st A OpalCompiler-Core.package/IRAbstractSqueakV3PlusClosuresBytecodeGenerator.class/instance/instructions/pushNewArray_.st A OpalCompiler-Core.package/IRAbstractSqueakV3PlusClosuresBytecodeGenerator.class/instance/instructions/pushReceiver.st A OpalCompiler-Core.package/IRAbstractSqueakV3PlusClosuresBytecodeGenerator.class/instance/instructions/pushRemoteTemp_inVectorAt_.st A OpalCompiler-Core.package/IRAbstractSqueakV3PlusClosuresBytecodeGenerator.class/instance/instructions/pushTemp_.st A OpalCompiler-Core.package/IRAbstractSqueakV3PlusClosuresBytecodeGenerator.class/instance/instructions/pushThisContext.st A OpalCompiler-Core.package/IRAbstractSqueakV3PlusClosuresBytecodeGenerator.class/instance/instructions/returnConstant_.st A OpalCompiler-Core.package/IRAbstractSqueakV3PlusClosuresBytecodeGenerator.class/instance/instructions/returnInstVar_.st A OpalCompiler-Core.package/IRAbstractSqueakV3PlusClosuresBytecodeGenerator.class/instance/instructions/returnReceiver.st A OpalCompiler-Core.package/IRAbstractSqueakV3PlusClosuresBytecodeGenerator.class/instance/instructions/returnTop.st A OpalCompiler-Core.package/IRAbstractSqueakV3PlusClosuresBytecodeGenerator.class/instance/instructions/send_.st A OpalCompiler-Core.package/IRAbstractSqueakV3PlusClosuresBytecodeGenerator.class/instance/instructions/send_toSuperOf_.st A OpalCompiler-Core.package/IRAbstractSqueakV3PlusClosuresBytecodeGenerator.class/instance/instructions/storeInstVar_.st A OpalCompiler-Core.package/IRAbstractSqueakV3PlusClosuresBytecodeGenerator.class/instance/instructions/storeIntoLiteralVariable_.st A OpalCompiler-Core.package/IRAbstractSqueakV3PlusClosuresBytecodeGenerator.class/instance/instructions/storePopInstVar_.st A OpalCompiler-Core.package/IRAbstractSqueakV3PlusClosuresBytecodeGenerator.class/instance/instructions/storePopIntoLiteralVariable_.st A OpalCompiler-Core.package/IRAbstractSqueakV3PlusClosuresBytecodeGenerator.class/instance/instructions/storePopRemoteTemp_inVectorAt_.st A OpalCompiler-Core.package/IRAbstractSqueakV3PlusClosuresBytecodeGenerator.class/instance/instructions/storePopTemp_.st A OpalCompiler-Core.package/IRAbstractSqueakV3PlusClosuresBytecodeGenerator.class/instance/instructions/storeRemoteTemp_inVectorAt_.st A OpalCompiler-Core.package/IRAbstractSqueakV3PlusClosuresBytecodeGenerator.class/instance/instructions/storeTemp_.st A OpalCompiler-Core.package/IRAbstractSqueakV3PlusClosuresBytecodeGenerator.class/instance/private/closureFrom_to_copyNumCopiedValues_numArgs_.st A OpalCompiler-Core.package/IRAbstractSqueakV3PlusClosuresBytecodeGenerator.class/instance/private/jumpBackward_.st A OpalCompiler-Core.package/IRAbstractSqueakV3PlusClosuresBytecodeGenerator.class/instance/private/jumpForward_.st A OpalCompiler-Core.package/IRAbstractSqueakV3PlusClosuresBytecodeGenerator.class/instance/private/jump_if_.st A OpalCompiler-Core.package/IRAbstractSqueakV3PlusClosuresBytecodeGenerator.class/instance/results/quickMethodPrim.st M OpalCompiler-Core.package/IRBytecodeDecompiler.class/instance/quick methods/quickMethod.st M OpalCompiler-Core.package/IRSistaV1BytecodeGenerator.class/instance/results/compiledMethodWith_.st A OpalCompiler-Core.package/IRSpurSqueakV3PlusClosuresBytecodeGenerator.class/README.md A OpalCompiler-Core.package/IRSpurSqueakV3PlusClosuresBytecodeGenerator.class/definition.st A OpalCompiler-Core.package/IRSpurSqueakV3PlusClosuresBytecodeGenerator.class/instance/accessing/hasPrimitive.st A OpalCompiler-Core.package/IRSpurSqueakV3PlusClosuresBytecodeGenerator.class/instance/initialize/initialize.st A OpalCompiler-Core.package/IRSpurSqueakV3PlusClosuresBytecodeGenerator.class/instance/initialize/irPrimitive_.st A OpalCompiler-Core.package/IRSpurSqueakV3PlusClosuresBytecodeGenerator.class/instance/instructions/checkTooManyLiterals_.st A OpalCompiler-Core.package/IRSpurSqueakV3PlusClosuresBytecodeGenerator.class/instance/results/compiledMethodWith_.st M OpalCompiler-Core.package/IRSqueakV3PlusClosuresBytecodeGenerator.class/README.md R OpalCompiler-Core.package/IRSqueakV3PlusClosuresBytecodeGenerator.class/class/initialize/bytecodeTableFrom_.st R OpalCompiler-Core.package/IRSqueakV3PlusClosuresBytecodeGenerator.class/class/initialize/initializeBytecodeTable.st R OpalCompiler-Core.package/IRSqueakV3PlusClosuresBytecodeGenerator.class/class/initialize/initializeSpecialConstants.st R OpalCompiler-Core.package/IRSqueakV3PlusClosuresBytecodeGenerator.class/class/initialize/specialConstants.st M OpalCompiler-Core.package/IRSqueakV3PlusClosuresBytecodeGenerator.class/definition.st R OpalCompiler-Core.package/IRSqueakV3PlusClosuresBytecodeGenerator.class/instance/instructions/blockReturnTop.st A OpalCompiler-Core.package/IRSqueakV3PlusClosuresBytecodeGenerator.class/instance/instructions/checkTooManyLiterals_.st R OpalCompiler-Core.package/IRSqueakV3PlusClosuresBytecodeGenerator.class/instance/instructions/popTop.st R OpalCompiler-Core.package/IRSqueakV3PlusClosuresBytecodeGenerator.class/instance/instructions/pushConsArray_.st R OpalCompiler-Core.package/IRSqueakV3PlusClosuresBytecodeGenerator.class/instance/instructions/pushDup.st R OpalCompiler-Core.package/IRSqueakV3PlusClosuresBytecodeGenerator.class/instance/instructions/pushInstVar_.st R OpalCompiler-Core.package/IRSqueakV3PlusClosuresBytecodeGenerator.class/instance/instructions/pushLiteralVariable_.st R OpalCompiler-Core.package/IRSqueakV3PlusClosuresBytecodeGenerator.class/instance/instructions/pushLiteral_.st R OpalCompiler-Core.package/IRSqueakV3PlusClosuresBytecodeGenerator.class/instance/instructions/pushNewArray_.st R OpalCompiler-Core.package/IRSqueakV3PlusClosuresBytecodeGenerator.class/instance/instructions/pushReceiver.st R OpalCompiler-Core.package/IRSqueakV3PlusClosuresBytecodeGenerator.class/instance/instructions/pushRemoteTemp_inVectorAt_.st R OpalCompiler-Core.package/IRSqueakV3PlusClosuresBytecodeGenerator.class/instance/instructions/pushTemp_.st R OpalCompiler-Core.package/IRSqueakV3PlusClosuresBytecodeGenerator.class/instance/instructions/pushThisContext.st R OpalCompiler-Core.package/IRSqueakV3PlusClosuresBytecodeGenerator.class/instance/instructions/returnConstant_.st R OpalCompiler-Core.package/IRSqueakV3PlusClosuresBytecodeGenerator.class/instance/instructions/returnInstVar_.st R OpalCompiler-Core.package/IRSqueakV3PlusClosuresBytecodeGenerator.class/instance/instructions/returnReceiver.st R OpalCompiler-Core.package/IRSqueakV3PlusClosuresBytecodeGenerator.class/instance/instructions/returnTop.st R OpalCompiler-Core.package/IRSqueakV3PlusClosuresBytecodeGenerator.class/instance/instructions/send_.st R OpalCompiler-Core.package/IRSqueakV3PlusClosuresBytecodeGenerator.class/instance/instructions/send_toSuperOf_.st R OpalCompiler-Core.package/IRSqueakV3PlusClosuresBytecodeGenerator.class/instance/instructions/storeInstVar_.st R OpalCompiler-Core.package/IRSqueakV3PlusClosuresBytecodeGenerator.class/instance/instructions/storeIntoLiteralVariable_.st R OpalCompiler-Core.package/IRSqueakV3PlusClosuresBytecodeGenerator.class/instance/instructions/storePopInstVar_.st R OpalCompiler-Core.package/IRSqueakV3PlusClosuresBytecodeGenerator.class/instance/instructions/storePopIntoLiteralVariable_.st R OpalCompiler-Core.package/IRSqueakV3PlusClosuresBytecodeGenerator.class/instance/instructions/storePopRemoteTemp_inVectorAt_.st R OpalCompiler-Core.package/IRSqueakV3PlusClosuresBytecodeGenerator.class/instance/instructions/storePopTemp_.st R OpalCompiler-Core.package/IRSqueakV3PlusClosuresBytecodeGenerator.class/instance/instructions/storeRemoteTemp_inVectorAt_.st R OpalCompiler-Core.package/IRSqueakV3PlusClosuresBytecodeGenerator.class/instance/instructions/storeTemp_.st R OpalCompiler-Core.package/IRSqueakV3PlusClosuresBytecodeGenerator.class/instance/private/closureFrom_to_copyNumCopiedValues_numArgs_.st R OpalCompiler-Core.package/IRSqueakV3PlusClosuresBytecodeGenerator.class/instance/private/jumpBackward_.st R OpalCompiler-Core.package/IRSqueakV3PlusClosuresBytecodeGenerator.class/instance/private/jumpForward_.st R OpalCompiler-Core.package/IRSqueakV3PlusClosuresBytecodeGenerator.class/instance/private/jump_if_.st M OpalCompiler-Core.package/IRSqueakV3PlusClosuresBytecodeGenerator.class/instance/results/compiledMethodWith_.st R OpalCompiler-Core.package/IRSqueakV3PlusClosuresBytecodeGenerator.class/instance/results/quickMethodPrim.st A OpalCompiler-Tests.package/OCBytecodeGeneratorTest.class/instance/helper/newBytecodeGen.st A OpalCompiler-Tests.package/OCBytecodeGeneratorTest.class/instance/helper/testMethod_against_.st M OpalCompiler-Tests.package/OCBytecodeGeneratorTest.class/instance/tests - errors/testPushRemoteTempInVectorAtOutOfRange.st M OpalCompiler-Tests.package/OCBytecodeGeneratorTest.class/instance/tests - errors/testPushRemoteTempOutOfRangeInVectorAt.st M OpalCompiler-Tests.package/OCBytecodeGeneratorTest.class/instance/tests - errors/testStoreRemoteTempInVectorAtOutOfRange.st M OpalCompiler-Tests.package/OCBytecodeGeneratorTest.class/instance/tests - errors/testStoreRemoteTempOutOfRangeInVectorAt.st M OpalCompiler-Tests.package/OCBytecodeGeneratorTest.class/instance/tests - execution/testClosureExample.st M OpalCompiler-Tests.package/OCBytecodeGeneratorTest.class/instance/tests - execution/testExample.st M OpalCompiler-Tests.package/OCBytecodeGeneratorTest.class/instance/tests - execution/testExample2.st M OpalCompiler-Tests.package/OCBytecodeGeneratorTest.class/instance/tests - instructions/testBlockReturnTop.st M OpalCompiler-Tests.package/OCBytecodeGeneratorTest.class/instance/tests - instructions/testGoTo.st M OpalCompiler-Tests.package/OCBytecodeGeneratorTest.class/instance/tests - instructions/testGoToIf.st M OpalCompiler-Tests.package/OCBytecodeGeneratorTest.class/instance/tests - instructions/testIfGoTo.st M OpalCompiler-Tests.package/OCBytecodeGeneratorTest.class/instance/tests - instructions/testIfGoToOtherWise.st M OpalCompiler-Tests.package/OCBytecodeGeneratorTest.class/instance/tests - instructions/testLabel.st M OpalCompiler-Tests.package/OCBytecodeGeneratorTest.class/instance/tests - instructions/testPopTop.st M OpalCompiler-Tests.package/OCBytecodeGeneratorTest.class/instance/tests - instructions/testPushClosureCopyNumCopiedValuesNumArgsTo.st M OpalCompiler-Tests.package/OCBytecodeGeneratorTest.class/instance/tests - instructions/testPushConsArray.st M OpalCompiler-Tests.package/OCBytecodeGeneratorTest.class/instance/tests - instructions/testPushDup.st M OpalCompiler-Tests.package/OCBytecodeGeneratorTest.class/instance/tests - instructions/testPushInstVar.st M OpalCompiler-Tests.package/OCBytecodeGeneratorTest.class/instance/tests - instructions/testPushLiteral.st M OpalCompiler-Tests.package/OCBytecodeGeneratorTest.class/instance/tests - instructions/testPushLiteralVariable.st M OpalCompiler-Tests.package/OCBytecodeGeneratorTest.class/instance/tests - instructions/testPushNewArray.st M OpalCompiler-Tests.package/OCBytecodeGeneratorTest.class/instance/tests - instructions/testPushReceiver.st M OpalCompiler-Tests.package/OCBytecodeGeneratorTest.class/instance/tests - instructions/testPushRemoteTempInVectorAt.st M OpalCompiler-Tests.package/OCBytecodeGeneratorTest.class/instance/tests - instructions/testPushTemp.st M OpalCompiler-Tests.package/OCBytecodeGeneratorTest.class/instance/tests - instructions/testPushThisContext.st M OpalCompiler-Tests.package/OCBytecodeGeneratorTest.class/instance/tests - instructions/testReturnConstant.st M OpalCompiler-Tests.package/OCBytecodeGeneratorTest.class/instance/tests - instructions/testReturnInstVar.st M OpalCompiler-Tests.package/OCBytecodeGeneratorTest.class/instance/tests - instructions/testReturnReceiver.st M OpalCompiler-Tests.package/OCBytecodeGeneratorTest.class/instance/tests - instructions/testReturnTop.st M OpalCompiler-Tests.package/OCBytecodeGeneratorTest.class/instance/tests - instructions/testSend.st M OpalCompiler-Tests.package/OCBytecodeGeneratorTest.class/instance/tests - instructions/testSendToSuperOf.st M OpalCompiler-Tests.package/OCBytecodeGeneratorTest.class/instance/tests - instructions/testStoreInstVar.st M OpalCompiler-Tests.package/OCBytecodeGeneratorTest.class/instance/tests - instructions/testStoreIntoLiteralVariable.st M OpalCompiler-Tests.package/OCBytecodeGeneratorTest.class/instance/tests - instructions/testStoreLiteralVariable.st M OpalCompiler-Tests.package/OCBytecodeGeneratorTest.class/instance/tests - instructions/testStorePopInstVar.st M OpalCompiler-Tests.package/OCBytecodeGeneratorTest.class/instance/tests - instructions/testStorePopIntoLiteralVariable.st M OpalCompiler-Tests.package/OCBytecodeGeneratorTest.class/instance/tests - instructions/testStorePopRemoteTempInVectorAt.st M OpalCompiler-Tests.package/OCBytecodeGeneratorTest.class/instance/tests - instructions/testStorePopTemp.st M OpalCompiler-Tests.package/OCBytecodeGeneratorTest.class/instance/tests - instructions/testStoreRemoteTempInVectorAt.st M OpalCompiler-Tests.package/OCBytecodeGeneratorTest.class/instance/tests - instructions/testStoreTemp.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/script308.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40308.st M ScriptLoader40.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 40308 14218 Opal should be able to compile methods for SqueakV3PlusClosure and Spur https://pharo.fogbugz.com/f/cases/14218 http://files.pharo.org/image/40/40308.zip

Oct. 16, 2014

Re: [Pharo-dev] [squeak-dev] Re: [Pharo-users] Trouble opening large files

by Nicolai Hess

done: 14250 <https://pharo.fogbugz.com/default.asp?14250> Enable large file support on linux 2014-10-16 9:03 GMT+02:00 Nicolai Hess <nicolaihess(a)web.de>: > I'll open an issue. > > > > 2014-10-15 8:46 GMT+02:00 stepharo <stepharo(a)free.fr>: > >> Do we create an issue for the Pharo-vm? >> >> Stef >> >> >> On 14/10/14 21:29, Nicolai Hess wrote: >> >> Ah, good to know. At least for squeak, >> bug 7522 can be closed :) >> >> Nicolai >> >> 2014-10-14 20:49 GMT+02:00 Eliot Miranda <eliot.miranda(a)gmail.com>: >> >>> Hi Nicolai, >>> >>> On Tue, Oct 14, 2014 at 11:26 AM, Nicolai Hess <nicolaihess(a)web.de> >>> wrote: >>> >>>> There is a bug report on mantis for squeaks unix vm. >>>> I think this applies to pharo too, although I don't know if this >>>> bug is still valid on recent squeak vm. >>>> >>>> http://bugs.squeak.org/view.php?id=7522 >>>> >>> >>> yes, one must compile with -D_FILE_OFFSET_BITS=64. The Cog VMs are >>> also built with -D_GNU_SOURCE. >>> >>> Here's a line from a Squeak file list on the current Cog VM: >>> >>> (2014.10.11 07:00:46 7,115,143,880) >>> Formula1.2014.Round16.Russia.Qualifying.BBCOneHD.1080i.H264.English-wserhkzt.ts >>> >>> No 32-bit limit here. >>> >>> >>>> >>>> 2014-10-14 17:43 GMT+02:00 Evan Donahue <emdonahu(a)gmail.com>: >>>> >>>>> The OS is Arch Linux. >>>>> >>>>> I can read the file with less. >>>>> >>>>> The problem, insofar as I can trace it, seems to stem from this line >>>>> in UnixStore: >>>>> >>>>> Primitives lookupDirectory: encodedPath filename: encodedBasename >>>>> >>>>> When I have my 57G file there this line returns nil. If I move the >>>>> 57G file and create a small file with the same name, the same command >>>>> successfully finds the file. I am not sure how large a file must be to >>>>> cause this issue, but A 1.5G file works fine. >>>>> >>>>> On Tue, Oct 14, 2014 at 8:17 AM, Nicolai Hess <nicolaihess(a)web.de> >>>>> wrote: >>>>> >>>>>> 2014-10-14 6:38 GMT+02:00 Evan Donahue <emdonahu(a)gmail.com>: >>>>>> >>>>>>> Hi, thanks for the reply. >>>>>>> >>>>>>> The response is the same: "MessageNotUnderstood: >>>>>>> False>>humanReadableSIByteSize." >>>>>>> >>>>>>> This happens both to print-it as well as to do-it-and-go. Running >>>>>>> the command on the neighboring "wiki.torrent" torrent file yields the >>>>>>> correct 54kb. >>>>>>> >>>>>>> Thanks, >>>>>>> Evan >>>>>>> >>>>>>> On Tue, Oct 14, 2014 at 12:24 AM, Tudor Girba <tudor(a)tudorgirba.com> >>>>>>> wrote: >>>>>>> >>>>>>>> Hi, >>>>>>>> >>>>>>>> If I understand correctly, the failure occurs while navigating in >>>>>>>> the "Items" presentation. >>>>>>>> >>>>>>>> I cannot reproduce this problem because I do not have enough disk >>>>>>>> space for such a large file :). But, could you do the following and let me >>>>>>>> know what the outcome is: >>>>>>>> >>>>>>>> 'path/to/your/large/file.xml' asFileReference humanReadableSize >>>>>>>> >>>>>>>> ? >>>>>>>> >>>>>>>> Cheers, >>>>>>>> Doru >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> On Tue, Oct 14, 2014 at 2:27 AM, Evan Donahue <emdonahu(a)gmail.com> >>>>>>>> wrote: >>>>>>>> >>>>>>>>> Hello, I've run into some odd behavior and wanted to check >>>>>>>>> whether I might be missing something: >>>>>>>>> >>>>>>>>> I have downloaded a copy of the english wikipedia as an xml file >>>>>>>>> and am hoping to (sax) parse it. However, I can't even seem to get pharo to >>>>>>>>> recognize that the file exists. >>>>>>>>> >>>>>>>>> If I open FileSystem disk root in the playground and naigate, >>>>>>>>> attempting to enter the folder containing the (57G) xml file fails with >>>>>>>>> "MessageNotUnderstood: False>>humanReadableSIByteSize." Likewise if I get a >>>>>>>>> FileReference with FileSystem disk root / 'path' / 'to' / 'file' then self >>>>>>>>> exists returns false and the parser fails. >>>>>>>>> >>>>>>>>> Am I doing something wrong? Should I be able to do this? >>>>>>>>> >>>>>>>>> The version number is #40283 >>>>>>>>> >>>>>>>>> Thanks, >>>>>>>>> Evan >>>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> -- >>>>>>>> www.tudorgirba.com >>>>>>>> >>>>>>>> "Every thing has its own flow" >>>>>>>> >>>>>>> >>>>>>> >>>>>> >>>>>> Which OS ? >>>>>> Can you check with other programs if this file is readable at all? >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> Nicolai >>>>>> >>>>>> >>>>>> >>>>> >>>> >>>> >>>> >>>> >>> >>> >>> -- >>> best, >>> Eliot >>> >> >> >> >

Oct. 16, 2014

Re: [Pharo-dev] [squeak-dev] Re: [Pharo-users] Trouble opening large files

by Nicolai Hess

I'll open an issue. 2014-10-15 8:46 GMT+02:00 stepharo <stepharo(a)free.fr>: > Do we create an issue for the Pharo-vm? > > Stef > > > On 14/10/14 21:29, Nicolai Hess wrote: > > Ah, good to know. At least for squeak, > bug 7522 can be closed :) > > Nicolai > > 2014-10-14 20:49 GMT+02:00 Eliot Miranda <eliot.miranda(a)gmail.com>: > >> Hi Nicolai, >> >> On Tue, Oct 14, 2014 at 11:26 AM, Nicolai Hess <nicolaihess(a)web.de> >> wrote: >> >>> There is a bug report on mantis for squeaks unix vm. >>> I think this applies to pharo too, although I don't know if this >>> bug is still valid on recent squeak vm. >>> >>> http://bugs.squeak.org/view.php?id=7522 >>> >> >> yes, one must compile with -D_FILE_OFFSET_BITS=64. The Cog VMs are >> also built with -D_GNU_SOURCE. >> >> Here's a line from a Squeak file list on the current Cog VM: >> >> (2014.10.11 07:00:46 7,115,143,880) >> Formula1.2014.Round16.Russia.Qualifying.BBCOneHD.1080i.H264.English-wserhkzt.ts >> >> No 32-bit limit here. >> >> >>> >>> 2014-10-14 17:43 GMT+02:00 Evan Donahue <emdonahu(a)gmail.com>: >>> >>>> The OS is Arch Linux. >>>> >>>> I can read the file with less. >>>> >>>> The problem, insofar as I can trace it, seems to stem from this line >>>> in UnixStore: >>>> >>>> Primitives lookupDirectory: encodedPath filename: encodedBasename >>>> >>>> When I have my 57G file there this line returns nil. If I move the 57G >>>> file and create a small file with the same name, the same command >>>> successfully finds the file. I am not sure how large a file must be to >>>> cause this issue, but A 1.5G file works fine. >>>> >>>> On Tue, Oct 14, 2014 at 8:17 AM, Nicolai Hess <nicolaihess(a)web.de> >>>> wrote: >>>> >>>>> 2014-10-14 6:38 GMT+02:00 Evan Donahue <emdonahu(a)gmail.com>: >>>>> >>>>>> Hi, thanks for the reply. >>>>>> >>>>>> The response is the same: "MessageNotUnderstood: >>>>>> False>>humanReadableSIByteSize." >>>>>> >>>>>> This happens both to print-it as well as to do-it-and-go. Running >>>>>> the command on the neighboring "wiki.torrent" torrent file yields the >>>>>> correct 54kb. >>>>>> >>>>>> Thanks, >>>>>> Evan >>>>>> >>>>>> On Tue, Oct 14, 2014 at 12:24 AM, Tudor Girba <tudor(a)tudorgirba.com> >>>>>> wrote: >>>>>> >>>>>>> Hi, >>>>>>> >>>>>>> If I understand correctly, the failure occurs while navigating in >>>>>>> the "Items" presentation. >>>>>>> >>>>>>> I cannot reproduce this problem because I do not have enough disk >>>>>>> space for such a large file :). But, could you do the following and let me >>>>>>> know what the outcome is: >>>>>>> >>>>>>> 'path/to/your/large/file.xml' asFileReference humanReadableSize >>>>>>> >>>>>>> ? >>>>>>> >>>>>>> Cheers, >>>>>>> Doru >>>>>>> >>>>>>> >>>>>>> >>>>>>> On Tue, Oct 14, 2014 at 2:27 AM, Evan Donahue <emdonahu(a)gmail.com> >>>>>>> wrote: >>>>>>> >>>>>>>> Hello, I've run into some odd behavior and wanted to check >>>>>>>> whether I might be missing something: >>>>>>>> >>>>>>>> I have downloaded a copy of the english wikipedia as an xml file >>>>>>>> and am hoping to (sax) parse it. However, I can't even seem to get pharo to >>>>>>>> recognize that the file exists. >>>>>>>> >>>>>>>> If I open FileSystem disk root in the playground and naigate, >>>>>>>> attempting to enter the folder containing the (57G) xml file fails with >>>>>>>> "MessageNotUnderstood: False>>humanReadableSIByteSize." Likewise if I get a >>>>>>>> FileReference with FileSystem disk root / 'path' / 'to' / 'file' then self >>>>>>>> exists returns false and the parser fails. >>>>>>>> >>>>>>>> Am I doing something wrong? Should I be able to do this? >>>>>>>> >>>>>>>> The version number is #40283 >>>>>>>> >>>>>>>> Thanks, >>>>>>>> Evan >>>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> www.tudorgirba.com >>>>>>> >>>>>>> "Every thing has its own flow" >>>>>>> >>>>>> >>>>>> >>>>> >>>>> Which OS ? >>>>> Can you check with other programs if this file is readable at all? >>>>> >>>>> >>>>> >>>>> >>>>> Nicolai >>>>> >>>>> >>>>> >>>> >>> >>> >>> >>> >> >> >> -- >> best, >> Eliot >> > > >

Oct. 16, 2014

Re: [Pharo-dev] OSProcess in 3.0

by David T. Lewis

On Tue, Oct 14, 2014 at 09:35:44PM +0200, Thierry Goubier wrote: > > > Le 14/10/2014 14:15, David T. Lewis a ?crit : > >On Tue, Oct 14, 2014 at 07:19:10AM +0200, Thierry Goubier wrote: > >>Hi Dave, > >> > >>took me a while to do some testing. It seems there is an issue, but I > >>couldn't find out where. First, the data: > >> > >>Loading a package from a local gitfiletree repository (get from the > >>command a zipped git archive containing the package) : > >> > >>4.5.11, 4.6.8: 2132 msec. > >>4.5.12, 4.6.9: 50847 msec. > >> > >>I tried to rewrite the main command, remove the closePipes, etc... No > >>change in the runtime, so your right. > >> > >>Profiling doesn't help much: execution time is mostly idle time (but > >>with a significant increase on PipeableOSProcess commands: goes from > >>invisible to 2700 ms. A user break in the middle shows it delay waiting > >>on output of the external process). > >> > >>Only hint I could see is that it seems to be linked with the size of the > >>output of the command. > > > >Thierry, > > > >Aha! I am quite sure that you have located the problem. There must be > >something preventing the OS process from running to completion with > >a larger amount of output data. It definitely sounds like a bug in my > >latest update to Pipeable OSProcess. > > The strange thing is that it runs to completion (i.e. I got no errors; > if any data was missing or corrupted on output, my load would fail); but > a lot slower than it should be. > > >Thank you very much for finding this. I will get it fixed as quickly > >as I can. > > Thanks. I'm unable to help you much, I'm afraid :( Thierry, I do not yet have a solution to this, but I have been able to confirm that the performance difference that you see is primarily associated with the AioPlugin not being present in your VM. When I changed PipeableOSProcess to handle pipe handle closing properly, I used a buffered output stream that is driven by aio events. When data is available to be read from the external OS process, an aio notification pulls the available data into the buffered stream, and when no more data is available, the pipe (file) handles are closed. If the plugin is not present in the VM, I provided a polling mechanism to read data from the external OS process. Apparently this is very inefficient, and I am sure it could be greatly improved. That is the cause of the extremely slow performance that you are seeing. So in summary: The enhancement to PipeableOSProcess relies on an aio event driven reader, and if the AIO plugin is missing, the fallback code relies on polling, and is horribly inefficient. More to follow, and thank you again for identifying the problem. If you can convice your VM vendor to include AioPlugin in your VM, that would be helpful also ;-) Dave

Oct. 15, 2014

Re: [Pharo-dev] [Screencast] Using ZnLogEvents and GT Tools to look at HTTP traffic behind Monticello

by Sven Van Caekenberghe

On 15 Oct 2014, at 21:57, phil(a)highoctane.be wrote: > Nice! > > I'll try the Announcers thing on a Seaside session. > > How would you do that? I mean DynamicVariables in GT. > > âPhil I am not sure I understand the question. I did/do Announcement based logging in Seaside, just firing them globally. But I did add a session ID to each log event so that you can keep them apart. My custom WASession subclass adds its #key and #username to the log event objects. I'll send you some example output in private. Sven

Oct. 15, 2014

Re: [Pharo-dev] [Screencast] Using ZnLogEvents and GT Tools to look at HTTP traffic behind Monticello

by phil＠highoctane.be

Nice! I'll try the Announcers thing on a Seaside session. How would you do that? I mean DynamicVariables in GT. âPhil

Oct. 15, 2014

Re: [Pharo-dev] Tests around Pharo

by mschepens

I finally managed the proxy problem by sending commits from my own web connection. So I put the issues to "Fix review needed". I had some problems while importing Collections-Tests (Native part, for the FloatArrayTest) but finally managed it too. I sent to Damien Cassou the "license agreements" filled and signed, I will give him my copy of this paper next wednesday. Hope our tests will be helpful and will increase test coverage of pharo, it was really interesting for us to work on this project, and we acquired significant knowledges (about smalltalk but about opensource projects too). We'll follow our commits evolution, and again thanks to all of you for the time you gave us ! -- View this message in context: http://forum.world.st/Tests-around-Pharo-tp4777295p4784793.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Oct. 15, 2014

Re: [Pharo-dev] CompiledMethod>>hash can produce clashes

by Eliot Miranda

On Wed, Oct 15, 2014 at 11:53 AM, Richard Sargent < richard.sargent(a)gemtalksystems.com> wrote: > Eliot Miranda-2 wrote > > On Wed, Oct 15, 2014 at 10:50 AM, Richard Sargent < > > > richard.sargent@ > > >> wrote: > >> One of the best things about Smalltalk is how easily we can say what we > >> mean. I think you would be better off creating a method named something > >> like > >> #hasSameEffectAs: to answer what you are presently using #= to do, and > >> change #= to answer the, in my opinion, more sensible "is the same as" > >> that > >> we conventionally think of #= meaning. > >> > > > > But that's the point. #= has to mean something and having it mean #== > > isn't useful, so one has to choose some value-based semantic for > > CompiledMethod>>#= and the one that's there is useful. Defining what #= > > means for some value type is far easier than defining what it might mean > > for something as complex as a CompiledMethod. The definition in > > Squeak/Pharo has been useful to me in implementing a closure-based > system, > > so I'm unapologetic about the current definition. It is a good one but > it > > doesn't preclude defining others. > > An interesting response. You ignored the point that e.g. #hasSameEffectAs: > provides greater clarity and add an argument against something I didn't > say. > It's a given. But the selector still isn't perfectly informative, see below. And what's the effect? The effect when executed, so why not hasSameEffectWhenExecuted:? It's a mouthful. I also don't think defining equality for a CompiledMethod is particularly > difficult. If I were to recompile a method's source code, I would get a new > instance of a CompiledMethod that would, in my opinion, be equal to the one > already installed in the class (and perhaps cached in the VM's > optimizations). So one would be able to say that we would not replace an > existing CompiledMethod with an equal one. The current implementation of #= > has no such characteristic, since it proclaims a CompiledMethod named #a to > be equal to one named #z. > And for some uses that is correct, one names a /is/ equal to one named z, even though their selectors differ. For example if you do the following: aClass compile: 'a ^1'; compile: 'b ^ 1'. aClass compiledMethodAt: #a put: aClass >> #b then "aClass new a" still answers 1. It's only if one introspects (thisContext method selector, opens the debugger, etc) that one sees that the selector doesn't match. If you go back to Smalltalk-80 you'll see that compiled methods didn't store their selector and to find out their selector one searched the method dictionary of the method's method class. As far as what most methods do (excluding introspecting code) the selector is merely a cache of the key in the relevant method dictionary. So #hasSameEffect: *doesn't* mean what one might think it means for some uses (it doesn't only depend on the method in question, but on usage, whether the method is used in an introspective context, etc). So naming a more explanatory selector is more difficult than you might think. The blue book say #= means "Answer whether the receiver and the argument > represent the same component." The current implementation does so only for > some, in my opinion, counter-intuitive definition of "same component". > Well Smalltalk-80 says Answer true if the receiver and the argument represent the same object and false otherwise. If = is redefined in any subclass, consider also redefining the message hash. and that's just as vague (AFAIA the blue book doesn't define what a component is), because whether objects are equal or not depends on usage. In the end the system is full of definitions of #= which are more or less generally useful in various contexts. Things are easy for the arithmetic types, but for more complex objects there are always caveats | s1 s2 | s1 := Set new. s1 add: s1. s2 := Set new. s2 add: s2. s1 = s2 doesn't terminate. So should Set's #= be called isEqualIfNonRecursive: ? No. Its limited #= is fine in practice and much better than Smalltalk-80's original fall back to #==. But it is not a perfect equality. Neither is CompiledMethod's. But it being imperfect is not an argument for changing it to another, inevitably also flawed definition without good reason. -- > View this message in context: > http://forum.world.st/CompiledMethod-hash-can-produce-clashes-tp4784722p478… > Sent from the Pharo Smalltalk Developers mailing list archive at > Nabble.com. > -- best, Eliot

Oct. 15, 2014