Every single macOS download I've tried of Eul has been completely broken. It simply won't launch. Doing so from the Terminal gives the following output: dyld: Library not loaded: libnanovg.a Referenced from: /Applications/eul.app/Contents/MacOS/./eul Reason: image not found Weirdly, `otool -L eul` tells me that eul links against no dynamic libraries whatsoever (not even libSystem) and `otool -l eul` backs this up. I'…
Eul – The language
11–20 of 33 posts
Re: Eul – The language
#12> functions are pure.
I think you need to reconsider what pure means
Re: Eul – The language
#13Normally I think "rewrite it in Rust!" comments are annoying, but in this case the author's requirements sound pretty relevant: - integration with C libraries - overhead similar to C - more productive than C - "Variables are immutable by default, globals are not allowed, functions are pure." That does sound an awful lot like Rust, at least if we kind of squint our eyes at the purity requirement :) I wonder if the ori…
Re: Eul – The language
#14Cool little language, but > functions are pure. I think you need to reconsider what pure means
Re: Eul – The language
#15Eul: fn
Come on, it should be "fun".
Re: Eul – The language
#16Normally I think "rewrite it in Rust!" comments are annoying, but in this case the author's requirements sound pretty relevant: - integration with C libraries - overhead similar to C - more productive than C - "Variables are immutable by default, globals are not allowed, functions are pure." That does sound an awful lot like Rust, at least if we kind of squint our eyes at the purity requirement :) I wonder if the ori…
On the other hand, Rust definitely does not have "Fast compilation", and although debatable, I would say that "Simplicity" is not one of Rusts many virtues.
True, though several people are now working on compiler performance.
> and although debatable, I would say that "Simplicity" is not one of Rusts many virtues.
I've found that Rust seems as simple as it can be given the problem it's solving. For instance, lifetimes and borrow checking aren't trivial, but I have a hard time thinking of a simpler abstraction that has the same safety and performance properties.
Another way to look at it: C is "simpler", in some ways, but it pushes the corresponding complexity into the heads of developers and the code of helper/wrapper libraries and tools.
Re: Eul – The language
#17Go: func Eul: fn Come on, it should be "fun".
Re: Eul – The language
#18Normally I think "rewrite it in Rust!" comments are annoying, but in this case the author's requirements sound pretty relevant: - integration with C libraries - overhead similar to C - more productive than C - "Variables are immutable by default, globals are not allowed, functions are pure." That does sound an awful lot like Rust, at least if we kind of squint our eyes at the purity requirement :) I wonder if the ori…
- Variables aren't immutable by default, but neither are they mutable by default.
- Globals are discouraged.
- Nim compiles to C so integration with C libraries is easy and overhead is also similar to C.
- Productivity is subjective but I'd say it's significantly more productive than C.
- Despite going through a C compiler the compilation is still incredibly fast.
Re: Eul – The language
#19Normally I think "rewrite it in Rust!" comments are annoying, but in this case the author's requirements sound pretty relevant: - integration with C libraries - overhead similar to C - more productive than C - "Variables are immutable by default, globals are not allowed, functions are pure." That does sound an awful lot like Rust, at least if we kind of squint our eyes at the purity requirement :) I wonder if the ori…
Since we're suggesting alternatives already I would like to throw Nim into the mix. - Variables aren't immutable by default, but neither are they mutable by default. - Globals are discouraged. - Nim compiles to C so integration with C libraries is easy and overhead is also similar to C. - Productivity is subjective but I'd say it's significantly more productive than C. - Despite going through a C compiler the compila…
-`const` for declaring immutables, `var` for mutables, do what you want.
-Use globals if you want, or don't.
-Can directly import C headers, generally no need to write bindings.
-Personally I've found it significantly more productive
-Compiles fast, but lets be fair, people only bring this up because C++ and Rust are the outliers here by compiling so slowly.
Other noteworthy features:
-Standard library is completely optional.
-No default allocator.
-Comptime functionality instead of macros.