Re[2]: So is this OK to write #include "parser.tab.hh" in parser.yy?

[Askar Safin]

>We
>generate parser.tab.{hh,cc} by default, because I was too stupid
>when I introduced the C++ skeleton to allow myself not to follow
>the idiotic and historic naming scheme.
I like current naming scheme.

It allows me to easily ignore generated files when I grep my whole home 
directory trying to find something.

When I grep my home dir, I type something like this:

$ find -L ~ '(' -path '*/.git' -o -path '*/autom4te.cache' -o -path 
'*/node_modules' ')' -prune -false -o -type f | grep -v 
'\.\(ps\|json\|pdf\|log\|mmp\|Po\|nb\|yy\.c\|yy\.cpp\|tab\.h\|tab\.hpp\|tab\.c\|tab\.cpp\|min\.js\)$'
 | grep -v 
'/\(missing\|output\.[0-9]*\|configure\|config\.status\|depcomp\|install-sh\|compile\|traces\.[0-9]*\|COPYING\|INSTALL\|aclocal\.m4\)$'
 | sort > /tmp/find-text-o

$ grep --color=always --no-messages -B 5 -A 5 -i -- 'some string' $(< 
/tmp/find-text-o) | less -R

Note 'yy\.c\|yy\.cpp\|tab\.h\|tab\.hpp\|tab\.c\|tab\.cpp' above
==
Askar Safin
http://vk.com/safinaskar