Two comments to add

   1. The "old" syntax and the lua syntax can coexist somewhat, this is you
   have a rule that is complicated enough to require lua it can, but you can
   still use the standard tup syntax where it's not required.
   2. For your specific problem, I feel like you could do something with
   the standard syntax, although you would have to give up some of the
   parallel build aspects. e.g.

   cat Tupfile <<<EOF
   : foreach *.c |> gcc -c %f -o %o |> %B.o {objs}
   : foreach *_test.o | {objs} |> gcc -o %o %g.o %f |> %B
   EOF

On Wed, Nov 30, 2016, 04:07 Freddie Chopin <[email protected]> wrote:

Hello again Thomas!

I guess there's no distinction into "old" (as in "legacy") and "new"
(as in "shiny") syntax. I think the only distinction is purely
chronological - the "old" syntax is in fact older then the lua syntax.

As to which one of these is better I think it's jus a matter of
preferences. For me the "old" syntax was too restrictive and I was more
than happy to switch to lua the moment it was available. In fact I've
heard that Mike is working on adding Python to tup (;

The syntax of lua may seem a bit strange at the first glance, but you
can do anything that is possible in the "old" syntax. If you have any
questions about tup+lua - just ask.

Regards,
FCh

--
--
tup-users mailing list
email: [email protected]
unsubscribe: [email protected]
options: http://groups.google.com/group/tup-users?hl=en
---
You received this message because you are subscribed to the Google Groups
"tup-users" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to [email protected].
For more options, visit https://groups.google.com/d/optout.

-- 
-- 
tup-users mailing list
email: [email protected]
unsubscribe: [email protected]
options: http://groups.google.com/group/tup-users?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"tup-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to