Well done, Jon!

-Pete

On 4/22/20 11:43 AM, Jon Wolfe via TriEmbed wrote:

 

Also, since you’re defining the array at global scope, the size of it must be a compile time const-_expression_ anyways, so you wouldn’t even need dynamic memory allocation.

 

Vec3<unsigned char> framebuffer[imageWidth * imageHeight];

 

would work., instead of using new. That also has the advantage that the linker will more easily catch size overruns.

 

 

 

From: Jon Wolfe via TriEmbed
Sent: Wednesday, April 22, 2020 11:36 AM
To: Jon Wolfe via TriEmbed
Subject: Re: [TriEmbed] TriEmbed Digest, Vol 83, Issue 15

 

 

I just realized something I’d overlooked.

 

Your for loop *is* unexpected in your example, it’s outside of any function.

 

I just fired up the Arduino and tried my example template code (with the for loop inside of Setup) , and it worked for me.

 


_______________________________________________
Triangle, NC Embedded Computing mailing list

To post message: [email protected]
List info: http://mail.triembed.org/mailman/listinfo/triembed_triembed.org
TriEmbed web site: http://TriEmbed.org
To unsubscribe, click link and send a blank message: 
mailto:[email protected]?subject=unsubscribe

Reply via email to