RE: [cc65] Coding style for apps: One huge header file, or a domain specific header files?

Personally, I like to keep my code in separate "modules", but also maintain
a "global.h" for global variables that are used throughout the program.  For
instance, the screen related stuff, or UI I keep separate from the
underlying i/o routines for utilities, although I was thinking recently that
with the optimizations that Ullrich has done for string storage, that it
makes more sense to put everything into one big file, as the string
optimization doesn't work across object files.

 

 

 

  _____  

From: owner-cc65@musoftware.de [mailto:owner-cc65@musoftware.de] On Behalf
Of Payton Byrd
Sent: Sunday, May 02, 2010 7:20 PM
To: cc65
Subject: [cc65] Coding style for apps: One huge header file, or a domain
specific header files?

 

I'm having a bit of code sprawl with my project and I am beginning to think
I should just have a single header file for the whole project and not one
for each code file as I was taught to do in school.  My code is beginning to
look like a smoke stack in the declarations with all the includes
everywhere.  What do you guys normally do?

-- 
Payton Byrd
<http://www.paytonbyrd.com>
<http://it.toolbox.com/blogs/paytonbyrd>




----------------------------------------------------------------------
To unsubscribe from the list send mail to majordomo@musoftware.de with
the string "unsubscribe cc65" in the body(!) of the mail.