I can't find a way in order to post my thread properly; therefore I will attach a PDF file through the Manage Attachments option below. Thank you Salem for your reply and I hope that my PDF file can display my thread properly this time. Falconcpp.
I can't find a way in order to post my thread properly; therefore I will attach a PDF file through the Manage Attachments option below. Thank you Salem for your reply and I hope that my PDF file can display my thread properly this time. Falconcpp.
External Dependencies. Please read my new attached PDF file entitled "External Dependencies". Falconcpp.
Please read my final PDF file entitled "Solved case in Cprogramming, for the present time." Falconcpp.
O_o
None of us want to download your PDF just because you are too lazy to describe what you need.
You see, because you are too lazy to describe what you need we are just going to assume that you are too lazy to do the work which leaves us thinking that you just want someone to do the work.
Soma
That, and most of us won't touch random PDF's because of the junk they can contain (deliberately or not) that could cause damage.
If you can't explain your problem in a screen-ful of code and explanatory text, it means you don't really have a problem I would be willing to look into answering.
- Compiler warnings are like "Bridge Out Ahead" warnings. DON'T just ignore them.
- A compiler error is something SO stupid that the compiler genuinely can't carry on with its job. A compiler warning is the compiler saying "Well, that's bloody stupid but if you WANT to ignore me..." and carrying on.
- The best debugging tool in the world is a bunch of printf()'s for everything important around the bits you think might be wrong.