Ecosyste.ms: Awesome

An open API service indexing awesome lists of open source software.

https://github.com/hogoww/PlainPharoCode

Last synced: 2 months ago
JSON representation

Host: GitHub
URL: https://github.com/hogoww/PlainPharoCode
Owner: hogoww
License: gpl-3.0
Created: 2019-04-30T14:49:02.000Z (about 5 years ago)
Default Branch: master
Last Pushed: 2023-01-15T09:20:03.000Z (over 1 year ago)
Last Synced: 2024-03-24T13:20:27.841Z (3 months ago)
Language: Smalltalk
Size: 4.26 MB
Stars: 4
Watchers: 2
Forks: 1
Open Issues: 9
Metadata Files:
- Readme: README.md
- License: LICENSE

Lists

awesome-pharo - PlainPharoCode - Instead of using String, use Pharo code to define code to generate. (Code generation)

README

        # PlainCode

[![Build Status](https://travis-ci.com/hogoww/PlainPharoCode.svg?branch=master)](https://travis-ci.com/hogoww/PlainPharoCode)

[![License](https://img.shields.io/badge/license-GPL-blue.svg)](LICENSE)

[![Pharo version](https://img.shields.io/badge/Pharo-7.0-%23aac9ff.svg)](https://pharo.org/download)

[![Pharo version](https://img.shields.io/badge/Pharo-8.0-%23aac9ff.svg)](https://pharo.org/download)

Able to generate methods using the pharo syntax in a block rather than strings, or complex node writting.  The variables used in the environment will be replaced by their values if they are set. You can also pass a dictionary to rename the arguments of the nodes.

Two main hooks with the same behavior are available for now:

PlainCodeVisitor >>> generateCode: aSelector withBody: aBlock \[ andArguments: aDictionary\]

BlockClosure >>> asMethod: aSelector withArguments: aDictionary

(see examples bellow)

There's a representative example of the syntax we're constrained with:

![Simple Example](./images/exRepresentatif.png)

/!\ Uses the context the block has been defined in, meaning that you cannot create the target block in another block that will be valued in another context. Use #ifTrue:ifFalse and variants if you need control flow (they are inlined at compilation time, so no context change).  

We also (sadly) have to stringify the AST rather than giving it directly to the compiler, because the replacement are pretty rudimentary, and don't analyze a lot of things (such as replaced values that are instance variables of the targeted class).

Unit tests show some more small examples. Here's some bigger ones from another project.

![Simple Example](./images/ex1.png)

![Example #2](./images/ex2.png)

![Example #3](./images/ex3.png)

A bit more information is available in this [mailing list thread](https://lists.pharo.org/empathy/thread/55WTZMWMU5OPG7JUCXUGBZKSJRQYE55X?hash=EMWJVUBPHDFOAIAMSJSHCP5IHHMAYH3I#EMWJVUBPHDFOAIAMSJSHCP5IHHMAYH3I) and the [small related presentation](https://github.com/hogoww/PlainPharoCode/blob/master/documentation/PlainPharoCode.pdf).