There really is no increase in code. I do this all the time in a single conditional statement like:

for x = 1 to 10

select case x

        case 1
                field_1 = "some value"
        case 2
                field_2 = "some value"
        case 3
                field_3 = "some value"
        case 4
                field_4 = "some value"
        case 5
                field_5 = "some value"
        case 6
                field_6 = "some value"
        case 7
                field_7 = "some value"
        case 8
                field_8 = "some value"
        case 9
                field_9 = "some value"
        case 10
                field_10 = "some value"
next x

There are other ways also, this is the simplest. Another way is to build an array of objects, and loop through them.

I think you underestimate the level of performance gain you get when you compile versus interpret on the fly on complex tasks. Especially processing loops. I will do a test and get back to this with some results.

Robert.

On Tuesday, July 1, 2003, at 02:32 PM, Ben Johansen wrote:

You are correct, and this is where I question the speed boost.

On one hand you have the quicker run speed but on the other hand you
have the increased amount of code due to lose of this dynamic.

There is no easy conversion of code and mindset between them.

Ben Johansen - http://www.pcforge.com
Authorized Witango Reseller http://www.pcforge.com/WitangoGoodies.htm
Authorized MDaemon Mail Server Reseller
http://www.pcforge.com/AltN.htm


-----Original Message----- From: Robert Garcia [mailto:[EMAIL PROTECTED] Sent: Tuesday, July 01, 2003 2:20 PM To: [EMAIL PROTECTED] Subject: Re: Witango-Talk: Boosting Server Performance, and TCFs

dynamic referencing a table is one thing, that should be ok. What I
mean is referencing an object dynamically like you can do with
javascript/flash with the eval() function.

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 x

The 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


_______________________________________________________________________ _
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

Reply via email to