Someone noted that my last post sounded like I would not fix bugs. I will go back and fix bugs in the virtual machine and extension code if_ someone finds them, but I am quite confident there are none. I know that sounds overconfident, but I have done plenty of testing to weed out the problems. Because Copper is a simple language, there are not many ways to trip up the virtual machine. Ironically, it does mean odd code is acceptable. You could even feed this_ entire blog post into the VM and it would all be legal code. Go ahead and try it.
As of one week, support for Copper has completely ended. Some time ago, I declared an end to the updates some time ago, but now I won’t be updating this blog anymore (unless I hand over the blog to someone else). But before you think that’s a bad thing…
It’s an exciting day for Copper. Three new built-in functions have been added to give the user even more power:
Each of these enhances the power of the type system in Copper by enabling greater abstraction in data flow.
Good news! CupricBridge and Curri are now online! CupricBridge is a wrapper for the Irrlicht engine GUI system, but it also provides a serialization interface implementation that will work with scene objects. Curri is a project containing the boilerplate code for creating applications with Copper, CupricBridge, and Irrlicht engine.