No Andrew - you miss my point. If I go
<cfset myArray = ArrayNew(1)> in the underlying Java classes of myArray, myArray is actually a java.util.Vector. There is nothing stopping MM to making it a synchronized linked list in the next version of CF, or even implement their own Array Java class. yes - Vector will stay the same, but a CF Array may not stay as being a Vector. That's what I mean by 'not supported' Mark On 7/15/05, Andrew Scott <[EMAIL PROTECTED]> wrote: > Mr SafeFromBees, > > Thanks for the heads up on your history:-) > > However the only way that the underlying java object would change is if sun > made them all private methods, or that you can't inherit another object. So > as long as CF runs in Java bytecode your very safe in this regards, but as > Mr SafeFromBees points out this could change and become a .Net layer in the > future (god no I hope this would never be considered). > > And having said that, if it is to run a BD then forget the java methods now! -- E: [EMAIL PROTECTED] W: www.compoundtheory.com ICQ: 3094740 --- You are currently subscribed to cfaussie as: [email protected] To unsubscribe send a blank email to [EMAIL PROTECTED] Aussie Macromedia Developers: http://lists.daemon.com.au/
