<story><title>The tale of aux.c</title><url>http://heirloom.sourceforge.net/mailx_aux_c.html</url></story><parent_chain></parent_chain><comment><author>badsectoracula</author><text>So, all that text to tell people he is refusing to rename a single file? :-P&lt;p&gt;I encountered that issue a few times in the past, most recently when a couple of years ago i was writing the console support for my 3d game engine and made two files called `con.c` and `con.h`, checked them in to version control and then at some point (much) later synced it on the Windows side. Fossil (the VCS i use) simply skipped that file (maybe it complained? i don&amp;#x27;t remember, but the files weren&amp;#x27;t created) and when i tried to build the engine it didn&amp;#x27;t work - i thought that i forgot to add the files, rebooted to Linux, forced a re-add, back to Windows and nothing again.&lt;p&gt;Eventually it clicked that &amp;quot;con&amp;quot; is a bad word in Windows filesystems, so i simply renamed the files to `csl.c` and `csl.h` :-P. I found this a bit irritating because my naming convention follows a mostly rigid pattern where `xxx_` prefixed functions will always recide on `xxx.c&amp;#x2F;h` (or `xxx_yyy.c&amp;#x2F;h` where yyy is a subsystem or specialization) and i really prefer the `con_` prefix to the `csl_` one. So far i&amp;#x27;ve kept the `con_` prefix and made a special note for that in the readme file where i explain the naming conventions, but every time i have to use or work with that part of the engine i feel the irritation :-P.</text></comment>
<story><title>The tale of aux.c</title><url>http://heirloom.sourceforge.net/mailx_aux_c.html</url></story><parent_chain></parent_chain><comment><author>drfuchs</author><text>So, you smug Linux guys think it can&amp;#x27;t happen to you? Well, before you get off my lawn, let me tell you a story...&lt;p&gt;Early versions of FrameMaker kept all resource files (internationalized strings, dialog box layouts, etc.) in the two subdirectories ...&amp;#x2F;FrameMaker&amp;#x2F;Resources&amp;#x2F;{Unix,Core} (the first one for the Unix platform-specific resources, and the second for the cross-platform ones also used by the Mac and Windows ports). We had hundreds of happy customers, and had been shipping for 4 years or more.&lt;p&gt;But one new customer was calling in a panic. They&amp;#x27;d installed the product, and it would work fine, but the next morning, it wouldn&amp;#x27;t even start up, and they had to re-install it. And then it would break again over night. After much pulling of hair and gnashing of teeth, it turns out that due to some other flakey product they were running, they had previously instituted a nightly cron job that ran around removing any core files it could find (since they were large and wasteful of precious disk space back in the day). And the knucklehead who wrote the script had it do a case-insensitive match on &amp;quot;core&amp;quot; &lt;i&gt;and&lt;/i&gt; had it essentially do a &amp;quot;rm -rf&amp;quot; even though no true core file could be a directory. So, every night, our Core resource directory was blown away.&lt;p&gt;We actually had to change the product, as this was a big, important customer, and they outright refused to fix their cron script. Never had this problem on the Windows and Mac ports.</text></comment>