Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Skip to content

Botffy/XPLanG

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Gittens

Code Climate Test Coverage Codeship

The PLanG programming language is an educational programming language used at the Faculty of Information Technology of the Péter Pázmány Catholic University, Hungary, for teaching the very basics of programming in the first semester. The language and the small IDE/interpreter accompanying it was designed and implemented by László Lövei in the summer of 2005, based on a pseudocode language used earlier to describe algorithms on paper. A Pascal-like language, its main distinguishing feature is that its keywords are in Hungarian.

It's a small language: while it's Turing-complete (of course), it lacks subroutines, records, user-defined types, and it doesn't even have elsif.

XPLanG (eXtended PLanG) is an extended version of that language. Having taken a course in compiler construction at ELTE, I chose extending PLanG as the topic for my self-directed laboratory project, then I chose to continue the project for my BSc thesis. The first release candidate is due to be released at the beginning of November 2019.

The dream lives on.

Running

Prerequisites

You will need Java 8 Runtime Environment (or later). Just install the latest JRE from Oracle's download page.

Download

The latest release is available here on Github, while the latest build can be downloaded from the homepage.

Command line

Start the XPLanG interpreter by running bin/XPLanG (Unix-like systems) or bin/XPLanG.bat (Windows).

Usage

XPLanG [options] SOURCE_FILE

SOURCE_FIE should be a PLanG program.

Valid options:

  • --dry-run Perform a dry run: parse and analyse the source, displaying any errors, but do not interpret it.
  • --print-ast Print the Abstract Syntax Tree after parsing the program
  • --dump-memory Dump the contents of the memory to the StdOut after running the program
  • --source-encoding the encoding of the source code (UTF8 or LATIN1)
  • --output-encoding The encoding of the standard output (UTF8 or LATIN1). When not set, the system default will be used.
  • --help display usage information and exit
  • --version display version information and exit

Editor

XPLanG comes with its own small editor/IDE. Start the XPLanG Editor by running bin/XPLanG-editor (Unix-like systems) or bin/XPLanG-editor.bat (Windows). When starting from the command line, you can specify a single file as an argument, that file will be opened in the editor.

Building

Prerequisites

You will need

Make sure to have these in your PATH, then restart your terminal.

Getting the source code

To get the source code, type git clone https://github.com/Botffy/XPLanG.git in your terminal, in the directory where you'd like your copy of the repo to be created.

Building in the command line

  • gradle classes downloads all dependencies and compiles the whole thing.
  • gradle assemble creates the actual product. The distribution packages are put in the build/distributions.
  • gradle test runs the JUnit tests.
  • gradle javadoc generates the Javadoc documentation, putting it in docs/javadoc.
  • gradle check invokes Checkstyle in addition to running the tests.
  • gradle jacoco invokes the JaCoCo code coverage tool.
  • gradle run runs the interpreter. Pass arguements to XPLanG via Gradle through the -PappArgs command line argument as a list of strings. Try gradle run -PappArgs="['examples/guessing_game.plang']".
  • gradle runGui starts the editor GUI. Specify the file to be opened on startup by using the -PappArgs argument.

You can find the build reports in build/reports.