https://github.com/moosetechnology/famix

An abstract representation of source code. Famix is generic and can describe applications in multiple programming languages.
https://github.com/moosetechnology/famix

meta-model moose pharo smalltalk

Last synced: about 1 month ago
JSON representation

An abstract representation of source code. Famix is generic and can describe applications in multiple programming languages.

• Host: GitHub
• URL: https://github.com/moosetechnology/famix
• Owner: moosetechnology
• License: mit
• Created: 2020-05-27T11:48:31.000Z (over 4 years ago)
• Default Branch: development
• Last Pushed: 2024-11-07T10:38:04.000Z (about 2 months ago)
• Last Synced: 2024-11-07T11:33:23.620Z (about 2 months ago)
• Topics: meta-model, moose, pharo, smalltalk
• Language: Smalltalk
• Homepage:
• Size: 13 MB
• Stars: 13
• Watchers: 14
• Forks: 23
• Open Issues: 138
• Metadata Files:
  • Readme: README.md
  • License: LICENSE

Awesome Lists containing this project

README

        
# Famix

Famix is an abstract representation of source code. It is generic and can describe applications in multiple programming languages.

  - [Installation](#installation)

  - [Documentation](#documentation)

  - [Version management](#version-management)

## Installation

To install the project on your Pharo image, execute the following script: 

```Smalltalk

Metacello new

  baseline: 'Famix';

  repository: 'github://moosetechnology/Famix:development/src';

  onConflict: [ :ex | ex allow ];

  load.

```

To add the project to your baseline:

```Smalltalk

spec

	baseline: 'Famix'

	with: [ spec repository: 'github://moosetechnology/Famix:development/src' ]

```

Note you can replace the #master by another branch such as #development or a tag such as #v1.0.0, #v1.? or #v1.2.? .

## Documentation

Check out the [Moose wiki](https://modularmoose.org/moose-wiki/).

## Version management 

This project use semantic versioning to define the releases. This means that each stable release of the project will be assigned a version number of the form `vX.Y.Z`. 

- **X** defines the major version number

- **Y** defines the minor version number 

- **Z** defines the patch version number

When a release contains only bug fixes, the patch number increases. When the release contains new features that are backward compatible, the minor version increases. When the release contains breaking changes, the major version increases. 

Thus, it should be safe to depend on a fixed major version and moving minor version of this project.