StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
2661913
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
1
CommunityOwnedDate
CreationDate
2010-04-18T10:33:42.333
FavoriteCount
0
LastActivityDate
2010-04-18T12:33:48.363
LastEditDate
2010-04-18T12:33:48.363
LastEditorUserId
319415
OwnerUserId
319415
ParentId
2661448
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
text
Body
Imagine that: You are a designer of library (DLL). You have to define what library must to do ... and after that you write it. Many process can use your functions from this DLL, there are one piece of memory in your RAM. When you include this library to your project (for example in c++) you have to add some informations about functions in this DLL. First option: You can declare some interfaces of library functions (then your linker is happy ;) ). For example: __declspec(dllexport) int my_function(char *); After that names of exported objects are completed in your programme (linker job ;) )... but Names of this objects depends on language, compiler, blah blah blah Second option: You add to the project of your library some informations to the linker (file *.def). That file has two sections: LIBRARY and SECTIONS. LIBRARY is internal name your lib: LIBRARY my_lib In EXPORTS section are symbols which can by exported from library. EXPORTS function1 function2 function3 You can see, this functions doesn't have types, formal parameters etc. When you include this lib, you don't have any information about function. When you do this (.def file) and compile your lib, you have got .dll and .lib file. Second file can be use to link library in execution time. If you want check exports in this library you can use "Dependecny Walker" or "dumpbin": dumpbin my.dll /exports Next you can load that library: first option: __declspec(dllimport) int my_function(char *); or second: HMODULE LoadLibrary(LPCSTR lpszLibName); conlusion: using exports can create more universal lib (but more complicated) (sorry for my very bad english :/)
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POHelp in understanding EXPORTS in Makefile.in
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USvizzdoom
UserOwnerUserId
1. USvizzdoom
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. This table or related slice is empty.
CommentsPostId
1. COThank you. But if 'In EXPORTS section are symbols which can by exported from library.', why in my example, it has .h files?
 singulars
 PostPostId
 PO
 UserUserId
 USmichael

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.