I agree with Tim and with Tim's suggested API, in particular
"withfile". Involving the shell in something as basic and inherently
portable as writing to a file opens up a world of portability issues,
in addition to the performance and readability problems mentioned.
Given that some platforms (Windo
>
> I find your suggestions more elagant than the original, they seem more
> general purpose, and less "let's introduce this feature to get around
> a specific problem". Of your two suggestions, I'd favor the "withfile"
> option, it would be both more powerful, and doesn't introduce the
> problem o
At Sun, 25 Sep 2011 19:36:26 +0100,
Tim Murphy wrote:
> My apologies to Luke for forgetting "reply to all" and for forgetting
> my manners by using the word "sucks" when I should not have.
Now it's my turn to apologize, I just forwarded your original message
to me to the list. Sorry.
> > dumpOneL
You didn't CC the list
--- Begin Message ---
I use the foreach "trick" and it utterly sucks. It's complicated and
tends to execute the shell 10x more than it needs to. For small
makefiles it doesn't matter but doing this for compiles (e.g. the ARM
RVCT's multifile compilation option) in a large m
My apologies to Luke for forgetting "reply to all" and for forgetting
my manners by using the word "sucks" when I should not have.
> I vote 'no'. This can easily be implemented in your
> Makefile. (assuming no single list item breaks the limit)
>
> dumpOneLine = $(foreach item,$(2),echo -n '$(item
At Tue, 20 Sep 2011 12:09:42 -0700,
Lawrence Ibarria wrote:
> I have often hit problems with the limit of command line lengths
> many shells have (CMD.EXE in Windows in my case).
> This is a common case with few solutions, I have searched around:
>
> http://www.makelinux.net/make3/make3-CHP-5-SECT
