Amigo programming language

[paxscript]

Hello All,

I have released my new product:

www.amigo-lang.com

Amigo is a new general-purpose, object-oriented, statically typed, high-level programming language. The main target of use is solving AI problems. It has simple C-like syntax, powerful capabilities for data representation and processing, and efficient memory management.

The key features of Amigo are:

- The core of the language is very small. It includes simple data types (int, string, double, etc.) and first-class functions.
- Amigo has a single compound data type—the tuple. Despite this, it provides powerful tools for creating, modifying, and manipulating any dynamic data structures: lists, trees, queues, etc. At the same time, the garbage collector is not used.
- Amigo introduces an extended concept of function. It allows introducing all OOP features without borrowing additional concepts. Such concepts as classes, objects, arrays, enums, ranges, interfaces, etc., are derived from the concepts of function and closure. In other words, we can consider OOP concepts as just a syntax sugar in relation to the Amigo core.
- Amigo has powerful macros. Any Amigo program can be used as a macro because Amigo macros are made in the language itself. You can debug macros in the same IDE.

Other features and concepts supported by Amigo are:

- Generic types
- Operator overloading
- Coroutines, generators, and fibers
- Continuations
- Bunches of functions
- Delegates
- Linq
- Destructuring and pattern matching
- Object literals and anonymous classes
- Modules (units of compilation)

Amigo interpreter is written in Delphi from scratch. The source code is compatible with FPC/Lazarus. IDE code uses TSynEdit component. I'm planning to release AmigoScripter soon.

Thanks.

A.

[maurog]

Oh WOW, I’ve always been a fan of PaxScript.
I used PaxScript in a CAM project as a runtime scripter.
(With PaxScripter, I created post-processors for CNC machines at runtime.)
Below is a screenshot showing PaxScripter/PaxDebugger + CADSys42-2D  in action.

Do you plan to port the legendary PaxScripter to Lazarus at some point?

Thanks for sharing,

Best regards,
Maurog.

[fireboxsoft]

Bro, you're amazing! I've been using PaxCompiler and paxScript for many years, of course, with the Pascal language. But later on, the PaxCompiler website was acquired, and I'm looking forward to a version that supports Pascal and is compatible with the Lazarus development tool.
大哥，你太厉害了！我好多年前就在使用PaxCompiler以及paxScript，当然，使用的是pascal语言。但后来paxCompiler网站被收购了，期待支持pascal语言以及支持lazarus开发工具的版本。

[paxscript]

Thank you!

I'm working on AmigoBasic and AmigoPascal interpreters now (they are using the same Amigo runner), so AmigoScripter and Amigo IDE will support 3 languages.

A.

[maurog]

These are great news. Thank you.

[my_only_lonely]

Thank you!

I'm working on AmigoBasic and AmigoPascal interpreters now (they are using the same Amigo runner), so AmigoScripter and Amigo IDE will support 3 languages.

A.

Does Amigo support compiling to machine code just like PaxCompiler, or it is a interpreter only language?

[paxscript]

Amigo compiler generates a bytecode that is interpreted with Amigo VM.

A.

[my_only_lonely]

Amigo compiler generates a bytecode that is interpreted with Amigo VM.

A.

That is a pity. The reason why I bought PaxCompiler and not using free PascalScript is the performance.
I'm using it on some server side performance-sensitive logic. It would be excellent if it could support compiled machine code.
Would you at least consider adding JIT support? As far as I know, DWScript is also interpreted, but it supports JIT.

[440bx]

Amigo interpreter is written in Delphi from scratch. The source code is compatible with FPC/Lazarus.

Just curious, do you intend to eventually make the source available ?

[paxscript]

That is a pity. The reason why I bought PaxCompiler and not using free PascalScript is the performance.
I'm using it on some server side performance-sensitive logic. It would be excellent if it could support compiled machine code.
Would you at least consider adding JIT support? As far as I know, DWScript is also interpreted, but it supports JIT.


Yes, it would be good, but it is not the nearest target. The main direction is flexibility.

AmigoScripter will support 3 languages, and it will be available for all platforms supported by Delphi. All languages will include such traits as coroutines, continuations, LINQ, the actor model, macros, and cross-language programming. Support of classes comes from first-class functions and closures ( www.amigo-lang.com/genesis_classes.htm ); support of data structures is based on processing of tuples (the single built-in data type in Amigo VM) and generics. For example, a Pascal-like array can be represented as class RangedArray<R, T>. This is flexible, but it will require bytecode optimization.

A.

[paxscript]

Just curious, do you intend to eventually make the source available ?

I'm going to sell licenses on the full source code of the scripter. It should allow me to continue development.

A.

[my_only_lonely]

I'm a bit curious since Pascal syntax is not supported yet.
Does it supports all Delphi data types? For example Delphi has Integer, SmallInt, ShortInt, Int64, Byte, Word, Cardinal.
It might be important if we want to migrate from PaxCompiler to the Amigo. DWScript only support Int64 for Integer values.

[paxscript]

I'm a bit curious since Pascal syntax is not supported yet.
Does it supports all Delphi data types? For example Delphi has Integer, SmallInt, ShortInt, Int64, Byte, Word, Cardinal.
It might be important if we want to migrate from PaxCompiler to the Amigo. DWScript only support Int64 for Integer values.

Yes, Amigo VM supports all primary .Net types. AmigoPascal will support all compound Delphi/FPC types (enums, sets, records, classes, arrays, etc.), and all these types will be derived from the Amigo kernel in a unified way.

A.

[my_only_lonely]

That is great! I know JIT or compiled machine code is not the nearest target. But is it on the roadmap?
For example LuaJIT is more porpular than the original Lua on the server side usage.

[paxscript]

That is great! I know JIT or compiled machine code is not the nearest target. But is it on the roadmap?
For example LuaJIT is more porpular than the original Lua on the server side usage

Yes, JIT is the road map. I have to make deep bytecode optimization to prepare it.