[ On Thursday, July 27, 2000 at 16:52:59 (-0400), Noel L Yap wrote: ]
> Subject: general makefile (and script) style rule
>
> Aside from "preventing" (ie ignoring) the problem, has anyone else found a good
> way to deal with the situation?
Proactively seeking them out and destroying them is hardly "ignoring the
problem"! :-)
> Note that I have considered the alternatives of:
> CLEARTOOL:="//c/Program Files/Rational/ClearCase/bin/cleartool"
>
> and:
> CLEARTOOL:=//c/Program\ Files/Rational/ClearCase/bin/cleartool
>
> The former has a problem when using $(CLEARTOOL) within another set of double
> quotes. The latter has a problem when passing $(CLEARTOOL) to another script.
> However, wrapping the call in double quotes makes the makefile less legible.
Well you can bow out of the problem with the second approach and simply
claim it's up to any script to deal properly with its arguments. That
is in fact the only 100% successful way to avoid outlawing such
filenames. Dealing with arbitrary arguments in a POSIX shell script is
difficult sometimes, but far from impossible, and it's good programming
practice regardless of what environment the script might run in.
--
Greg A. Woods
+1 416 218-0098 VE3TCP <[EMAIL PROTECTED]> <robohack!woods>
Planix, Inc. <[EMAIL PROTECTED]>; Secrets of the Weird <[EMAIL PROTECTED]>
