chrisblutz/trinity-legacy

The legacy version of the Trinity Programming Language [archived]

This is the legacy version of the Trinity interpreter. The new, updated version can be found here.

---

Trinity is a dynamically-typed, object-oriented programming language. It is heavily influenced by aspects of Java and Ruby.

Repository Structure

• bin - Batch/Shell scripts
• lib - Trinity standard library
• logo - PNG/SVG logos for Trinity
• src - Java source code for the Trinity interpreter
• test - Trinity unit tests (written in Trinity)

Copyright

Copyright © 2017 Christopher Lutz. See LICENSE for further details.

trinity-legacy's Issues

Array.removeObject does not remove objects as expected

Array.removeObject should be made to operate similar to Map's methods, where the equality of values is checked using Trinity's == method rather than Java's checker. This method might even be de-nativized to provide the best solution:

def removeObject(value)
    for i = 0; i < length(); i += 1
        if this[i] == value
            remove(i)
            i -= 1

ExpressionInterpreter falsely report items inside block definitions |x| as being "on the first level"

Take the following code sample:

method() |i = 2 + 2|
    ...

In this sample, the + inside the block definition (vertical bars), is reported as being "on the first level", and is used as a division point when parsing. In the eyes of the parser, the parts of the statement look like this: method() |i = 2, +, and 2|.

The expected functionality would be to treat these definitions as a separate entity, excluded from any parsing on the first pass. If this was the case, the example would be treated as a single method call with an attached block. Only when the arguments for that block are parsed would the + be used to split statements.

Scope not saved on reflective method invocation

Take the following sample:

module TestModule
    class Test
        def static main(args)
            Test.class.getMethod('main').invoke(nil, [])

This should start an infinite recursion loop. However, it throws this error:

Trinity.Errors.MethodNotFoundError: No method 'Test' found in 'Method'.
  at TestModule.Test.main in file 'test.ty' at line 4
  at Method.invoke (native)
  at Class.getMethod (native)
  at TestModule.Test.main in file 'test.ty' at line 4
  at native method '<init>'

When the method is called the second time, its scope is different and no longer contains the correct information. This may require a move from Procedure.call to Class.tyInvoke.

Return/Break statements inside blocks passed to methods do not work as expected

return and break statements inside of blocks passed to methods should allow programmers to act on them. return statements should cause the surrounding method to return the specified value. break statements might be able to set a variable in the block that could be retrieved using block.isBroken().