The code I sent you had some more steps in it that the code that failed with the pop error. I've just PM'ed you the code that produces the 'pop' error (a subset of the first code piece I sent you). Regarding using types smaller than int - that's my mistake - ints are just fine.I just looked at your code. I'm not getting the same 'pop' error you are getting, and I'm not sure why.... did you send me exactly the code you were using? In any case, I am getting a couple of other errors that touch on areas I didn't implement (namely, unsigned types, and types smaller than int). I took a bunch of shortcuts there, just to get things working.
Of course that's OK with me.I was hoping to do a quick hack tonight but I'm getting pretty tired. I think I'd like to take another look this weekend if that's OK with you. It would be quite exciting if I could get this prototype to produce correct code for the routine you wrote.
You are absolutely right about this and this is also how I intend to do it. The code I sent you was just the first steps towards having it all run natively.By the way, I'm a little worried about whether this is going to be effective. I'm pretty confident that I can (eventually) produce code for the routine you sent me, but I'm very worried that the interop overhead (going from managed to native) is going to dwarf any savings you get by doing these several math operations in native code. Now on the other hand, if you had a whole array of CrossScale[] Value1[] and Value2[]s to work on (so that you only made one managed-to-native transition but then worked on a whole array of parameters), I'm pretty confident that there would be substantial performance improvement.
This project you have done here is just what I need to complete my project and keep me on the netduino platform. And I would very much like to stay on the netduino platform. I have some realtime code that runs way way to slow on netduino and therefore need it to run natively. So I really appreciate what you have done here and if I can help in any way let me know.Regarding more than one method in the class, yeah, I was thinking about that. It helps a lot that you're interested in this project--after doing the initial prototype I kind of moved on to other things because, although people seem to like this idea in principle, I wasn't sure anyone was actually going to use my particular prototype in practice.
Cheers,
-Fabien.
