I stumbled upon Unicon because I installed the noweb [1] literate programming system from scratch some time ago. It uses Icon as an (optional) dependency to create cross-references during the weaving process. The fallback is based on Awk, but inferior in features. Anyway, if you have read this far, you should check out noweb and of course (Un)Icon.
Oh silly me who read unicorn language for a long time before getting it…
Icon (and therefore Unicon) is one of my favorite languages. It's remarkable the parallels between Prolog, Icon, jq, and Verse.
Some days ago I tried to install from the PPA repository, but it appears Ubuntu jammy derivatives are not supported yet. Is there a PPA update estimate?
I read Python stole its generators from Icon. Being an enthusiastic user of the itertools module, was curious to see how do generators work on Unicon/Icon.
Check out section 1.8 from this manual: http://www2.cs.uidaho.edu/~jeffery/unicon/ub.pdf#page30
Seems pretty excellent for an old jalopy.
Add XFT support and this language would be cool to have a fast RAD development with easy crosscompilation.
> Add XFT support and this language would be cool to have a fast RAD development with easy crosscompilation.
What is "XFT support" in this context?
LLM code gen, presumably
The poster wrote “RAD development”, which implies highly visual development environments for making client side apps eg for desktop , mobile, or web. Xft is a library that draws text and graphics. That’s what I thought the poster referred to because in the article the text rendering is pretty poor. Addressing font rendering is critical to get perfect for a RAD / visual development tool.
So I also think the poster’s statement is ambiguous.
No. TTF/OTF support for widgets.
I assume you meant to write "XTF" (where X=T or O) not "XFT" then.
Although even then, using XTF as an abbreviation for TTF/OTF is highly nonstandard. Those four extra characters greatly increase the likelihood that you'll be understood
XFT it's the tecnology from X11 which allows antialiased fonts among FreeType. Add that support and you'll magically have proper fonts (and full Unicode ones) instead of the old, aliased, locale bound ones.
You confuse people when you write it as XFT, when the correct capitalisation is Xft: https://en.wikipedia.org/wiki/Xft
Also, you said:
> Add XFT support and this language would be cool to have a fast RAD development with easy crosscompilation.
Xft only works on X11, whereas "easy crosscompilation" suggests an interest in supporting multiple platforms, which normally includes platforms that don't use X11 (macOS, iOS, Android, Windows, even Linux with Wayland)