A dynamic OO language with ideas traditionally described as "functional"
 
 
 
 
 
Go to file
Lucas Dohmen e8cf021256 Update docs 2023-07-18 16:35:42 +02:00
bin First version of the lexer 2018-02-02 19:13:34 +01:00
docs Update docs 2023-07-18 16:35:42 +02:00
examples Introduce a custom error for unknown messages 2019-03-04 22:06:19 +01:00
exe Better error display including position of the error 2019-03-04 22:45:06 +01:00
lib Release 0.10.0 2019-03-17 17:23:37 +01:00
test Better error message for re-assigning a class 2019-03-17 17:16:10 +01:00
.editorconfig First version of the lexer 2018-02-02 19:13:34 +01:00
.gitignore First version of the lexer 2018-02-02 19:13:34 +01:00
.travis.yml Travis 2019-03-17 17:37:42 +01:00
CODE_OF_CONDUCT.md First version of the lexer 2018-02-02 19:13:34 +01:00
Dockerfile Add a "simple" Dockerfile 2018-02-12 01:42:56 +01:00
Gemfile First version of the lexer 2018-02-02 19:13:34 +01:00
Gemfile.lock Release 0.10.0 2019-03-17 17:23:37 +01:00
LICENSE.txt First version of the lexer 2018-02-02 19:13:34 +01:00
README.md Fix Logo on Codeberg 2023-06-29 14:53:14 +02:00
Rakefile Rename Lexer to Tokenizer 2019-03-03 13:58:21 +01:00
halunke.gemspec Ignore "warning: mismatched indentations" for generated files 2019-03-04 22:00:59 +01:00

README.md

Halunke

Halunke

Halunke is a dynamic, object-oriented language that has a simple grammar inspired by Smalltalk and Lisp. It is created to show that interesting characteristics traditionally described as "functional" make sense in an object-oriented language:

  • Separation of identity and data (but not data and behavior)
  • Immutability and persistent data structures
  • Isolation of Side-Effects
  • Pattern matching

It also has the following characteristics:

  • There is no null/nil value in the language
  • Playing close attention to error message design

Find out more on the documentation page.

License

The project is available as open source under the terms of the MIT License.

Code of Conduct

Everyone interacting in the Halunke projects codebases, issue trackers, chat rooms and mailing lists is expected to follow the code of conduct.