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: Daniel J Sebald
Subject: Re: .h.in vs .in.h
Date: Wed, 11 Apr 2012 16:06:55 -0500
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.24) Gecko/20111108 Fedora/3.1.16-1.fc14 Thunderbird/3.1.16

On 04/11/2012 03:24 PM, John W. Eaton wrote:
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?

Just the fact that the extension is .h and the file really isn't a header file. The only confusion I could see arising is if some IDE (is this done anywhere? Windows compilation perhaps?) might interpret a .in.h file as a header file.

Dan


reply via email to

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