octave-maintainers
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: .h.in vs .in.h


From: Júlio Hoffimann
Subject: Re: .h.in vs .in.h
Date: Wed, 11 Apr 2012 17:57:31 -0300

Yeah, hehehe, it's also strange having *.h.in, but at least it follows the traditional \w+.in naming stuff found in GNU autoconf (configure.in)?

Anyways, renaming the files because of a regex scope is not the prettier solution. :-)

Júlio.

2012/4/11 John W. Eaton <address@hidden>
On 11-Apr-2012, Júlio Hoffimann wrote:

| Well, if i understood correctly, why not just do a trivial `grep ... *.h *.h.in

I often forget that there are .in files.

| ' ? If targeting only Bash (what i think is not the case), you can be even
| more compact: grep *.{h,h.in}

I also often do things like

 find . -name '*.h' -o -name '*.cc' | xargs grep ...

to find files in the entire directory tree.

| It's strange having *.in.h files.

How is it any stranger than having .h.in files?

jwe


reply via email to

[Prev in Thread] Current Thread [Next in Thread]