 |
BorlandTalk.com
Borland discussion newsgroups
|
| View previous topic :: View next topic |
| Author |
Message |
Tracey
Guest
|
 Posted: Fri Mar 23, 2007 2:31 am Post subject: naming convention: unit.cpp and project.bpr |
 |
|
Is it necessary/advisable to name unit.cpp and project.bpr as such...
or...
can I and the CPP and the BPR file after the program-name that I am trying
to create (like: MyApp.cpp and MyApp.bpr)
I do create a separate folder for each project, but it seems logical to name
the CPP and the BPR file the same as the program name, but it also may
create more hassles or issues than its worth.
Thanks, Tracey |
|
| Back to top |
|
 |
Remy Lebeau (TeamB)
Guest
|
| Posted: Fri Mar 23, 2007 3:42 am Post subject: Re: naming convention: unit.cpp and project.bpr |
|
|
"Tracey" <wpiis (AT) gte (DOT) net> wrote in message
news:4602e79f$1 (AT) newsgroups (DOT) borland.com...
| Quote: | Is it necessary/advisable to name unit.cpp and project.bpr as
such... |
It is not necessary.
| Quote: | can I and the CPP and the BPR file after the program-name that
I am trying to create (like: MyApp.cpp and MyApp.bpr)
|
Of course. However, do keep in mind that the .bpr will have its own
..cpp file, so do not name your other units the exact same as the
project name.
| Quote: | it also may create more hassles or issues than its worth.
|
No, it won't. Why would you think that?
Gambit |
|
| Back to top |
|
|
Chris Uzdavinis (TeamB)
Guest
|
| Posted: Fri Mar 23, 2007 6:06 pm Post subject: Re: naming convention: unit.cpp and project.bpr |
|
|
"Tracey" <wpiis (AT) gte (DOT) net> writes:
| Quote: | Is it necessary/advisable to name unit.cpp and project.bpr as such...
|
Not really.
| Quote: | or... can I and the CPP and the BPR file after the program-name
that I am trying to create (like: MyApp.cpp and MyApp.bpr)
|
I think that's a much better way to go. Otherwise you have to
memorize which classes are in which units, without any name-hints.
Then using grep or "find in files" will be so common that you'll want
to pull your hair out.
I've, um, "heard" of some companies that thought of source files as
"inventory" and programmers actually had to submit a form to receive
an inventory number before creating a filename, and they were TOLD
what the filename would be. They ended up being unreadable internal
codes, like aQ7dF.cpp and bY7j2.cpp. Programmers that worked there
had no incentive to create new files (as proper programming habits
would normally have you do), and so they tended to throw LOTS of
classes into a single file. Further, for productivity they had to
have a piece of paper taped to their screen that would "map" real
classes to filenames, so they could find what was there.
Eventually they relaxed these rules, I've been told, but only after
all of the talented developers resigned.
In short, I agree fully with meaningful filenames. :)
--
Chris (TeamB); |
|
| Back to top |
|
|
Thorsten Kettner
Guest
|
| Posted: Mon Mar 26, 2007 8:10 am Post subject: Re: naming convention: unit.cpp and project.bpr |
|
|
"Tracey" <wpiis (AT) gte (DOT) net> wrote:
| Quote: | can I and the CPP and the BPR file after the program-name that
I am trying to create (like: MyApp.cpp and MyApp.bpr)
|
You should name the bpr according to your project and the cpp
after what it contains, e.g. HelloWorld.bpr, UnitFormMain.cpp. |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
FAQ
Search
Memberlist
Usergroups
Register
Profile
Log in to check your private messages
Log in
