One other suggestion that might work - create a category for your methods right on FloatArray. Put them in a category *projectname. You should probably read up on PackageInfo to understand how naming conventions work.
http://beta4.com/squeak/aubergines/docs/packageinfo.html
On May 10, 2006, at 1:38 PM, Charles D Hixson wrote:
David Shaffer wrote:
C...
Again, I'd suggest an adapter class if you want to preserve the API of your C++ classes in your Smalltalk code.
Hope this helps...
David
Well, that's where I want to start. Presumably in the course of the translation I'll get a better idea of what the thing is doing, and possibly then I'll refactor. (I started off using the adaptor pattern, but as it started getting messy, I thought I ought to check and ascertain that this was, indeed, the correct approach. While writing to ask about it was really the first time I had thought that subclassing might be the best approach.)
Beginners mailing list Beginners@lists.squeakfoundation.org http://lists.squeakfoundation.org/mailman/listinfo/beginners