 |  |  |  |  |  |  |  |
Library Questions
Please support our C++ advertiser: Intel Parallel Studio Home
 |
Hi,
I am new to using C and C++ libraries. So my questions might seem to be naive.
1. When installed, will the source files ( .c or .cpp) of a library be placed into some system directory like /usr/local/src/ for other code that will use them?
2. If not, are all the implementations included in the library files and accessible during debug by stepping-into?
3. If the library files are dynamic linked, i.e .so or .dll, can the implementations be accessed during debug?
Thanks in advance!
I am new to using C and C++ libraries. So my questions might seem to be naive.
1. When installed, will the source files ( .c or .cpp) of a library be placed into some system directory like /usr/local/src/ for other code that will use them?
2. If not, are all the implementations included in the library files and accessible during debug by stepping-into?
3. If the library files are dynamic linked, i.e .so or .dll, can the implementations be accessed during debug?
Thanks in advance!
Last edited by lehe; Jan 27th, 2009 at 7:38 pm.
•
•
Join Date: May 2008
Posts: 631
Reputation: 
Solved Threads: 103
Practically a Master Poster
Whether or not the source is available for a given library is up to the developer of the library.
If the source files are not included, you can't step into them. (Unless you like to read disassembly.)
If the library is only released as a dll, the same applies.
If you are having problems with a library that was released without source, you are generally not supposed to attempt to debug it.
If you are having a problem with such a library, you confirm that you are using the documented interface and then 'prove' that the function you call does not behave as documented. You then 'present' the evidence to the library supplier and they will usually fix the problem and release an updated library.
If the source files are not included, you can't step into them. (Unless you like to read disassembly.)
If the library is only released as a dll, the same applies.
If you are having problems with a library that was released without source, you are generally not supposed to attempt to debug it.
If you are having a problem with such a library, you confirm that you are using the documented interface and then 'prove' that the function you call does not behave as documented. You then 'present' the evidence to the library supplier and they will usually fix the problem and release an updated library.
|
Similar Threads
- A few questions about C++ (C++)
- MFC File I/O Philosophy questions/clarifications (C++)
- Very new to C++ ...questions (C++)
- Having trouble with library in dev-c++ (wxWindows) (C++)
- Beginner's questions: C++ and databases (C++)
- 128bit arithmetic (C++)
- 2 ASP Questions (ASP.NET)
Other Threads in the C++ Forum
- Previous Thread: insertion operator
- Next Thread: Bubble sort
| Thread Tools | Search this Thread |
Latest C++ Posts
- Today's Posts
- Unanswered Threads
Related Forum Features
Tag cloud for C++
api application array arrays assignment beginner binary bitmap c++ c/c++ calculator char char* class classes code coding compile compiler console conversion convert count data database delete developer display dll email encryption error file forms fstream function functions game generator getline givemetehcodez graph homeworkhelper iamthwee ifstream image input int java lazy lib loop looping loops map math matrix memory multidimensional multiple newbie news node number numbertoword output parameter pointer problem program programming project proxy python random read recursion recursive reference return sorting string strings struct template templates text tree url variable vector video visual visualstudio win32 windows winsock word wordfrequency wxwidgets
