I have added #ObjectIcon and #ATS --
https://rosettacode.org/wiki/Bernstein_basis_polynomials#ATS

#ATSlang #FunctionalProgramming

Addendum: Others have been adding examples, too, so far in languages with which I am unfamiliar.

Bernstein basis polynomials

The n + 1 {\displaystyle n + 1} Bernstein basis polynomials of degree n...

Rosetta Code

Anti-aliased straight line drawing, implemented in #ObjectIcon (using the drawing of individual pixels, rather than cheating):

Xiaolin Wu's line algorithm - Rosetta Code https://rosettacode.org/wiki/Xiaolin_Wu's_line_algorithm#ObjectIcon

#RosettaCode

(I discovered (a) that ‘variable’ does what Parlett documented, even though it is different from what ‘variable’ does in Icon; (b) there are major bugs in ipl.math(ExtMath). I have marked them ‘SEVERE BUG’ in my issues tracker. Easy to fix, but not today.)

Xiaolin Wu's line algorithm

Task Implement the Xiaolin Wu's line algorithm described in Wikipedia. This algorithm draws anti-aliased lines. Related task See Bresenham's line algorithm...

Rosetta Code
Euler method

Euler's method numerically approximates solutions of first-order ordinary differential equations (ODEs) with a given initial value. It is an explicit method for...

Rosetta Code

I hope that so far I have AT LEAST done enough to prevent #ObjectIcon disappearing into nowhere.

Now I have to go mention the new repo on #RosettaCode. I’ll just make a handwritten note, for now.

Of course, any RC contributor can make the changes. But one shouldn’t give the impression I plan to be a ‘maintainer’. I’m an older, disabled person simply providing the thing in the most forkable way.

(Were it my own project, it would surely be in a Mercurial archive, not Git.)

Come get your #ObjectIcon sources, people! A #programming #language you probably do not yet know: https://github.com/chemoelectric/objecticon

Easier to learn if you already know #Icon or #Unicon. Also if you know #Prolog or #Mercury, which are other languages that have goal-directed evaluation (which which are declarative, whereas the Icon family are procedural).

(Please fork rather than expect support, though. I am an elderly disabled person.)

GitHub - chemoelectric/objecticon: Object Icon, beginning from a migration to Git of the Subversion at https://sourceforge.net/p/objecticon/code/ For the original, use branch objecticon-last-svn-commit

Object Icon, beginning from a migration to Git of the Subversion at https://sourceforge.net/p/objecticon/code/ For the original, use branch objecticon-last-svn-commit - chemoelectric/objecticon

GitHub

#ObjectIcon is one of those compilers that installs an executable as intermediate code with a shebang header that runs the intermediate code interpreter. So oipatch is something to rewrite the shebang header to point to a different location for the interpreter.

With that, you can do a staged install.

As it current comes (but perhaps not after I make changes, if I get to doing that), Object Icon is meant to be run where you built it. To me, that’s not acceptable.

Here is how I decided to work monotonic cubic splining (for color gradients) straight into the #ATS program:

chemoelectric / mandelbrot-viewer / [d4995d] /pchip2c.icn.m4 https://sourceforge.net/p/chemoelectric/mandelbrot-viewer/ci/default/tree/pchip2c.icn.m4

That is an #Icon/#Unicon program (or #ObjectIcon, depending on #m4 settings). What it does is take the output of passing the original PCHIP (not any of the derivatives) through f2c and make it buildable without f2c.h or libf2c.

Then I simply link the #ATS with that C code.

chemoelectric / mandelbrot-viewer / [d4995d] /pchip2c.icn.m4

A snapshot from #SeahorseValley of the #MandelbrotSet, in the #ObjectIcon program I am writing for #RosettaCode.
A portion of the #MandelbrotSet as drawn by an #ObjectIcon program I am working on for #RosettaCode.