>> Using a dynamic array of byte will not slow down the component if >> the array size is not constanly changed. > > And if the Move function is used to move data around, specifically when > the project uses the FastMove unit which has very efficient move code.
That's not a problem. The code can be conditionaly compiled to use move or fastmove. The problem is to have a class interface which is the same on both platforms so that an application code can be the same. > Mind Move uses pointers, so might be useless in .net, but that's a > problem for people wanting to use .net, not win32. Indeed. Because .NET doesn't accept pointer, the code is frequently slower. But again, this is not important and do not compromize win32 code. I restate it: the code inside the class can be changed using conditional compile, but not the class interface, specially the event handlers signature which mess all the forms. I'm trying to have the best portable code to easily maintain a single set of components and samples. Take ICS for Kylix: the code has not been updated with all the changes in win32 code because it is different code. It is simply too time consuming to maintain both sets of source code. -- Contribute to the SSL Effort. Visit http://www.overbyte.be/eng/ssl.html -- [EMAIL PROTECTED] http://www.overbyte.be -- To unsubscribe or change your settings for TWSocket mailing list please goto http://www.elists.org/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
