For instance, in javascript/flash, if you have a set of fields, named field_1, and field_2, and so on to field_10, they could be referenced dynamically like so:
for x = 1 to 10
eval("field_"+str(x)) = "some value"
next xThe same could be done in witango with a bunch of arguments, <@arg field_1>, and so on.
<@for start=1 stop=10 step=1>
<@addrows local$newArray <@arg field_<@currow>>>
</@for>I don't believe this could be done in a compiled language. You would have to use a select case method or build an array of objects or something.
Robert.
On Tuesday, July 1, 2003, at 01:47 PM, Atrix Wolfe wrote:
you could still do dynamic referencing if they made allowances for it, like
if they stored a table w/ the names of the vars and pointers to them.
If you can make java bytecodes though and then use gcc to make that into an
executable or dynamic library, would you really need With to make a witango
compiler? That is assuming you dont lose anything like dynamic referencing
in either of those 2 steps.
I've been kind of wondering about this since With said you could make tango
into java bytecodes though...if you made your code into java bytecodes, does
it support dynamic referencing TCF's, includes etc?
Just wondering if could expect any and all code to work the same whether it
was tango or java bytecodes.
----- Original Message ----- From: "Robert Garcia" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Tuesday, July 01, 2003 1:25 PM Subject: Re: Witango-Talk: Boosting Server Performance, and TCFs
Just because our tafs would be compiled in some native format, doesn't
mean we would have to start worrying about things garbage collection.
The compiled tcf would would have in/out points and process data
within. It would run within the memory space of the witango server, and
the server would handle the garbage collection and the nasty stuff. The
main benefit would be that complex methods in a tcf would not be
scripted, but compiled so that there would be no tag processing and the
other performance drags that are inherant with an interpreted language.
It would mean, though, that certain things you can do in a tml or taf,
you could not do, like dynamic referencing.
Robert.
On Tuesday, July 1, 2003, at 09:49 AM, Scott Cadillac wrote:
But it does add several layers of complexity too. I'm not an expert at
this
level by any means, but it seams to me that Witango isn't ready to
support
this kind of low-level environment (nor any interpreted language for
that
matter, e.g., ColdFusion).
For example, garbage collection and other memory allocation issues - what sort of Metatags would we need for this?
--
Robert Garcia President - BigHead Technology CTO - eventpix.com 2781 N Carlmont Pl Simi Valley, Ca 93065 ph: 805.522.8577 - cell: 805.501.1390 [EMAIL PROTECTED] - [EMAIL PROTECTED] http://bighead.net/ - http://eventpix.com/ - http://theradmac.com/
______________________________________________________________________ __
TO UNSUBSCRIBE: Go to http://www.witango.com/maillist.taf
_______________________________________________________________________ _
TO UNSUBSCRIBE: Go to http://www.witango.com/maillist.taf
--
Robert Garcia President - BigHead Technology CTO - eventpix.com 2781 N Carlmont Pl Simi Valley, Ca 93065 ph: 805.522.8577 - cell: 805.501.1390 [EMAIL PROTECTED] - [EMAIL PROTECTED] http://bighead.net/ - http://eventpix.com/ - http://theradmac.com/
________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/maillist.taf
