Emojicode Versions Save

🥁 Yet another update:

• Fixes a bug related to the use of callables as generic arguments. (#116)

The awesomest release yet. 😊

🍃🍂 It appears it’s update season. 0.6.2 fixes some serious bugs:

• 🍇 Fixes a linker bug that could occur if closures were used in imported packages.
• 🖍 The compiler did not correctly determine mutability of 🐕 in value types.
• 🖍 Fixes a compiler bug that could lead to a crash or incorrect results when determining variable mutability.

It‘s just gonna be awesomely awesome. 😊

👋 It’s time for an update. This update:

• 🦢🦒🥶 Adds support for Unicode 11 emojis.
• 🏞 Improves memory flow analysis.
• 💣 Fixes a compiler crash that occurred with file paths shorter than seven characters.
• ⁉️ Fixes a bug that allowed incorrect callable calls.
• 🐞 Fixes a bug related to generics.

This should make awesome even more awesome. 😊

🎉 Proudly announcing an all-new, all-better version of Emojicode.

What has changed:

• Improved syntax. A lot has changed. We can’t list everything here, please check out the documentation. Here are some highlights:
  • Infix operators! 4 ➕ 3 ✖️ 2 evaluates to 4 + 3 times 2 = 10
  • Revamped method syntax. Methods are now defined with ❗️ or ❓.
  • 🆕 for initialization.
  • ➡️ 🖍🆕 Variable assignment and declaration has changed.
  • 🚂 and 🚀 have been renamed to 🔢 and 💯 respectively.
  • Single-line comments now begin with 💭. Multiline comments are delimited by 💭🔜 Bah 🔚💭
  • Type methods are called differently now.
  • The default namespace is 🏠 now.
  • Fruits no longer affect flow control. New if (↪️) and return syntax (↩️).
  • Documentation comments are now wrapped in 📗 and package documentation is wrapped into 📘.
  • Generic syntax is slightly different.
• The compiler has been re-written and now uses LLVM to compile to native binaries, which means huge performance gains.
• Error reporting is a lot better, with more exact positions and messages and better overall resilience.
• The package ecosystem has changed: Packages are now simpler to create and the compiler now searches multiple locations that can be easily configured and extended.
• Great interoperability improvements: The new C++ API is much simpler.
• Emojicode now manages memory with reference counting and can eliminate heap allocations.
• The JSON API was removed and will be re-added in an upcoming version.
• All package has been rewritten in large parts and extended, too. (🍨 & 🍯 are now implemented in Emojicode, for instance.)

It is awesome, you have to give it a try. 😊

Our documentation and installation instructions are — as always — located at https://www.emojicode.org.

If you discover a bug or have feedback, we will be glad to hear from you.

👋 Hey!

It’s time to announce the second beta release of Emojicode 0.6 (Symphonic). Here’s what changed from the last beta:

• Casting
• Improved interoperability
• Added a basic migration assistant

It’s even greater than last time, you have to give it a try. 😊

Known issues:

• Calling protocol methods on certain values of a generic type cannot be compiled.
• Casting with generics and casting from protocol types does not work as expected.
• Memory management is not available.

If you discover a bug or have feedback, we will be glad to hear from you.

👋 Hey!

Nice you're here to check out the first beta release of Emojicode 0.6. Here’s what changed from the alpha:

• Implements missing interfaces (e.g. 🍯)
• Automatic Ownership Management
• Updated Generic Syntax (#107)
• Type parsing and analysis has been decoupled – no more circular dependencies
• Lots of bugs fixes and other minor changes and improvements.

It’s even greater, you have to give it a try. 😊

Known issues:

• Calling protocol methods on certain values of a generic type cannot be compiled.
• Casting is not available yet.
• Memory management is not available yet. Programs leak memory.
• Extensions might not work as expected.

If you discover a bug or have feedback, we will be glad to hear from you.

👋 Hi there!

This is Emojicode Symphonic alpha. The first pre-release of a truly great Emojicode.

Here are some of the amazing changes:

• Improved syntax. A lot has changed. And it’s a lot better.
• Emojicode compiles to native binaries using LLVM. Optimization. Speed. Interoperability. (Say goodbye to the complicated package API.)
• The compiler has been rewritten and is much more stable and handles errors more gracefully (and more beautifully).
• Many, many bugs and borderline cases have been fixed.
• New APIs.

It’s so great, you have to give it a try. 😊

It’s an alpha version, though. The following things will not work for sure:

• Calling protocol methods on generic type values will cause a crash.
• Multiprotocols and Casting are not available.
• The garbage collector is not available. Programs will leak memory.
• Not all APIs are available.
• Extensions might not work as expected.

If you discover a bug or have feedback, we will be glad to hear from you.

Notably, this update

• brings support for all Unicode 10 emojis (v5.0). 🤩🤪🤯🧝‍♀️🦒
• fixes a bug that caused the compiler to emit an error when a comment was the last token in a source code file. (#102)
• deprecates 🌶. (#92)
• deprecates the addition of instance variables in extensions.
• adds a new initializer 👂🏼 and the 👄 method to 🔡.

This update fixes several memory-related bugs:

• 🐛 A compiler bug that could affect captured variable values to not be retained.
• 🐛 A compiler bug that could occur if a closure was optimized to not capture 🐕.
• 🐛 A run-time bug that could cause a crash for closures without captured variables.
• 🐛 A run-time bug that could cause captured variables to contain improper values.
• 🐛 A compiler bug that could cause the Garbage Collector to incorrectly treat values as object references.

If you have any questions, comments, feedback, suggestions or whatever you come up with, open an issue or follow Emojicode’s Twitter account now.

Have fun using world’s only programming language that's bursting with emojis!

This minor update

• 🐛 fixes a bug that caused ranges to behave faulty. (#87)
• ⚠️ changes the compiler to disallow the use of value type meta types. Obtaining such meta type instances does not serve any purpose but generates bytecode with undefined behavior.
• ⚠️ changes the compiler to forbid the capturing of value type methods. This can lead to undefined behavior too, if the value type is stored in a variable that goes out of scope while the callable is retained. If you were using this feature, change your code to use plain closures (🍇🍉).

If you have any questions, comments, feedback, suggestions or whatever you come up with, open an issue or follow Emojicode’s Twitter account now.

Have fun using world’s only programming language that's bursting with emojis!