Comments on: Actionscript Vector class initialization with a source Array http://www.daveoncode.com/2009/04/06/actionscript-vector-class-initialization-with-a-source-array/ coder and technology lover Sat, 24 Jul 2010 20:37:14 +0000 hourly 1 http://wordpress.org/?v=3.0 By: Gary Paluk http://www.daveoncode.com/2009/04/06/actionscript-vector-class-initialization-with-a-source-array/comment-page-1/#comment-4436 Gary Paluk Sun, 03 Jan 2010 21:36:50 +0000 http://www.daveoncode.com/?p=367#comment-4436 Please note, the type declairations were stripped out of the example code given above. The first example was cast as String and the second example were cast as uint. Gary Paluk aka RipX Please note, the type declairations were stripped out of the example code given above. The first example was cast as String and the second example were cast as uint.

Gary Paluk aka RipX

]]> By: Gary Paluk http://www.daveoncode.com/2009/04/06/actionscript-vector-class-initialization-with-a-source-array/comment-page-1/#comment-4418 Gary Paluk Sun, 03 Jan 2010 00:58:29 +0000 http://www.daveoncode.com/?p=367#comment-4418 BEWARE of instantiating your Vectors in this way as it exhibits random casting behaviours and using an incorrect datatype will NOT throw a compile Error, it will sometimes silently cast the datatype to that specified in the Vector and default to its construction value. Also, compilers will generally give you the Vector specified data type API (as expected) causing invalid method invocation and potential bugs. The following two examples show this in action: var vector:Vector. = Vector.( ["hello", new Point4d(), "world"] ); trace( vector[1] ); The above code traces the toString(): String return value contained in my Point4d object, however: var vector:Vector. = Vector.( [ 5, new Point4d(), 4] ); trace( vector[1] ); traces 0 Yikes, to conclude, if you want compile type data type checking and no silent hidden data casting, avoid this at all costs. Gary Paluk aka RipX BEWARE of instantiating your Vectors in this way as it exhibits random casting behaviours and using an incorrect datatype will NOT throw a compile Error, it will sometimes silently cast the datatype to that specified in the Vector and default to its construction value. Also, compilers will generally give you the Vector specified data type API (as expected) causing invalid method invocation and potential bugs.

The following two examples show this in action:

var vector:Vector. = Vector.( ["hello", new Point4d(), "world"] );
trace( vector[1] );

The above code traces the toString(): String return value contained in my Point4d object, however:

var vector:Vector. = Vector.( [ 5, new Point4d(), 4] );
trace( vector[1] );

traces 0

Yikes, to conclude, if you want compile type data type checking and no silent hidden data casting, avoid this at all costs.

Gary Paluk aka RipX

]]> By: JaneRadriges http://www.daveoncode.com/2009/04/06/actionscript-vector-class-initialization-with-a-source-array/comment-page-1/#comment-2189 JaneRadriges Sat, 13 Jun 2009 20:30:03 +0000 http://www.daveoncode.com/?p=367#comment-2189 The best information i have found exactly here. Keep going Thank you The best information i have found exactly here. Keep going Thank you

]]> By: George http://www.daveoncode.com/2009/04/06/actionscript-vector-class-initialization-with-a-source-array/comment-page-1/#comment-1117 George Wed, 29 Apr 2009 19:05:03 +0000 http://www.daveoncode.com/?p=367#comment-1117 Thanks Thanks

]]>