If you're referring to Quigibo's code,
    X<<0?0->X
is the same thing as
    if X<<0
    0->x

Question, how does the line routine speed compares to the built-in Axe one?

Well, that's a good question...It hasn't been written yet, so I can't answer it

There has been talk that if a clipped line routine is developed, Axe would use that one and this axiom might instead implement a non-clipped line routine for people who want the extra speed and don't need clipping.

Some form of curves, I'm not sure syntactically how the function would be called, would be nice. Also, being able to do everything on multiple buffers would be really nice.

All commands will have variable buffer arguments.

This has been in the works for a few weeks now, so I thought I'd make a thread about it.

I began writing this Axiom with a fixed-memory flood fill routine, but I failed miserably. I finally convinced jacobly to give it a try. Together we completely optimized the algorithm and he was able to write an awesomely optimized version. Then I started working on a filled circle algorithm, which jacobly volunteered to convert to Axiom format for me, but a few *cough* bugs were found. He has since been working with me to fix those bugs. All-in-all, this is basically an Axiom by both jacobly and myself.

This Axiom will be a collection of more advanced graphics routines which we hope will be greatly useful for graphics programs, and potentially games as well. Some of the routines will definitely NOT be useful for games, due to speed issues.

Currently written:

• Fixed-Memory Flood Fill (needs optimization)

"Fixed-memory" means there is no risk for stack overflow AT ALL. However, the routine is subsequently very slow, so it will not be suitable for games or anything that needs fast dynamic area filling. It would be fine for a "paint bucket" tool in most on-calc graphics programs though. This will *hopefully* support grayscale filling as well.

• Filled Circles (aaalmost done)

Fully clipped filled circle routine with variable buffer and variable fill type (on/off/invert) using numerical arguments.

Kinda sorta planned:

• Vertical/Horizontal Line Segments (on/off/invert)
• Clipped Lines (on/off/invert)
• Rectangles (on/off/invert)
• Rectangle outlines (on/off/invert)
• Ellipses?

Any other suggestions for what this axiom could have?

Well I can tell you that clipped lines is on Quigibo's to-do list (I have it right here ). So I figure if you/jacobly creates a pretty nice line clipping method, Quigibo would probably be happy to include it in Axe. And the people who have been bugging him for native clipped lines (myself included) would be happy as well.

EDIT: One thing you could make in an Axiom is an alternate routine, possibly without clipping, that's optimized to be faster.

Hmm...Good idea. Have an optimized line routine that will never clip, and have the clipped one in Axe. Sounds like a good idea to me.

Line clipping support!

This is going to be coming in an Axiom that is under development.

This seems to be quite out of date and lacking a lot of great possible articles, though :\