| Notices |
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
 |
GNU/Linux Basic Guide
This 255-page guide will provide you with the keys to understand the philosophy of free software, teach you how to use and handle it, and give you the tools required to move easily in the world of GNU/Linux. Many users and administrators will be taking their first steps with this GNU/Linux Basic guide and it will show you how to approach and solve the problems you encounter.
Click Here to receive this Complete Guide absolutely free. |
|
 |
- Q: Why should we split our program instead of
placing all the code in one file?
A: If/When our program becomes very large, or it contains
the code for some entirely different sets of functionalities,
it may become cumbersome for us to edit/read the lengthy
code.
Also, if we make a small change and then try to recompile,
the whole giant file will get compiled again and may
consume quite some amount of time.
Dividing our
...
|
Senior Member
|
|
Views 463
Comments 0
|
All times are GMT -5. The time now is 02:56 PM.
|
