work flow language 1084

Black Sun and said:

When using that miserable "G2" excuse for a real newsreader, follow the approximating the right thing.

First thing to do is to learn WFL, then you should be able to translate it into something different. All Turing-complete languages are theoretically equivalent, after all. (Note: it may be somewhat difficult to express the weirder Perl syntax constructs in C, but it's certainly *possible* to get a rough approximation of functional equivalence with enough work. Whether this is efficient or politically feasible depends on a lot of details that haven't been provided.)

...when all the keywords are in CAPS and there are things that look suspiciously like line numbers interspersed with statements, you're probably dealing with something that was meant to run on a dinosaur or a bitty box. Find out which one it is, which variety, and which OS. If it's meant to run on a dinosaur, you may find better help in another newsgroup.

snip

Interesting. What's the & operator do? String concatenation? That's easy enough. Dates are easy enough with Time::Date or `date` or the routines in time.h, depending on the target language.

#s in front of variable names... interesting, sort of like the $ construct in bash. The CHANGE operation looks similar to the =~s expression in Perl, or bash's internal regexp handling, or the things sed can do. But it may actually do totally different things.

snip more stuff

I think the best bet would be to learn enough WFL to get by and translate things on the fly, as you need it. The WFL script you posted doesn't *seem* too complex to me, but then I don't have a WFL manual or a person who knows WFL around, so I may be missing something significant. HTH anyway,

-- Matt GThere is no Darkness in Eternity-But only Light too dim for us to see Brainbench MVP for Linux Admin mail: TRAP + SPAN don't belong ----------------------------- penguins, is Tux." --MegaHAL