Re: [Gnu-arch-users] [BUG] Untagged files should always be warning

[Matthieu Moy]

Miles Bader <address@hidden> writes:

> On Sat, Apr 10, 2004 at 10:02:12AM +0200, Matthieu Moy wrote:
>> So, untagged sources raise an error when you have "untagged-source
>> unrecognized" *and* when your tagging method is "explicit".  So an untagged
>> source will raise only a warning in "tagline" mode, even if you have
>> "untagged-source unrecognized" in your =tagging-methods.
>
> No, I think that's wrong -- in tla-tools I use `untagged-source unrecognized'
> and a tagging method of `tagline', and a new source file without any tagging
> info most definitely causes an error (which I like).  As soon as I add a
> tagline or an explicit tag, the error goes away. 

See an example:

$ ls
file.c  {arch}/ 
$ cat \{arch}/=tagging-method
#explicit
tagline
untagged-source unrecognized
source ^[_=a-zA-Z0-9].*$
$ tla tree-lint || echo error
These apparent source files lack inventory ids:

file.c


$ vi \{arch}/=tagging-method 
$ cat \{arch}/=tagging-method
explicit
#tagline
untagged-source unrecognized
source ^[_=a-zA-Z0-9].*$
$ tla tree-lint || echo error
These apparent source files lack inventory ids:

file.c


error
$ 

In both  cases you get  the message on  stdout, but the  return status
changes, according to the tagging method. This is really confusing. 

(I use tla 1.2)

-- 
Matthieu