Re: Attempting to unit test

2000-11-25 Thread Tom Tromey
> "Pavel" == Pavel Roskin <[EMAIL PROTECTED]> writes: >> Do you think it would be better to warn or to simply recognize >> lines like that? Pavel> I think it's better to recognize those lines and ignore Pavel> spaces. Doing otherwise will make Automake somewhat similar to Pavel> Python becau

Re: Attempting to unit test

2000-11-22 Thread Pavel Roskin
Hello, Tom! > Do you think it would be better to warn or to simply recognize lines > like that? I think it's better to recognize those lines and ignore spaces. Doing otherwise will make Automake somewhat similar to Python because the formatting will affect the result (without being considered a

Re: Attempting to unit test

2000-11-22 Thread Marc van Woerkom
> Pavel> Don't start lines in Makefile.am with spaces. Automake will not > Pavel> recognize them, neither will it warn you. > > Do you think it would be better to warn or to simply recognize lines > like that? At least warn. Regards, Marc

Re: Attempting to unit test

2000-11-19 Thread Tom Tromey
> "Pavel" == Pavel Roskin <[EMAIL PROTECTED]> writes: >> check_PROGRAMS = test_program >> test_program_SOURCES = test.C Pavel> You have discovered a bug in Automake. It still exists in the Pavel> current CVS version. Pavel> Don't start lines in Makefile.am with spaces. Automake will not

Re: Attempting to unit test

2000-11-16 Thread Pavel Roskin
Hello, Tim! On Thu, 16 Nov 2000, Tim Heath wrote: > I have added the following lines to a Makefile.am: > > check_PROGRAMS = test_program > test_program_SOURCES = test.C You have discovered a bug in Automake. It still exists in the current CVS version. Don't start lines in Makefile.am with

Attempting to unit test

2000-11-16 Thread Tim Heath
I have added the following lines to a Makefile.am: check_PROGRAMS = test_program test_program_SOURCES = test.C When I execute automake -i (v1.4) the ./configure it generates the line: test_program_SOURCES = test_program.c in the Makefile. What happened to test.C? Thanks, Tim Heath