- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Having comments for pragma?

by Eliot Miranda

> On Jun 28, 2016, at 8:17 AM, Denis Kudriashov <dionisiydk(a)gmail.com> wrote: > > Following this "bad idea" we should agree that smalltalk metaclass system is horrible and class should be just a language artifact > Are you being serious or sarcastic? > 28 Ð¸ÑÐ½Ñ 2016 Ð³. 11:45 Ð¿Ð¾Ð»ÑÐ·Ð¾Ð²Ð°ÑÐµÐ»Ñ "Jan Vrany" <jan.vrany(a)fit.cvut.cz> Ð½Ð°Ð¿Ð¸ÑÐ°Ð»: >> >> >>> On Mon, Jun 27, 2016 at 1:09 PM, Nicolas Passerini <npasserini(a)gmail.com> wrote: >>> >>> >>>> On Mon, Jun 27, 2016 at 1:44 PM, Denis Kudriashov <dionisiydk(a)gmail.com> wrote: >>>> >>>> 2016-06-27 13:28 GMT+02:00 Nicolas Passerini <npasserini(a)gmail.com>: >>>>> That is not quite true, annotations are (kind of) objects but you can not put behavior in them, just define attributes and optionally default values for those attributes. >>>> >>>> Ah, you are right. I remember many restrictions was applied to them which always forced me to hate Java :) >>> >>> Yep. >> >> Well, there's a reason why they're restricted. Note, that the restriction is on language level, not at runtime level. A annotation class >> with arbitrary code would pass JVM verification (or at least I can't see a rule that would reject such a class). >> >> When I implemented annotation support I was initially thinking the same - let's create an instance of CoolAnnotationClass when the code is accepted >> and then one can add arbitrary code to his CoolAnnotationClass. I quickly realized this is a (very) bad idea. Or, to be precise, it is a bad idea given the >> environment. So I'd be very careful.. >> >> Jan >> >> P.S.: As for "which always forced me to hate Java": I found myself a very enlightening to think carefully about why somebody else >> do things differently before I start to hate her/him. Besides, there's whole lot of things that Java guys got right...

June 28, 2016

Re: [Pharo-dev] Smalltalk Hub on Chrome

by Dale Henrichs

With regards to GitLab and Metacello. A couple of years ago, I looked into adding GitLab support to Metacello, similar to `github:\\` for downloading repository without requiring git to be installed and found that there were issues[1] ... Now that was in 2014 and it's possible that GitLab has fiddled with their zip download support, but I haven't checked ... `github://` is convenient but if you are moving to full git support and expect everyone to be cloning projects into local repos (by hook or by crook) not being able to download a zip version of the project is less of a problem ... Dale [1] https://github.com/dalehenrich/metacello-work/issues/287#issuecomment-59815… On 6/27/16 7:05 PM, Ben Coman wrote: > On Tue, Jun 28, 2016 at 6:36 AM, Sean P. DeNigris <sean(a)clipperadams.com> wrote: >> stepharo wrote >>>> maybe we need to consider deprecate the amber client >>>> and use a full-pharo version. >>> Torsten what is the state of your solution? >> Is it worth it to take another trip down this road of rolling-our-own source >> code repo? Whatever we create, we accept the responsibility to maintain, and >> with GitHub's social coding features, BitBucket for free private repo >> hosting, and all the advances in Pharo-git integration, it seems our limited >> resources would be most effectively committed elsewhere... > Jumping ahead to the end game of not needing to support development of > the repository backend ourselves, > there are a couple of levels to this... > > 1. Create a "SmalltalkHub" organisation on github and move *all* > repositories (maintaining privacy. Synchronize between the two servers > for a couple of years so as to not abandon old Pharo versions or break > existing Configurations, or build a thin forwarding service such that > requests received at smalltalkhub interact with github - perhaps this > is read only. Build a thin web SmalltalkHub home page with github > pages at smalltalkhub.io. > > 2. While GitHub gets most of the glory, its closed source and there > are some open source git options to consider like GitLab (MIT license) > or Gerrit (Apache license). This might be the path to choose if we > need some Smalltalk customizations like Smalltalk syntax highlighting. > The advantage of integrating with GitLab would be that the community > could use their hosted solution, but private companies could run their > own GitLab server if they have secrets they want to be more careful > about sharing with third parties. > > 3. We might run a GitLab/Gerrit server in place of the existing > Smalltalkhub server, and make it look the same for pre-git Pharo > clients. There would still be some administration cost, but a larger > community for support, features and bug fixing, or paid support > options. > * https://www.linux.com/learn/how-run-your-own-git-server > * https://about.gitlab.com/applications/ > * https://www.gerritcodereview.com/ > * https://gerrit-review.googlesource.com/Documentation/config-plugins.html > > But these considerations shouldn't stop an intermediate solution. > cheers -ben >

June 28, 2016

[pharo-project/pharo-core] 203c29: 60123

by GitHub

Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: 203c29097f8cf46edded36130a40a51bfaedf21e https://github.com/pharo-project/pharo-core/commit/203c29097f8cf46edded3613… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2016-06-28 (Tue, 28 Jun 2016) Changed paths: A Kernel.package/CompiledBlock.class/instance/accessing/methodClass.st A Kernel.package/CompiledBlock.class/instance/accessing/primitive.st A Kernel.package/CompiledBlock.class/instance/accessing/sourceCode.st A Kernel.package/CompiledCode.class/instance/accessing/bytecode.st A Kernel.package/CompiledCode.class/instance/accessing/clearFlag.st A Kernel.package/CompiledCode.class/instance/accessing/clearSignFlag.st A Kernel.package/CompiledCode.class/instance/accessing/comment.st A Kernel.package/CompiledCode.class/instance/accessing/encoderClass.st A Kernel.package/CompiledCode.class/instance/accessing/endPC.st A Kernel.package/CompiledCode.class/instance/accessing/flag.st A Kernel.package/CompiledCode.class/instance/accessing/frameSize.st A Kernel.package/CompiledCode.class/instance/accessing/initialPC.st A Kernel.package/CompiledCode.class/instance/accessing/numArgs.st A Kernel.package/CompiledCode.class/instance/accessing/numLiterals.st A Kernel.package/CompiledCode.class/instance/accessing/numTemps.st A Kernel.package/CompiledCode.class/instance/accessing/referredInstVars.st A Kernel.package/CompiledCode.class/instance/accessing/scanner.st A Kernel.package/CompiledCode.class/instance/accessing/setSignFlag.st A Kernel.package/CompiledCode.class/instance/accessing/signFlag.st A Kernel.package/CompiledCode.class/instance/accessing/trailer.st A Kernel.package/CompiledCode.class/instance/cleaning/voidCogVMState.st A Kernel.package/CompiledCode.class/instance/comparing/=.st A Kernel.package/CompiledCode.class/instance/comparing/equivalentTo_.st A Kernel.package/CompiledCode.class/instance/comparing/hash.st A Kernel.package/CompiledCode.class/instance/comparing/sameLiteralsAs_.st A Kernel.package/CompiledCode.class/instance/converting/asOrderedCollection.st A Kernel.package/CompiledCode.class/instance/debugger support/pcPreviousTo_.st A Kernel.package/CompiledCode.class/instance/initialize-release/needsFrameSize_.st A Kernel.package/CompiledCode.class/instance/initialize-release/setFrameBit_.st A Kernel.package/CompiledCode.class/instance/literals/allLiterals.st A Kernel.package/CompiledCode.class/instance/literals/hasLiteralSuchThat_.st A Kernel.package/CompiledCode.class/instance/literals/hasLiteralThorough_.st A Kernel.package/CompiledCode.class/instance/literals/hasLiteral_.st A Kernel.package/CompiledCode.class/instance/literals/hasSelector_.st A Kernel.package/CompiledCode.class/instance/literals/hasSelector_specialSelectorIndex_.st A Kernel.package/CompiledCode.class/instance/literals/header.st A Kernel.package/CompiledCode.class/instance/literals/headerDescription.st A Kernel.package/CompiledCode.class/instance/literals/indexOfLiteral_.st A Kernel.package/CompiledCode.class/instance/literals/literalAt_.st A Kernel.package/CompiledCode.class/instance/literals/literalAt_put_.st A Kernel.package/CompiledCode.class/instance/literals/literalStrings.st A Kernel.package/CompiledCode.class/instance/literals/literals.st A Kernel.package/CompiledCode.class/instance/literals/literalsDo_.st A Kernel.package/CompiledCode.class/instance/literals/objectAt_.st A Kernel.package/CompiledCode.class/instance/literals/objectAt_put_.st A Kernel.package/CompiledCode.class/instance/literals/refersToLiteral_.st A Kernel.package/CompiledCode.class/instance/literals/sendsSelector_.st A Kernel.package/CompiledCode.class/instance/printing/asString.st A Kernel.package/CompiledCode.class/instance/printing/longPrintOn_.st A Kernel.package/CompiledCode.class/instance/printing/primitiveErrorVariableName.st A Kernel.package/CompiledCode.class/instance/printing/symbolic.st A Kernel.package/CompiledCode.class/instance/printing/symbolicBytecodes.st A Kernel.package/CompiledCode.class/instance/printing/timeStamp.st A Kernel.package/CompiledCode.class/instance/scanning/abstractBytecodeMessageAt_.st A Kernel.package/CompiledCode.class/instance/scanning/abstractBytecodeMessagesDo_.st A Kernel.package/CompiledCode.class/instance/scanning/abstractBytecodeMessagesFrom_to_do_.st A Kernel.package/CompiledCode.class/instance/scanning/accessesSlot_.st A Kernel.package/CompiledCode.class/instance/scanning/hasInstVarRef.st A Kernel.package/CompiledCode.class/instance/scanning/messages.st A Kernel.package/CompiledCode.class/instance/scanning/readsField_.st A Kernel.package/CompiledCode.class/instance/scanning/readsRef_.st A Kernel.package/CompiledCode.class/instance/scanning/readsSlot_.st A Kernel.package/CompiledCode.class/instance/scanning/scanFor_.st A Kernel.package/CompiledCode.class/instance/scanning/sendsToSuper.st A Kernel.package/CompiledCode.class/instance/scanning/writesField_.st A Kernel.package/CompiledCode.class/instance/scanning/writesRef_.st A Kernel.package/CompiledCode.class/instance/scanning/writesSlot_.st A Kernel.package/CompiledCode.class/instance/source code management/argumentNames.st A Kernel.package/CompiledCode.class/instance/source code management/author.st A Kernel.package/CompiledCode.class/instance/source code management/definition.st A Kernel.package/CompiledCode.class/instance/source code management/stamp.st A Kernel.package/CompiledCode.class/instance/testing/containsHalt.st A Kernel.package/CompiledCode.class/instance/testing/isCollection.st A Kernel.package/CompiledCode.class/instance/testing/isExternalCallPrimitive.st A Kernel.package/CompiledCode.class/instance/testing/isNamedPrimitive.st A Kernel.package/CompiledCode.class/instance/testing/isPrimitive.st A Kernel.package/CompiledCode.class/instance/testing/isQuick.st A Kernel.package/CompiledCode.class/instance/testing/isRealPrimitive.st A Kernel.package/CompiledCode.class/instance/testing/usesPrimaryBytecodeSet.st A Kernel.package/CompiledCode.class/instance/testing/usesSecondaryBytecodeSet.st A Kernel.package/FullBlockClosure.class/README.md A Kernel.package/FullBlockClosure.class/definition.st A Kernel.package/FullBlockClosure.class/instance/accessing/compiledBlock.st A Kernel.package/FullBlockClosure.class/instance/accessing/compiledBlock_.st A Kernel.package/FullBlockClosure.class/instance/accessing/home.st A Kernel.package/FullBlockClosure.class/instance/accessing/method.st A Kernel.package/FullBlockClosure.class/instance/accessing/numArgs_.st A Kernel.package/FullBlockClosure.class/instance/accessing/numTemps.st A Kernel.package/FullBlockClosure.class/instance/accessing/outerContext_.st A Kernel.package/FullBlockClosure.class/instance/accessing/receiver.st A Kernel.package/FullBlockClosure.class/instance/accessing/receiver_.st A Kernel.package/FullBlockClosure.class/instance/accessing/startpc.st A Kernel.package/FullBlockClosure.class/instance/evaluating/value.st A Kernel.package/FullBlockClosure.class/instance/evaluating/valueNoContextSwitch.st A Kernel.package/FullBlockClosure.class/instance/evaluating/valueNoContextSwitch_.st A Kernel.package/FullBlockClosure.class/instance/evaluating/valueWithArguments_.st A Kernel.package/FullBlockClosure.class/instance/evaluating/value_.st A Kernel.package/FullBlockClosure.class/instance/evaluating/value_value_.st A Kernel.package/FullBlockClosure.class/instance/evaluating/value_value_value_.st A Kernel.package/FullBlockClosure.class/instance/evaluating/value_value_value_value_.st A Kernel.package/FullBlockClosure.class/instance/private/asContextWithSender_.st A OpalCompiler-Core.package/extension/CompiledCode/instance/compiler.st A OpalCompiler-Core.package/extension/CompiledCode/instance/compilerClass.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60122.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60123.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60122.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60123.st M ScriptLoader60.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 60123 18105 Introduction of FullBlockClosure (2) Adding the FullBlockClosure class https://pharo.fogbugz.com/f/cases/18105 18503 Introduction of FullBlockClosure (3) Moving code from CompiledMethod to CompiledCode https://pharo.fogbugz.com/f/cases/18503 http://files.pharo.org/image/60/60123.zip

June 28, 2016

Re: [Pharo-dev] Having comments for pragma?

by Denis Kudriashov

Following this "bad idea" we should agree that smalltalk metaclass system is horrible and class should be just a language artifact 28 Ð¸ÑÐ½Ñ 2016 Ð³. 11:45 Ð¿Ð¾Ð»ÑÐ·Ð¾Ð²Ð°ÑÐµÐ»Ñ "Jan Vrany" <jan.vrany(a)fit.cvut.cz> Ð½Ð°Ð¿Ð¸ÑÐ°Ð»: > > > On Mon, Jun 27, 2016 at 1:09 PM, Nicolas Passerini <npasserini(a)gmail.com> > wrote: > > > > On Mon, Jun 27, 2016 at 1:44 PM, Denis Kudriashov <dionisiydk(a)gmail.com> > wrote: > >> >> 2016-06-27 13:28 GMT+02:00 Nicolas Passerini <npasserini(a)gmail.com>: >> >>> That is not quite true, annotations are (kind of) objects but you can >>> not put behavior in them, just define attributes and optionally default >>> values for those attributes. >> >> >> Ah, you are right. I remember many restrictions was applied to them which >> always forced me to hate Java :) >> > > Yep. > > > Well, there's a reason why they're restricted. Note, that the restriction > is on language level, not at runtime level. A annotation class > with arbitrary code would pass JVM verification (or at least I can't see a > rule that would reject such a class). > > When I implemented annotation support I was initially thinking the same - > let's create an instance of CoolAnnotationClass when the code is accepted > and then one can add arbitrary code to his CoolAnnotationClass. I quickly > realized this is a (very) bad idea. Or, to be precise, it is a bad idea > given the > environment. So I'd be very careful.. > > Jan > > P.S.: As for "which always forced me to hate Java": I found myself a very > enlightening to think carefully about why somebody else > do things differently before I start to hate her/him. Besides, there's > whole lot of things that Java guys got right... > > >

June 28, 2016

[pharo-project/pharo-core]

by GitHub

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

June 28, 2016

[pharo-project/pharo-core] d0292c: 60122

by GitHub

Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: d0292cc2e321299e425ddc7a5dfb43bf3497443e https://github.com/pharo-project/pharo-core/commit/d0292cc2e321299e425ddc7a… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2016-06-28 (Tue, 28 Jun 2016) Changed paths: M ConfigurationOfEpicea.package/ConfigurationOfEpicea.class/instance/baselines/baseline72p5_.st M ConfigurationOfEpicea.package/ConfigurationOfEpicea.class/instance/tags/stable_.st A ConfigurationOfEpicea.package/ConfigurationOfEpicea.class/instance/versions/version794p6_.st A ConfigurationOfEpicea.package/ConfigurationOfEpicea.class/instance/versions/version795_.st M Epicea.package/EpLog.class/instance/initialization/initializeWith_.st M Epicea.package/EpLog.class/instance/refreshing/refresh.st M Epicea.package/EpMonitor.class/instance/announcement handling/snapshotDone_.st A Ombu.package/OmEntryReader.class/instance/reading/moveStreamToNextEntry_.st M Ombu.package/OmFileStore.class/instance/refreshing/refresh.st A Ombu.package/OmSTONEntryReader.class/instance/reading/moveStreamToNextEntry_.st M OmbuTests.package/OmFileStoreTest.class/instance/tests/testLoadFromCorruptFile1.st M OmbuTests.package/OmFileStoreTest.class/instance/tests/testLoadFromCorruptFile2.st M OmbuTests.package/OmFileStoreTest.class/instance/tests/testLoadFromCorruptFile3.st M OmbuTests.package/OmFileStoreTest.class/instance/tests/testLoadFromCorruptFile4.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60121.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60122.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60121.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60122.st M ScriptLoader60.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 60122 18374 SmalltalkImage>>backupTo: modifies current working directory https://pharo.fogbugz.com/f/cases/18374 http://files.pharo.org/image/60/60122.zip

June 28, 2016

The .changes file should be bound to a single image

by Max Leske

Hi, Opening the same image twice works fine as long as no writes to the .changes file occur. When both images write to the .changes file however it will be broken for both because the offsets for the changes are wrong. This can lead to lost data and predominantly to invalid method source code, which is a pain with Monticello. I suggest that we implement a kind of lock mechanism to ensure that only one image (the first one opened) can write to the .changes file. Iâve opened an issue for Pharo here: https://pharo.fogbugz.com/f/cases/18635/The-changes-file-should-be-bound-to… Cheers, Max

June 28, 2016

Re: [Pharo-dev] Having comments for pragma?

by Jan Vrany

On Mon, Jun 27, 2016 at 1:09 PM, Nicolas Passerini <npasserini(a)gmail.com> wrote: > > > On Mon, Jun 27, 2016 at 1:44 PM, Denis Kudriashov > <dionisiydk(a)gmail.com> wrote: >> >> 2016-06-27 13:28 GMT+02:00 Nicolas Passerini <npasserini(a)gmail.com>: >>> That is not quite true, annotations are (kind of) objects but you >>> can not put behavior in them, just define attributes and optionally >>> default values for those attributes. >> >> Ah, you are right. I remember many restrictions was applied to them >> which always forced me to hate Java :) > > Yep. Well, there's a reason why they're restricted. Note, that the restriction is on language level, not at runtime level. A annotation class with arbitrary code would pass JVM verification (or at least I can't see a rule that would reject such a class). When I implemented annotation support I was initially thinking the same - let's create an instance of CoolAnnotationClass when the code is accepted and then one can add arbitrary code to his CoolAnnotationClass. I quickly realized this is a (very) bad idea. Or, to be precise, it is a bad idea given the environment. So I'd be very careful.. Jan P.S.: As for "which always forced me to hate Java": I found myself a very enlightening to think carefully about why somebody else do things differently before I start to hate her/him. Besides, there's whole lot of things that Java guys got right...

June 28, 2016

[pharo-project/pharo-core]

by GitHub

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

June 28, 2016

[pharo-project/pharo-core] e5dc3a: 60121

by GitHub

Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: e5dc3a07c6dded60302a7e1edbb48c683ec615aa https://github.com/pharo-project/pharo-core/commit/e5dc3a07c6dded60302a7e1e… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2016-06-28 (Tue, 28 Jun 2016) Changed paths: M Kernel-Rules.package/FloatReferencesRule.class/instance/running/basicCheck_.st M Kernel-Rules.package/FloatReferencesRule.class/instance/running/check_forCritiquesDo_ifNone_.st M Kernel-Rules.package/SendsDeprecatedMethodToGlobalRule.class/instance/running/basicCheck_.st M Kernel-Rules.package/SendsDeprecatedMethodToGlobalRule.class/instance/running/checkMethod_.st M Kernel-Rules.package/SendsDeprecatedMethodToGlobalRule.class/instance/running/check_forCritiquesDo_ifNone_.st M Morphic-Base.package/extension/WorldState/class/debugOn_.st M Network-Tests.package/UDPSocketEchoTest.class/instance/testing/testEcho.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60120.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60121.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60120.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60121.st M ScriptLoader60.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st M Spec-Tools.package/MessageBrowser.class/instance/private/installIconStylerFor_.st Log Message: ----------- 60121 18629 use debug icon for debug submenu https://pharo.fogbugz.com/f/cases/18629 18137 Network test failing only on MAC on CI: UDPSocketEchoTest.testEcho https://pharo.fogbugz.com/f/cases/18137 18626 Guard calls to isGlobal from Rules https://pharo.fogbugz.com/f/cases/18626 18631 Add critiques to message browser https://pharo.fogbugz.com/f/cases/18631 http://files.pharo.org/image/60/60121.zip

June 28, 2016