- Pharo-dev - lists.pharo.org

This week (05/2022) on the Pharo Issue Tracker
by Marcus Denker Feb. 4, 2022

Feb. 4, 2022

We merged 15 PRs and closed 31 Issues. Fixes ===== - Increasing minimum size for Calypso browser #10838 https://github.com/pharo-project/pharo/pull/10838 - Add back beautifulcomments #10832 https://github.com/pharo-project/pharo/pull/10832 - 10800-Broken-FT2-library-setting #10851 https://github.com/pharo-project/pharo/pull/10851 Breakpoint interaction ====================== - Breakpoint position from cursor #10812 https://github.com/pharo-project/pharo/pull/10812 - Inserting variable breakpoint when the selected node is variable https://github.com/pharo-project/pharo/pull/10841 Cleanup ======= - Remove Class>>isAbstract as it actually call the super class method #10825 https://github.com/pharo-project/pharo/pull/10825 - Remove Spec1 Critic Browser #10816 https://github.com/pharo-project/pharo/pull/10816 - Remove Spec1 #10818 https://github.com/pharo-project/pharo/pull/10818 - Cleanup-unsent-Deprecated90 #10833 https://github.com/pharo-project/pharo/pull/10833 - fix-users-canBeGlobalVarInitial #10820 https://github.com/pharo-project/pharo/pull/10820 - Cleanup : remove Class>>isValidTraitName. No more sender of it in theâ¦ #10826 https://github.com/pharo-project/pharo/pull/10826 - Replace Moose algos graphs by AI graphs algorithms #10839 https://github.com/pharo-project/pharo/pull/10839 - Integrate Roassal3 v0.9.9e #10846 https://github.com/pharo-project/pharo/pull/10846 Comments ======== - 10214 improving comments and adding tests to tree searcher #10636 https://github.com/pharo-project/pharo/pull/10636 - 10214 improving comments and adding tests to tree searcher #10817 https://github.com/pharo-project/pharo/pull/10817

1 0

PharoDays'22: Inscriptions are open!
by Guillermo Polito Feb. 1, 2022

Feb. 1, 2022

-------------------------------------------------------------------------------- Pharo Days March 3rd and 4th, Lille, France https://days.pharo.org/ <https://days.pharo.org/> ââââââââââââââââââââââââââââââââââââââââ Inscriptions are open! Do not miss the opportunity to meet the Pharo programming environment and its community! PharoDays is a unique event where you can meet other Pharoers, discover latest advances, and share your experience. Hand-ons sessions are there to help you getting started on advance topics. Follow the "Show us your project" sessions to get immersed in Pharo lively community. This year, PharoDays is a mix of technical talks and hand-ons. Come to join business chat and enjoy friendly atmosphere and discuss with experts. Check the tentative schedule: from building command line interfaces to web applications, through modern desktop applications, visualisations, debugging and even a live music performance! See you in march!

1 0

FFI help with *** pointers to get font family list
by Stewart MacLean Jan. 31, 2022

Jan. 31, 2022

Hi, I'm trying to figure out how to implement code to retrieve a list of font families using the Pango libraries. The key function definition is: https://docs.gtk.org/Pango/method.FontMap.list_families.html void pango_font_map_list_families ( PangoFontMap* fontmap, PangoFontFamily*** families, int* n_families ) I've found some C code, which is shown below. The tricky bit is the ***. I've managed to get this working in VisualWorks (code also below), but can't figure out how to do this using the Pharo FFI. I've managed to get the basic Pango functionality going, but I can't figure out how to use ExternalAddress to do this. Running on a MacMini M1. Any pointers (:)) appreciated! Thanks, Stew C Version ---------------- #include <glib.h> #include <pango/pangocairo.h> static void list_fonts () { int i; PangoFontFamily ** families; int n_families; PangoFontMap * fontmap; fontmap = pango_cairo_font_map_get_default(); pango_font_map_list_families (fontmap, & families, & n_families); printf ("There are %d families\n", n_families); for (i = 0; i < n_families; i++) { PangoFontFamily * family = families[i]; const char * family_name; family_name = pango_font_family_get_name (family); printf ("Family %d: %s\n", i, family_name); } g_free (families); } int main (int argc, char ** argv) { list_fonts (); return 0; } ================================= VisualWorks Version --------------------------- availableFamilyNames " Transcript clear. (FontFamily availableFamilyNames asSortedCollection: [: a : b | a < b]) do: [: each | Transcript cr; show: each]. NamedFontSelector open " "08/09/20 SIM. Modified to work on 64bit. Clues obtained from: XSurface class >>displaySurface: DisplaySurface>>cairoVisual PDFSurface class>>versions" | listPointer sizePointer ffPointers result | ObjectMemory is64Bit ifTrue: [listPointer := CIntegerType unsignedLongLong gcMalloc. sizePointer := listPointer sizeof gcCopyToHeap] ifFalse: [listPointer := 0 gcCopyToHeap. sizePointer := 0 gcCopyToHeap]. LibPango default pango_font_map_list_families: LibPango default pango_cairo_font_map_get_default with: listPointer with: sizePointer. ffPointers := (ObjectMemory is64Bit ifTrue: [CIntegerType unsignedLongLong] ifFalse: [ CIntegerType unsignedInt]) newPointerToAddress: listPointer contents. result := OrderedCollection new: sizePointer contents. sizePointer contents timesRepeat: [result add: (LibPango default pango_font_family_get_name: ffPointers contents) utf8. ffPointers += 1]. LibPango default g_free: listPointer contents. ^result

2 3

ZTimestamp now has nanosecond precision
by Sven Van Caekenberghe Jan. 31, 2022

Jan. 31, 2022

Hi, Last year, I extended ZTimestamp with a default nanosecond precision (it previously had whole second precision). This makes it a more complete replacement for DateAndTime. https://github.com/svenvc/ztimestamp https://github.com/svenvc/ztimestamp/commit/de6c5a670ed0c6cb18894b4917383dd… The goals of ZTimestamp are to be simpler and more efficient (both faster and more compact). A ZTimestamp instance occupies half the space of a DateAndTime instance, its two slots being SmallIntegers. Back in the 32-bit days, the seconds since midnight field was too small for nanoseconds. Now, 64-bit is the default and there is enough room and no speed penalty for working with nanoseconds since midnight. In casual use, you won't see much of a difference, apart from the added detail: ZTimestamp now. "2022-01-27T09:21:20.528695Z" There are ways to convert to the older precision: ZTimestamp now truncated. ZTimestamp now rounded. ZTimestamp nowTruncated. Obviously, other methods and classes now support this added precision (like ZTimestampFormat). If you load or depend on tag/release v25 you get the latest version before this major change. If you encounter any problems please let me know. Sven

2 3

This week (04/2022) on the Pharo Issue Tracker
by Marcus Denker Jan. 28, 2022

Jan. 28, 2022

We merged 23 PRs and closed 24 Issue Tracker entries Fixes ===== - Fix 10741: Adding an unknown SharedPool and canceling the proposed choice brings a debugger #10808 https://github.com/pharo-project/pharo/pull/10808 - 10695-CmdBrowse-raise-a-DNU #10775 https://github.com/pharo-project/pharo/pull/10775 - Rename "Hier" to "Hierarchy" in scopes of refactoring #10778 https://github.com/pharo-project/pharo/pull/10796 - Fix #10698: Misleading Calypso warning when defining new instance variables #10806 https://github.com/pharo-project/pharo/pull/10806 - Fix #7952: Decompiler raises Error For methods from Traits on class side #10807 https://github.com/pharo-project/pharo/pull/10807 - Fix #8630: fix allInstVarNames for Traits with State #10811 https://github.com/pharo-project/pharo/pull/10811 Spec2 ===== - 10721-Porting-ExternalBrowser-to-Spec2-and-remove-Spec1-version #10776 https://github.com/pharo-project/pharo/pull/10776 - 10722-Porting-ChangesBrowser-to-Spec2-and-remove-Spec1-version #10786 https://github.com/pharo-project/pharo/pull/10786 - Load Spec2-Transformations package after Refactoring-Core is loaded #10789 https://github.com/pharo-project/pharo/pull/10789 - spec2 auto-rewrites #10791 https://github.com/pharo-project/pharo/pull/10791 - commit spec rewrites 2 #10792 https://github.com/pharo-project/pharo/pull/10792 - Rename defaultSpec to defaultLayout #10793 https://github.com/pharo-project/pharo/pull/10793 - Move Dependency Analyzer to Spec2 #10813 https://github.com/pharo-project/pharo/pull/10813 Cleanup ======= - testNoUncategorizedMethods-false-positives #10785 https://github.com/pharo-project/pharo/pull/10785 - AST-Tag-Abstract-classes #10783 https://github.com/pharo-project/pharo/pull/10783 - chore: Define baseline of TaskIt for Pharo 10 #10799 https://github.com/pharo-project/pharo/pull/10799 - Using "adding-removing" instead of "adding/removing" #10622 https://github.com/pharo-project/pharo/pull/10622 - Cleanup-canBeExecutedInContext #10784 https://github.com/pharo-project/pharo/pull/10784 - NewValueHolder extracted to its own baseline #10763 https://github.com/pharo-project/pharo/pull/10763 - Updated Fuel to 3.0.4 #10513 https://github.com/pharo-project/pharo/pull/10513 - Cleanup-gtInspectorAllVariablesIn #10809 https://github.com/pharo-project/pharo/pull/10809

1 0

This week (03/2022) on the Pharo Issue Tracker MD
by Marcus Denker Jan. 21, 2022

Jan. 21, 2022

We merged 22 PRs and closed 22 Issues this week. Bug Fixes ========= - Fixes #10702 Printing method selector in windows title only if the selector is not nil #10713 https://github.com/pharo-project/pharo/pull/10713 - CmdCommand-isAbstract-check #10770 https://github.com/pharo-project/pharo/pull/10770 - Skip-testSNIPage #10771 https://github.com/pharo-project/pharo/pull/10771 - TFFI not compatible to UFFI - missing #tfPointerAddress on Integer #10738 https://github.com/pharo-project/pharo/pull/10738 - Enh/better expansion for non fluid #10759 https://github.com/pharo-project/pharo/pull/10759 - Fixes #10747 adding a shortcut to expand class definition. Thanks Denis. #10757 https://github.com/pharo-project/pharo/pull/10757 - Fixes #10253 adding new fetcher for selectors. #10717 https://github.com/pharo-project/pharo/pull/10717 - Use double click on the left bar to install a breakpoint in the browser #10736 https://github.com/pharo-project/pharo/pull/10736 Spec2 ===== - 10721-Porting-ExternalBrowser-to-Spec2-and-remove-Spec1-version #10776 https://github.com/pharo-project/pharo/pull/10776 - Move FontChooser to NewTools #10709 https://github.com/pharo-project/pharo/pull/10709 - 10720-Porting-WatchesWindow-to-Spec2-and-remove-Spec1-version #10761 https://github.com/pharo-project/pharo/pull/10761 - 10719-Porting-TestReviver-to-Spec2-and-remove-Spec1-version #10762 https://github.com/pharo-project/pharo/pull/10762 Cleanups ======== - Fix-DeprecationRewrites #10772 https://github.com/pharo-project/pharo/pull/10772 - Cleanup newlines and blanks in "Random" packages #10743 https://github.com/pharo-project/pharo/pull/10743 - Cleanup newlines and blanks in "Refactoring" packages #10745 https://github.com/pharo-project/pharo/pull/10745 - Cleanup newlines and blanks in "ReflectionMirrors" packages #10751 https://github.com/pharo-project/pharo/pull/10751 - 10730 Update comments kernel wrt responsibilities/behavior #10728 https://github.com/pharo-project/pharo/pull/10728 - Cleanup newlines and blanks in "Reflectivity" packages #10753 https://github.com/pharo-project/pharo/pull/10753 - Cleanup newlines and blanks in "Regex" packages #10755 https://github.com/pharo-project/pharo/pull/10755 - Do not use deprecated method in ClyNotebookPageMorph>>#initialize #10749 https://github.com/pharo-project/pharo/pull/10749 - Remove temporarily documentation reader #10734 https://github.com/pharo-project/pharo/pull/10734 Pharo 9 ======= - Backport Fix #10253 Adding new fetcher for selectors. #10718 https://github.com/pharo-project/pharo/pull/10718

1 0

This week (02/2022) on the Pharo Issue Tracker
by Marcus Denker Jan. 17, 2022

Jan. 17, 2022

For more infos, see https://github.com/pharo-project/pharo/pulse Fixes ===== - MC Warning - Add #versions Getter #10696 https://github.com/pharo-project/pharo/pull/10696 - Fixes #10702 Printing method selector in windows title only if the selector is not nil #10713 https://github.com/pharo-project/pharo/pull/10713 - Integrate Roassal3 v0.9.9d #10716 https://github.com/pharo-project/pharo/pull/10716 - 10703-Collectionflattened-changed-semantics #10705 https://github.com/pharo-project/pharo/pull/10705 - 10678-Step-Over-fails-for-leaving-simple-accessors #10707 https://github.com/pharo-project/pharo/pull/10707 - Fixes #10673 by adding missing method method to display a MessageTally identified #10682 https://github.com/pharo-project/pharo/pull/10682 - use DoubleByteLayout and DoubleWordLayout #9792 https://github.com/pharo-project/pharo/pull/9792 Image Building ============== - align commit of external projects with its merged version #10697 https://github.com/pharo-project/pharo/pull/10697 - Updating bootstrap image to v1.7.8 #10694 https://github.com/pharo-project/pharo/pull/10694 Cleanup ======= - Fix-deprecated-hostWindowTitle #10711 https://github.com/pharo-project/pharo/pull/10711 - 10331-No-need-to-refer-to-transcript-in-executable-comments #10706 https://github.com/pharo-project/pharo/pull/10706 Comments ======== - fixes #10704. changed Random>>nextInt: to nextInteger: in class comments #10710 https://github.com/pharo-project/pharo/pull/10710

1 0

Re: Helping with documentation
by stephane ducasse Jan. 14, 2022

Jan. 14, 2022

> On 12 Jan 2022, at 02:03, Jimmie Houchin <jlhouchin(a)gmail.com> wrote: > > I am going to be working my way through some Pharo docs. > > As I read the books I sometimes see some English that can be improved. Yes I noticed it too but Iâm running too fast and my english is not my native language so it is not good. > > What is the proper procedure for doing so? > > Any pointers to documents to help with this greatly appreciated. Oh this is easy just send small PRs and I will read and integrate them. Thanks in advance because this is important to get better documentation. S > > > Thanks. > > > Jimmie

2 2

Pharo VM Release - v9.0.11
by tesonep＠gmail.com Jan. 13, 2022

Jan. 13, 2022

Hello, I have released a new version of the Pharo VM for Pharo 9 and Pharo 10. This VM is accessible right now from Zero-Conf, updating it in the Pharo Launcher or using the usual downloads (as described in pharo.org/download) This version includes a series of minor bug fixes. Changelog: - Include FloatArrayPlugin in the build - Updating SDL2 to 2.0.18 for OSX X86_64 - Using Pharo 10 image as VMMaker image - Fixing issue in message counting on non-JIT VM Thanks a lot, and any doubt please let me know. Cheers, Pablo on behalf of the whole Pharo team. -- Pablo Tesone. tesonep(a)gmail.com

2 1

Array sum. is very slow
by Jimmie Houchin Jan. 12, 2022

Jan. 12, 2022

I have written a micro benchmark which stresses a language in areas which are crucial to my application. I have written this micro benchmark in Pharo, Crystal, Nim, Python, PicoLisp, C, C++, Java and Julia. On my i7 laptop Julia completes it in about 1 minute and 15 seconds, amazing magic they have done. Crystal and Nim do it in about 5 minutes. Python in about 25 minutes. Pharo takes over 2 hours. :( In my benchmarks if I comment out the sum and average of the array. It completes in 3.5 seconds. And when I sum the array it gives the correct results. So I can verify its validity. To illustrate below is some sample code of what I am doing. I iterate over the array and do calculations on each value of the array and update the array and sum and average at each value simple to stress array access and sum and average. 28800 is simply derived from time series one minute values for 5 days, 4 weeks. randarray := Array new: 28800. 1 to: randarray size do: [ :i | randarray at: i put: Number random ]. randarrayttr := [ 1 to: randarray size do: [ :i | "other calculations here." randarray sum. randarray average ]] timeToRun. randarrayttr. "0:00:00:36.135" I do 2 loops with 100 iterations each. randarrayttr * 200. "0:02:00:27" I learned early on in this adventure when dealing with compiled languages that if you donât do a lot, the test may not last long enough to give any times. Pharo is my preference. But this is an awful big gap in performance. When doing backtesting this is huge. Does my backtest take minutes, hours or days? I am not a computer scientist nor expert in Pharo or Smalltalk. So I do not know if there is anything which can improve this. However I have played around with several experiments of my #sum: method. This implementation reduces the time on the above randarray in half. sum: col | sum | sum := 0. 1 to: col size do: [ :i | Â Â Â Â sum := sum + (col at: i) ]. ^ sum randarrayttr2 := [ 1 to: randarray size do: [ :i | "other calculations here." Â Â Â ltsa sum: randarray. ltsa sum: randarray ]] timeToRun. randarrayttr2. "0:00:00:18.563" And this one reduces it a little more. sum10: col | sum | sum := 0. 1 to: ((col size quo: 10) * 10) by: 10 do: [ :i | Â Â Â Â sum := sum + (col at: i) + (col at: (i + 1)) + (col at: (i + 2)) + (col at: (i + 3)) + (col at: (i + 4)) Â Â Â Â Â Â Â Â + (col at: (i + 5)) + (col at: (i + 6)) + (col at: (i + 7)) + (col at: (i + 8)) + (col at: (i + 9))]. ((col size quo: 10) * 10 + 1) to: col size do: [ :i | Â Â Â Â sum := sum + (col at: i)]. ^ sum randarrayttr3 := [ 1 to: randarray size do: [ :i | "other calculations here." Â Â Â ltsa sum10: randarray. ltsa sum10: randarray ]] timeToRun. randarrayttr3. "0:00:00:14.592" It closes the gap with plain Python3 no numpy. But that is a pretty low standard. Any ideas, thoughts, wisdom, directions to pursue. Thanks Jimmie

14 30