Pharo

Pharo

Pharo is an open source, cross-platform implementation of the classic Smalltalk-80 programming language and runtime.[3] It is based on the OpenSmalltalk virtual machine called Cog (VM), [4][5][6][7]:16 which evaluates a dynamic, reflective, and object-oriented programming language with a syntax closely resembling Smalltalk-80.

Quick Facts Paradigm, Developer ...

Pharo is shipped with source code compiled into a system image that contains all software necessary to run Pharo.[7]:16 Like the original Smalltalk-80, Pharo provides several live programming features such as immediate object manipulation, live updates, and just-in-time compilation. The image includes an IDE-like software to modify its components.

Pharo was forked from Squeak v3.9 in March of 2008.[8][3][7][7]:10[9]

Overview

Pharo is a pure object-oriented dynamically typed and reflective language. The stated goal of Pharo is to revisit Smalltalk design and enhance it.

The name Pharo comes from the French word "phare" (French pronunciation: [faʁ]) which means lighthouse. This is why the Pharo logo shows a drawing of a lighthouse inside the final letter O of the name.

Key features

Virtual machine

  • Multiplatform virtual machine with JIT, combined generational garbage collector, ephemerons, forwarders
  • Fast object enumeration
  • Easy call stack manipulation
  • AST metalinks
  • Relatively low memory consumption
  • Customizable compiler
  • Optional complete object memory persistence
  • Resumable exceptions
  • Fast object serialization

Built-in software

Language features

  • Simple syntax
  • Object-oriented programming
  • Immediate object identity swapping
  • Dynamic inheritance
  • Objects as methods
  • Optional Green threads
  • Customizable metaclasses
  • Easy to use proxy objects

Relation to Smalltalk

Pharo is based on general concepts of Smalltalk but seeks to improve on them so does not limit itself to them. The basic syntax of the language has a close resemblance to Smalltalk. However, the way classes are defined in Pharo differs from other Smalltalk dialects.[how?]

Language syntax

Pharo syntax postcard

The Pharo syntax is based on Smalltalk-80 language syntax with several extensions. Some of these are common among modern Smalltalk dialects.

  • literals for dynamic arrays. The expressions that specify the array content are evaluated in time of the program execution
{1. 2. 1+2}
  • literals for byte arrays that can be composed only of integer numbers in the range from 0 to 255
#[1 2 3 4]
  • literals for scaled decimals, a representation of fixed point decimal numbers able to accurately represent decimal fractions
3.14s2
  • pragmas. In Smalltalk-80 the pragmas are used only for primitive methods. In Pharo they are fully capable method annotations
<gtInspectorPresentationOrder: 30>
  • two double quotes inside a comment are interpreted as a single double quotes character that is part of the content of the comment

The Pharo language syntax is supposed to be very simple and minimalistic. The basic language elements are often presented on a single postcard as a showcase for the language's brevity. The grammar is classified as LL(1).

The language grammar does not specify directly how the code should be stored in files. Pharo uses Tonel as the preferred code serialization format.

History

Pharo emerged as a fork of Squeak, an open-source Smalltalk environment created by the Smalltalk-80 team (Dan Ingalls and Alan Kay). Pharo was created by S. Ducasse and M. Denker in March 2008. It focuses on modern software engineering and development techniques.[citation needed] Pharo is supported by the Pharo consortium (for legal entities) and the Pharo association for physical persons .


More information Version, Release date ...


Use of Pharo

Companies and consultants

Some companies use Pharo for their development projects.[23] In particular, they use:

  • Seaside for dynamic web development[24]
  • Zinc for server architectures[25]
  • Moose[26] to analyse data and software from all programming languages
  • Graphic libraries for evolved user interfaces
  • Roassal to visualize data[27]

The Pharo consortium[28] was created for companies wishing to support the Pharo project. The Pharo association[29] was created in 2011[30] for users wishing to support the project.

Performance and virtual machine (VM)

Pharo relies on a virtual machine that is written almost entirely in Smalltalk itself. Beginning in 2008, a new virtual machine (Cog) for Squeak, Pharo and Newspeak has been developed that has a level of performance close to the fastest Smalltalk virtual machine.[31] In 2014/2015 the VM community is working on Spur, a new Memory Manager for Cog that should again increase performance and provide better 64-bit VM support.[32]

See also


References

  1. Error: Unable to display the reference properly. See the documentation for details.
  2. Pharo by example. Andrew P. Black, Stéphane Ducasse, Oscar Nierstrasz, Damien Pollet, Damien Cassou, Marcus Denker. [Kehrsatz] Switzerland. October 28, 2009. ISBN 978-3-9523341-4-0. OCLC 957555627.{{cite book}}: CS1 maint: location missing publisher (link) CS1 maint: others (link)
  3. "OpenSmalltalk". opensmalltalk.org. Retrieved November 24, 2021.
  4. OpenSmalltalk/opensmalltalk-vm, OpenSmalltalk, November 23, 2021, retrieved November 24, 2021
  5. "Cog Blog :: About Cog". Retrieved November 24, 2021.
  6. Black, Andrew P.; Ducasse, Stéphane; Nierstrasz, Oscar; Pollet, Damien (October 28, 2009). Pharo by Example. Samuel Morello. ISBN 978-3-9523341-4-0.
  7. "DevelopOnTheWeb". developontheweb.co.uk. Retrieved November 24, 2021.
  8. "The Rise and Fall of Commercial Smalltalk". www.wirfs-brock.com. Retrieved November 24, 2021.
  9. "Pharo got 10 years". Pharo-project.org. Retrieved May 31, 2018.
  10. "Pharo Open Source Smalltalk — Release 1.4". Pharo-project.org. April 17, 2012. Retrieved April 5, 2013.
  11. "Pharo Open Source Smalltalk — Release 2.0". Pharo-project.org. March 18, 2013. Retrieved April 5, 2013.
  12. "Pharo Open Source Smalltalk — Release 3.0". pharo.org. April 30, 2014. Archived from the original on August 23, 2017. Retrieved May 1, 2014.
  13. "Pharo Open Source Smalltalk — Release 4.0". pharo.org. April 15, 2015. Archived from the original on August 23, 2017. Retrieved April 16, 2015.
  14. "Pharo Open Source Smalltalk — Release 5.0". pharo.org. May 12, 2016. Archived from the original on December 29, 2017. Retrieved May 13, 2016.
  15. "Pharo Open Source Smalltalk - Release 6.0". pharo.org. June 6, 2017. Archived from the original on November 20, 2017. Retrieved June 6, 2017.
  16. "Pharo 6.1 released". pharo.org. July 24, 2017. Archived from the original on August 20, 2017. Retrieved August 11, 2017.
  17. "Pharo 7.0 released". pharo.org. January 22, 2019. Archived from the original on February 12, 2022. Retrieved January 22, 2019.
  18. "Pharo 8.0 Released!". pharo.org. January 20, 2020. Archived from the original on February 12, 2022. Retrieved January 20, 2020.
  19. "Pharo 9.0 Released!". pharo.org. July 15, 2021.
  20. "Pharo 10.0 Released!". pharo.org. April 5, 2022.
  21. "Pharo 11.0 Released!". pharo.org. May 11, 2023.
  22. "Home". seaside.st. March 18, 2007. Retrieved April 5, 2013.
  23. "Zinc HTTP Components". Zn.stfx.eu. Retrieved April 5, 2013.
  24. Girba, Tudor. "Home". Moose technology. Retrieved April 5, 2013.
  25. "Agile Visualization". Object Profile. Retrieved May 31, 2018.
  26. "web: Pharo Consortium". Consortium.pharo.org. March 31, 2013. Retrieved April 5, 2013.
  27. Ducasse, Stephane. "association: Pharo Association". Association.pharo.org. Retrieved April 5, 2013.
  28. "Annonce JOAFE n°1025 de la parution n°20110013 du 26 mars 2011". Journal-officiel.gouv.fr. Retrieved May 1, 2022.
  29. "Cog Blog". Mirandabanda.org. Retrieved April 5, 2013.
  30. "7-point summary of the Spur memory manager". Clément Béra. Retrieved April 17, 2015.

Share this article:

This article uses material from the Wikipedia article Pharo, and is written by contributors. Text is available under a CC BY-SA 4.0 International License; additional terms may apply. Images, videos and audio are available under their respective licenses.