On Sep 13, 2008, at 2:38 PM, Mark Wieder wrote:
Saturday, September 13, 2008, 6:10:42 AM, you wrote:
Why force the developer to enforce an order after the fact? That is
My point is rather that there's no need to impose an order on data
that isn't ordered. Or at least not chronological order on xml data.
I guess we jut have to agree to disagree then :-) XML that represents
data from a database is ordered and the order does in fact matter as
it is usually the result of a sort of some kind. There are times when
you would like to print things off as they appear in the XML tree.
As I pointed out to David Bovill, I think you're talking about a queue
or a stack here rather than just an array. I use both queues and
stacks and I'd like to see them as primitive objects at some point.
push "title 1" onto theDataA[]
push "title 2" onto theDataA[]
pop theDataA[] into tCurrentTitle
I'm actually referring to how I would like to see arrays behave in
Revolution. They just aren't the types of arrays you are accustomed
to. Like I said before, I really like how PHP arrays work and I am
advocating something similar in the feature request (which David filed).
We just have different views on how an array should work in Revolution.
Regards,
--
Trevor DeVore
Blue Mango Learning Systems
www.bluemangolearning.com - www.screensteps.com
_______________________________________________
use-revolution mailing list
[email protected]
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution
