So I’m still working on bug #1065, the only real progress that I’ve made is to find out that what I have done so far is definitely not the right answer. After spending time chatting on IRC, it seems the right answer is not so obvious. One solution that I’ve been working on involves changing the Char constructor to accept a number. Currently it only accepts a string with a length that is equal to one. Everything else is created with the value “NaN”. This may solve another bug, p5 allows a user to create a Char from a number. The char is then printed as the charcter of that value. I can get similiar functionality by changing Char.ValueOf() to return a string from the char code. Now Char will hold a int but when it is called, it will return a string of the char. This creates problems though and breaks 5 tests. I’ll submit my change to the Char constructor to see what peole think. Then go from there. This bug has become a example of how sometimes there is no right solution to a problem. Sometimes theres only a less wrong answer.
