- Pharo-dev - lists.pharo.org

Git Method Timestamps
by sean＠clipperadams.com Sept. 27, 2021

Sept. 27, 2021

What is the git equivalent to `CompiledCode>>#timeStamp`? (which returns an empty string)

2 2

This week (38/2021) on the Pharo Issue Tracker
by Marcus Denker Sept. 24, 2021

Sept. 24, 2021

We merged 38 pull requests and fixed 26 issues. Pharo9 ====== update Spec version to v1.0.3 and NewTools to v0.6.10 #9974 https://github.com/pharo-project/pharo/pull/9974 BACKPORT-6311-Enhance-Completion-to-be-more-fluid-in-large-images #10003 https://github.com/pharo-project/pharo/pull/10003 - Backport: Pharo 9 + Seaside - Process dying on cloud instance #9987 https://github.com/pharo-project/pharo/pull/9987 Remove Deprecated and Dead Code =============================== - Cleanup methods declared as deprecated #10013 https://github.com/pharo-project/pharo/pull/10013 - Redo #9845 -- Fix 9798: Deprecated class TextConverter is still used #10012 https://github.com/pharo-project/pharo/pull/10012 - cleanup-Display-and-Cursor #9889 https://github.com/pharo-project/pharo/pull/9889 - Cleanup-Duplicated-Methods-09-18 #9989 https://github.com/pharo-project/pharo/pull/9989 - Cleanup: remove unreferenced deprecated class in Spec-Deprecated #9997 https://github.com/pharo-project/pharo/pull/9997 - Cleanup-Deprecated-Spec-Examples-Tests #9975 https://github.com/pharo-project/pharo/pull/9975 - Cleanup-Duplicated-Methods-09-17 #9978 https://github.com/pharo-project/pharo/pull/9978 Speed ===== - 6311-Enhance-Completion-to-be-more-fluid-in-large-images #10002 https://github.com/pharo-project/pharo/pull/10002 - do not re-parse in ReShouldSendSuperSetUpAsFirstMessage and ReShouldSendSuperTearDownAsLastMessage #9988 https://github.com/pharo-project/pharo/pull/9988 Features ======== - String #beginsWith:caseSensitive and #endsWith:caseSensitive: #9960 https://github.com/pharo-project/pharo/pull/9960 Refactoring Tools ================== - Migrating RBMoveMethodToClassRefactoring to RBMoveMethodToClassTransformation #9945 https://github.com/pharo-project/pharo/pull/9945 - Migrated RBTemporaryToInstanceVariableRefactoring to RBTemporaryToInsâ¦ #9944 https://github.com/pharo-project/pharo/pull/9944 Fixes ====== - 9961-cleanup-and-support-CompiledMethodLayout-in-CDClassDefinitionParserhandleClassNamewithType #10022 https://github.com/pharo-project/pharo/pull/10022 - 9936-MCClassDefinitionkindOfSubclass-wrong-for-user-defined-layouts #9939 https://github.com/pharo-project/pharo/pull/9939 - Fix ZnBufferedReadStream>>#setToEnd for ZipArchive usage #8658 https://github.com/pharo-project/pharo/pull/8658 - Fix #8524: Fix Process>>#priority: incorrectly allowing lower priority process run while â¦ #10004 https://github.com/pharo-project/pharo/pull/10004 - Fix #7634: Use "Smalltalk vm wordSize" to determine the version of the VM: 32 or 64 #10008 https://github.com/pharo-project/pharo/pull/10008 - fix: #9992 add pharo10 for metacello #9994 https://github.com/pharo-project/pharo/pull/9994 - 9965-CI-ZipArchiveTesttestArchiveWithThousandFilesShouldWork-sometimes-times-out #9969 https://github.com/pharo-project/pharo/pull/9969 - 9933-isDeprecated-should-not-check-for-the-category #9981 https://github.com/pharo-project/pharo/pull/9981 - Pharo 9 + Seaside - Process dying on cloud instance #9986 https://github.com/pharo-project/pharo/pull/9986 - Improve UI manager to allow testing by reacting to notifications #9979 https://github.com/pharo-project/pharo/pull/9979 - 9925-Defining-variables-in-the-debugger-DNU-isForScripting #9926 https://github.com/pharo-project/pharo/pull/9926 - Improve the flaky test for the ProcessMonitorTestService #9976 https://github.com/pharo-project/pharo/pull/9976 Cleanup ======= - Fixes #9972: SycSourceCodeRefactoringCommand should be tagged abstract #9977 https://github.com/pharo-project/pharo/pull/9977 - cleaning-up-workaround in copyTo: #10006 https://github.com/pharo-project/pharo/pull/10006 - 9970-ReConsistencyCheckRule-is-a-very-bad-name #9998 https://github.com/pharo-project/pharo/pull/9998 - Fix: #7974 deprecate openAndTruncateForWriteFile: #10009 https://github.com/pharo-project/pharo/pull/10009 - Small cleanups - class side initialize and other #9883 https://github.com/pharo-project/pharo/pull/9883 - Release test for #basicNew categorization #9897 https://github.com/pharo-project/pharo/pull/9897 - Improve ProperClassCategorizationTest>>#testProperClassTagCasing #9858 https://github.com/pharo-project/pharo/pull/9858 - [Enable Flaky Tests] Enable continuation flaky test #6768 https://github.com/pharo-project/pharo/pull/6768 - 9955-add-comments-to-mcType-subclassDefiningSymbol-kindOfSubclass #9983 https://github.com/pharo-project/pharo/pull/9983

1 0

About punishment vs. help
by stephane ducasse Sept. 22, 2021

Sept. 22, 2021

Hi guys I would like to have mindset revolution. I would like that Pharo HELPS us to produce good code and not just PUNISH us when we do mistakes. Let me show you an example. I write a little method and as a good and nice programmer I place my little utility method in the utilities protocol. I commit and then I get a FAILED ERROR RED BAR telling that Iâm an asshole because I did not place that &*T^(^&(* method in utils. Something that Cop stuff is not even able to tell me precisely what is the problem There is a method in class X that use an undefined instance variables. I always thought that computers were about doing clever stuffâ¦ but the Cop inside Pharo proves me the inverse. I wonder why instead of investing in stupid rule we do not invest in building simple tool that do the job for us. Why the system cannot recategorise the method for me. Why the system does not remove the unused variable automatically prompting before I commit. Oh my dear StÃ©phane I saw that you left this horrible unused instance variable, do you want me to clean for you? Yes be my guest. This is why I invested by improving the automatic categorizer. This is why I did a tool to analyse the frequency of methods in terms of their protocol and you can ask the tool please fix all badly categorized methods. https://github.com/Ducasse/MethodCategorizer/blob/master/MethodCategorizer/… This is always why I HATE all these %^&*^&(&*^&*(%^(& warnings that get into my way when the system could fix them for me in no time. SO THIS IS A CALL FOR A CHANGE OF PARADIGM Can Pharo help me in my development instead of bitting me? Can we STOP adding more and more dull rules and produce something that HELP US? https://github.com/Ducasse/MethodCategorizer/blob/master/MethodCategorizer/… THIS IS NOT BECAUSE WE HAVE A HAMMER THAT WE SHOULD NAIL EVERYTHING. THIS IS OUR DUTY TO INVENT NEW TOOLS AND NEW WAYS TO HELP DEVELOPERS! S.

1 0

his week (37/2021) on the Pharo Issue Tracker
by Marcus Denker Sept. 17, 2021

Sept. 17, 2021

We merged 10 Pull Requests and closed 7 Issue tracker entries this week. Cleanup: Dead Code =================== Cleanup of Deprecated and useless code continues. - Cleanup-tests-fullblocks #9930 https://github.com/pharo-project/pharo/pull/9930 - Cleanup-Deprecated-09-15 #9967 https://github.com/pharo-project/pharo/pull/9967 - Cleanup-deprecated-09-14 #9957 https://github.com/pharo-project/pharo/pull/9957 - Cleanup-Duplicated-Methods-09-14 #9958 https://github.com/pharo-project/pharo/pull/9958 Fixes ===== Man focus of fixing has been the ClassParser and cleanups related to class layouts so the same mistakes will be harder to do in the future. - 9948-OCRequestorScope-does-not-like-empty-variable-names #9952 https://github.com/pharo-project/pharo/pull/9952 - 9924-CDBehaviorDefinitionNode-uses-subclassDefiningSymbol-not-unique #9959 https://github.com/pharo-project/pharo/pull/9959 - 9909-Deprecate-typeOfClass-and-kind-and-add-mcType-instead #9923 https://github.com/pharo-project/pharo/pull/9923 - CDSlotNode-NoIndex #9949 https://github.com/pharo-project/pharo/pull/9949 Speed ===== - NoSymbolCreation-hasPackageMatchingExtensionName #9941 https://github.com/pharo-project/pharo/pull/9941 Cleanups ======== - Fixes #9972: SycSourceCodeRefactoringCommand should be tagged abstract #9977 https://github.com/pharo-project/pharo/pull/9977

1 0

This week (36/2021) on the Pharo Issue Tracker
by Marcus Denker Sept. 14, 2021

Sept. 14, 2021

A bit lateâ¦ so this is for last week. Dead Code Cleanup: Deprecated Code ================= Ongoing: removing deprecated methods and unused code in general - 9888-FFI-remove-gcpointer #9903 https://github.com/pharo-project/pharo/pull/9903 - 9905-Cleanup-Remove-EyeInspector #9906 https://github.com/pharo-project/pharo/pull/9906 - 9879-AthensCairoSurface-deprecated-methods-still-have-senders #9902 https://github.com/pharo-project/pharo/pull/9902 - Remove-Deprecated-09-03 #9887 https://github.com/pharo-project/pharo/pull/9887 - Remove unnecessary #new methods #9893 https://github.com/pharo-project/pharo/pull/9893 Old Bytecode Set / non full block cleanup ========================================== The idea is that Pharo10 will not support the old Bytecode Set and will only support full blocks. This simplifies the compiler and makes testing simpler, too. - Cleanup-Compiler-remove-tests-optionFullBlockClosure #9910 https://github.com/pharo-project/pharo/pull/9910 - 9928-Do-not-use-optionFullBlockClosure-in-OCASTTranslatorvisitBlockNode #9942 https://github.com/pharo-project/pharo/pull/9942 Fixes ===== - 9901-Fluid-Class-Parser-gets-wrong-symbols-from-the-layout-kind #9908 https://github.com/pharo-project/pharo/pull/9908 - Pharo10 - 9038-windows edges grabbing for resizing not optimal #9920 https://github.com/pharo-project/pharo/pull/9920 - 9308 code critics improving critic description api change api hints architectural #9426 https://github.com/pharo-project/pharo/pull/9426 Improvements ============= - enhance code changes browser a little bit #9937 https://github.com/pharo-project/pharo/pull/9937 - another small improvement in the UI of code changes #9940 https://github.com/pharo-project/pharo/pull/9940 - 9877-SmalltalkImagepackages-should-not-sort #9904 https://github.com/pharo-project/pharo/pull/9904 - Rewrote and improved String >> skipAnySubstring:startingAt: #9277 https://github.com/pharo-project/pharo/pull/9277 Cleanup ======= - modify Spec2-Common-Widgets dependencies #9911 https://github.com/pharo-project/pharo/pull/9911 - Align and cleanup two #new methods (AthensCanvas, ClapDocument) with â¦ #9891 https://github.com/pharo-project/pharo/pull/9891 - Reenable FFICallbackTest on Windows #9529 https://github.com/pharo-project/pharo/pull/9529 Documentation ============== - Expand String class comment. #9900 https://github.com/pharo-project/pharo/pull/9900 Pharo 9 ======= - 9038-Windows-edges-grabbing-for-resizing-not-optimal #9917 https://github.com/pharo-project/pharo/pull/9917

1 0

About / and ZnUrl
by stephane ducasse Sept. 5, 2021

Sept. 5, 2021

Hi sven may be you know the answer :) 'http://www.pharo.org/figures/' asUrl / 'documentation/p.png' "http://www.pharo.org/figures/documentation/p.pngâ so far so good. 'http://www.pharo.org/figures/' asUrl / '/documentation/p.png' "http://www.pharo.org/figures//documentation/p.png" Why not having "http://www.pharo.org/documentation/p.pngâ Because /documentation is absolute so the resolution could take that into account. S

2 1

This week (35/2021) on the Pharo Issue Tracker
by Marcus Denker Sept. 3, 2021

Sept. 3, 2021

We merged 26 Pull Requests and closed 15 Issue tracker entries this week. Focus for Pharo10 is still cleaning up unused code. Features ======== - Adding initial iteration of ExternalProjectLoader #9827 https://github.com/pharo-project/pharo/pull/9827 - 9848-Allow-reflective-execution-of-CompiledMethod-without-sending-to-the-receiver #9849 https://github.com/pharo-project/pharo/pull/9849 Fixes ===== - Make printing of BlockClosure more robust #9843 https://github.com/pharo-project/pharo/pull/9843 - 9731-Ph9-Spec2-List-items-cannot-be-selected-when-medium-font-is-used #9852 https://github.com/pharo-project/pharo/pull/9852 Dead code cleanup ================= - Cleanup-deprecated-classify #9837 https://github.com/pharo-project/pharo/pull/9837 - remove-deprecated-code-08-30 #9862 https://github.com/pharo-project/pharo/pull/9862 - Cleanup-Deprecated-Code-09-01 #9876 https://github.com/pharo-project/pharo/pull/9876 - Cleanup-Deprecated-09-02 #9886 https://github.com/pharo-project/pharo/pull/9886 - AthensCairoStrokePaint>>#initialize not necessary #9867 https://github.com/pharo-project/pharo/pull/9867 - Cleanup #isActivePlatform #9865 https://github.com/pharo-project/pharo/pull/9865 - Remove UnixEnvironment>>#unsetEnv: #9875 https://github.com/pharo-project/pharo/pull/9875 - Metaclass>>#sharedPools can be removed #9869 https://github.com/pharo-project/pharo/pull/9869 - 9878-detectSum-is-deprecated-but-still-has-users #9884 https://github.com/pharo-project/pharo/pull/9884 - Cleanup-Deprecated-DisplayMedium #9880 https://github.com/pharo-project/pharo/pull/9880 - Cleanup FileSystemDirectoryEntry #9873 https://github.com/pharo-project/pharo/pull/9873 Cleanups ======== - Simpler-VariableName-ReservedVariable #9841 https://github.com/pharo-project/pharo/pull/9841 - Deprecate-DebuggerMethodMapOpal #9824 https://github.com/pharo-project/pharo/pull/9824 - Unify #layoutForType: with the #kind methods. #9819 https://github.com/pharo-project/pharo/pull/9819 - 9681-AbstractLayout-hierarchy-unify-typeOfClass-and-kind #9861 https://github.com/pharo-project/pharo/pull/9861 - EmbeddedFreeTypeFontInstaller class >> initialize should not do a supâ¦ #9855 https://github.com/pharo-project/pharo/pull/9855 - Cleaning up ValueLink objects #9799 https://github.com/pharo-project/pharo/pull/9799 - categorize-more-09-01 #9881 https://github.com/pharo-project/pharo/pull/9881 Documentation ============== - Expand Dictionary documentation #9834 https://github.com/pharo-project/pharo/pull/9834 - Add EmbeddedFreeTypeFontDescription class comment #9860 https://github.com/pharo-project/pharo/pull/9860 - Fix #9788 : Change parameter from class to string #9842 https://github.com/pharo-project/pharo/pull/9842 Pharo9 ====== - Backport Issue 9731: Ph9-Spec2-List-items-cannot-be-selected-when-medium-font-is-used #9853 https://github.com/pharo-project/pharo/pull/9853

1 0

about URL isAbsolute
by stephane ducasse Aug. 31, 2021

Aug. 31, 2021

Hi Iâm a bit confused. When I use isAbsolute I get 'file:///toto.png' asUrl isAbsolute >>> false 'file://toto.png' asUrl isAbsolute >>> true Now I confused because as Unix / is absolute so file://toto.png <file:///toto.png> would be relative. and /foo is absolute. Are URLs so different than files? Are the results I get correct? I ask this question in the context of Microdown if people write ![caption](file://toto.png). ![caption](figures/toto.png) ![caption](file:///toto.png). S

2 2

This week (34/2021) on the Pharo Issue tracker
by Marcus Denker Aug. 27, 2021

Aug. 27, 2021

We merged 24 pull requests and closed 19 issues this week. The focus right now is cleaning up unused code. The image got already smaller! Immutable Litarals / Literal Sharing ================================== We compile literals as immutable objects already in Pharo9, this is now improved: Literal arrays are now recursively read-only, the compiler preference was removed and we have some first code (not used yet) to share all the equal literals between methods (and literal arrays) so save a little bit of memory. - ReadOnlyLiterals-Remove-Preference #9793 https://github.com/pharo-project/pharo/pull/9793 - RecurseReadOnly-LiteralArray #9815 https://github.com/pharo-project/pharo/pull/9815 - LiteralSharing-NestedArrays #9836 https://github.com/pharo-project/pharo/pull/9836 Cleanups: Remove Dead Code ========================== One Focus of Pharo10 is to remove unused code. The Image got already smaller by around 5MB! This week we removed the old FFI and the old Event handlin code, besides smaller removals. - Removing old Event handling and VM World Renderer #9838 https://github.com/pharo-project/pharo/pull/9838 - Removing old ffi #9831 https://github.com/pharo-project/pharo/pull/9831 - Reduce-duplicated-Methods-2 #9789 https://github.com/pharo-project/pharo/pull/9789 - Refactoring2-Deprecation-Clean #9817 https://github.com/pharo-project/pharo/pull/9817 - DeadCode-Cleanup-08-24 #9816 https://github.com/pharo-project/pharo/pull/9816 - Cleanup-Deprecated-Metacello #9823 https://github.com/pharo-project/pharo/pull/9823 Tests ===== Keeping the CI tests green is work... - Fixing broken tests #9785 https://github.com/pharo-project/pharo/pull/9785 - 9795-Failing-on-CI-ReleaseTesttestNoEquivalentSuperclassMethods #9797 https://github.com/pharo-project/pharo/pull/9797 - Skip-testModifiedReturn #9802 https://github.com/pharo-project/pharo/pull/9802 - Improve testNoUncategorizedMethods #9808 https://github.com/pharo-project/pharo/pull/9808 - upgrading Pharo 10 with Roassal 0.9.9 #9801 https://github.com/pharo-project/pharo/pull/9801 - ReleaseTest-Timeout-Longer #9839 https://github.com/pharo-project/pharo/pull/9839 Cleanups ======== - Use Protocol unclassified whenever possible #9805 https://github.com/pharo-project/pharo/pull/9805 - SystemWindow>>#openInWorldExtent: should be in Deprecated10 package #9810 https://github.com/pharo-project/pharo/pull/9810 - Categorize some more uncategorized methods #9812 https://github.com/pharo-project/pharo/pull/9812 - Fix typos: boostrap -> bootstrap #9814 https://github.com/pharo-project/pharo/pull/9814 - Adding doc #9821 https://github.com/pharo-project/pharo/pull/9821 - Ring2: simplify #mcType and unify with #kind #9820 https://github.com/pharo-project/pharo/pull/9820 Features ======== - Loading documentation reader. #9818 https://github.com/pharo-project/pharo/pull/9818 - Exposing the ABI of a function to the image. #9826 https://github.com/pharo-project/pharo/pull/9826

1 0

Two year engineer or postdoc position on Moose
by stephane ducasse Aug. 27, 2021

Aug. 27, 2021

Hello We have a two year position for an engineer or postdoc position for supporting research activities on top of the Moose open-source platform. The RMOD team is about to transform itself into a new Team called Evref that is a joint team with a part of Berger-Levrault R&D department. Berger-Levrault is the 10th software developer french editor. In the context of the enhancement of the Moose platform, the selected candidate will contribute to one of several of the following topics: - The introduction of the process mechanism in the platform. Indeed, currently, the Moose platform enables the user to build her own metamodels, models, visualisations and so on. However, there is no process mechanism to help more the user in the analysis or the migration using the Moose platform. This work implies for example to define a model of flexible process and an architecture where the developper can easily define her own process from scratch or by adaptation of existing process. - The management of several versions of the same models. Currently, in the Moose platform each version is separated from the others. We have support in previous versions of Moose for example through Orion (ref). This works implies to define how to represent, manipulate and integrate in the Moose platform the management of several versions. It also implies to support the difference between models eventually conforming different metamodels and the evolution from one model to another. - The management of the software system representation through several models conforming different metamodels. All the models represent the same version of the software systems, but from different perspectives. For example, we may have a GUI model, a Database model and a software model. This work implies to be able to specify that a concept in one model is the same in another model. This will then enable us to propose specific analysis explaining how data are used and propagated in the software systems. Or it will also enable us to identify in the code the business concepts and thus to provide a more abstract model. - Decomposition of god classes from their clients. In practice, there exist different types of god classes. The ones that have several responsibilities materialised by a lot of attributes and methods using these attributes. The ones that have several responsibilities materialised by a lot of client classes invoking their classes. We already proposed support to decompose god classes of the first type (ref to ICSME2019). The work here consists to provide support for the second type. It means provide visualisation and possibly a process. There might be eventually other types or classes for which the type is a mixture of these two. It will be necessary to deal with those hybrid classes. - Operationalizable non-functional requirements. Currently, the non-functional requirements (NFR) are used to build a system, but it exists few approaches that enable the developer to identify them from the code by reverse engineering. However, we know that with time, software systems evolve and often without update of the documentation. Thus it is not clear that after time the non-functional requirements are still fulfilled by the software system. This work implies to be able to represent NFR, to support them in the Moose platform and propose NFR aware tools to manipulate the source code. Such tools will include: (1) tools to automatically detect security threats in the source code from software quality issues, (2) tools to support software engineers in understanding NFR (memory consumption, security, efficiency) and (3) tools to transform source code while preserving a NFR (such as security or efficiency). All this work will happen in interaction with Berger-Levrault collaboration. In addition, the possibility to have a permanent research position at the end of this contract with Berger-Levrault is part of the current contract. Salary is competitive and taken from french state grid. S. -------------------------------------------- StÃ©phane Ducasse http://stephane.ducasse.free.fr / http://www.pharo.org 03 59 35 87 52 Assistant: Aurore Dalle FAX 03 59 57 78 50 TEL 03 59 35 86 16 S. Ducasse - Inria 40, avenue Halley, Parc Scientifique de la Haute Borne, BÃ¢t.A, Park Plaza Villeneuve d'Ascq 59650 France

1 0