Re: "undefined behavior"?

On 6/14/2024 4:44 AM, Ben Bacarisse wrote:
[...]

Which is why I thought you might be including images in the notion of
"holding rgba values".

Fwiw, I remember doing a channel based hit map that stored an image using RGBA but used floats. Each pixel would have a hit:
struct hit
{
     float m_color[4];
};
It would take all of the hits and depending on what was going on during iteration it would increment parts of hit::m_color[4]. The sum of all of the colors would be the total hits. Fwiw, here is an example of one of my results from a trig based bifurcation iterated function system I developed. There is actually some pseudo code in the description:
https://youtu.be/XKhS_nklCkE
Notice the white colors? Those are high density points that create the "main" connections in the bifurcation. Here is my pseudo code that has allowed others to recreate it:
______________
A highly experimental #iterated function system of mine that creates many #fractal #bifurcation diagrams locked in the unit square. Afaict, the animation makes it appear as if everything is rotating around a cylinder. Here is my #IFS that was used to create this animation:
______________
// px_mutation interpolates from -4...4 across each frame; 1440 here.
render frames:
_________
// angle interpolates from 0...pi2 across iterations
// px = py = 0
// Iteration:
px = sin(angle * px_mutation);
py = cos(angle * py);
______________
Plot every pixel in the ifs. Actually, I am adding color to each pixel visited during iteration.
______________
It was fun to create! :^)