undefined | Better HN

0 pointsjlarocco2y ago0 comments

Have to agree with the OP here.

There may be a handful of yacc files in a large project, so prefixing them with "yy" is convenient to locate them quickly - though I'd still prefer a dedicated subdirectory.

Every file in this project is a "castle file", so preceding every name with "castle" is pretty useless and hinders readability and navigation. If it's not part of castle, it shouldn't be checked into the repo.

0 comments

vfclists2y ago

And what happens when these castle_xx files have to be combined with files from other libraries?

This goes a long way into avoid namespace conflicts.

dkersten2y ago

Do they need that? If not you’re using a hypothetical situation that likely will never occur to excuse a bad decision (see YAGNI). In my 24 years of programming, I’ve never needed to do this in any way where this naming would have helped me (a very occasional single prefixed file sure, but an entire project, never).

j / k navigate · click thread line to collapse