Interesting - I'll have to go back and reread the make docs to fix this in my mind. Thanks for teaching me something new today :-) -Samrobb
-----Original Message----- From: Ross Ridge [mailto:[EMAIL PROTECTED] Sent: Mon 4/19/2004 9:40 PM To: [EMAIL PROTECTED] Cc: Subject: RE: Cygwin make thinks a statement can be neither true nor false.... > Possibly a bug in make, as I'd expect it to complain >about an undefined function named "error:". I would've expected it to complain about a bad substition reference, ie. it's missing an "=". > Similar constructs are also silently ignored: > > $(foo This isn't a valid make function) > $(bar Neither is this) Since "foo" and "bar" aren't functions supported by GNU Make these are just simple variable references. Eg: foo This isn't a valid make function=one bar Neither is this=two test: echo $(foo This isn't a valid make function) echo $(bar Neither is this) Ross Ridge -- l/ // Ross Ridge -- The Great HTMU [oo][oo] [EMAIL PROTECTED] -()-/()/ http://www.csclub.uwaterloo.ca/u/rridge/ db // -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/