Its guiding principles are

• Simplicity and readability
• Minimal: there ought to be one way to write something
• Striving for orthogonality
• Programs are about transforming data into other forms of data
  • Code is about expressing algorithms—not the type system
• There is embedded knowledge and wisdom in older programming languages
• The entire language specification should be possible to be memorized by a mere mortal

Its featre are features (in no particular order):

• Full UTF-8 Support
• Custom allocators that are simple to use:
  • Memory arenas/regions, pools, stacks, etc. which can be easily added
• Context system for allocations, logging, and thread data
• Built-in types and procedures that take advantage of the context system:
  • new(type), and make use the context’s allocator (unless explicitly given)
  • Dynamic arrays and hash maps ([dynamic]int and map[string]int)
• Array programming
  • a, b: [4]f32; c := a * b
  • i := a.x * b.y
  • v := swizzle(a, 1, 2, 0)
• Explicit procedure overloading
• Introspection on all types
• High control over memory layout
  • Alignment
  • Field offsets
  • Endianness
  • Data sizes
• Endian specific integer types (useful for specific data formats)
  • u32le
  • u64be
• Decent package system and file handling
• No bad preprocessor
• Type inference
  • x: int = 1
  • x := 1 // x is deduced to be an int
• using
  • making everything a namespace (similar to Pascal’s with but on steroids)
  • Ability to have subtype polymorphism
• Multiple return values
• Clean, consistent, and fast to parse syntax
• No need for procedure prototypes
• defer statements
  • defer a statement until the end of scope (akin to D’s scope(exit))
• Nested procedures and types
• Tagged unions and untagged unions
• Ranged for loops
• Labelled branches
  • break label_name
• break by default in switch statements
  • Explicit fallthrough
• “Raw” strings
  • x := `what "the" string?`
• cstring for legacy use
• Parametric polymorphism (“generics”)
• Foreign system
• Compile time when statements
• Bounds checking which is togglable at the statement level:
  • #no_bounds_check #bounds_check
• i128 and u128 support

And lots more!

This is definitively something that I would like to Eiffelize!

I simply had to let Bertrand Meyer, father of Eiffel know it. The easiest way I found is throught X (once known as Twitter):

Dear professor @Bertrand_Meyer, I’m sure you have been informed of https://eiffel-community.github.io Isn’t their name picking choise a little confusing, to say the least?

I also left the same message as a comment on his blog.

I know the name space of project looks almost exausted but coudln’t they conceive another name?

In addition to C, there is Nim, V, Rust…. that’s very sad

Well… wow!

Haxe – The Cross-platform Toolkit

Haxe is an open source toolkit based on a modern, high level, strictly typed programming language.

All those “open source” have the same targets that Eiffel had 30-40 years ago… this for example already have commercial, hefty “Support Plans”, starting from an yearly rate of 6000€ (six thousand euros).

One thing I think they got right is that Haxe allows you to compile for several targets:

• JavaScript
• C++
• C#
• Java
• JVM
• Lua
• PHP 7
• Python 3
• HashLink
• NekoVM
• Flash (SWF Bytecode)
• And its own interpreter

Liberty has C, and once had JVM. Ideally I wish to “resurrect” the JVM and add PHP (yes) and Python, or at least improve the interoperability with those languages.

Textual is a TUI framework for Python, inspired by modern web development.

Textual is a Rapid Application Development framework for Python, built by Textualize.io.

Build sophisticated user interfaces with a simple Python API. Run your apps in the terminal or a web browser!

Well, I just wish I could have it in EIffel….

twin: ANY– Return a new object with the dynamic type of Current.

copy (other: ANY) — Update current object using fields of object attached to other, so as to yield equal objects.

Too bad that those Eiffel features, (function members) available in each and every object and variable are not available in Kotlin.

Ok, yet another #GUI library.

Of course I hope they’ll be successful, but I wonder why they had to start another one.

I’ll keep an eye on it, it may be useful in the case we make LibertyEiffel interfacable with Rust