 |
| Register | Login | |||||
 |
Main
| Memberlist
| Active users
| Calendar
| Chat
| Online users Ranks | FAQ | ACS | Stats | Color Chart | Search | Photo album |
|
| | ||
|
| Register | Login | |||||
|
Main
| Memberlist
| Active users
| Calendar
| Chat
| Online users Ranks | FAQ | ACS | Stats | Color Chart | Search | Photo album |
|
| | ||
| 0 users currently in Programming. |
| User | Post |
| FreeDOS + Posts: 45/1312 |
Yeah, and I think neo pretty much explained it  |
| HyperHacker Posts: 97/5072 |
Originally posted by FreeDOS How do you mean? Like actual code to load them? |
| neotransotaku Posts: 48/1860 |
Libraries do not interact with the programs that use them. Rather they are code that is loaded along with the primary program to get things done. For example, suppose you wrote a program foo.exe that used a useful function in foo.dll -- a library you created to contain useful functions. Thus, when foo.exe is run, not only is the code within foo.exe loaded, but also the code found in a library that foo.exe uses. |
| FreeDOS + Posts: 42/1312 |
Yeah, I know what libraries do (and Windows doesn't give anything special but a .dll extension typically), but I don't know how they interact with programs/UIs. |
| HyperHacker Posts: 91/5072 |
On Windows, generally you compile a library into a DLL file. Then other programs can load the file and call whatever functions it exports and access any resources in it. |
| FreeDOS + Posts: 39/1312 |
Can anyone explain how libraries should work? I know they serve as kind-of backends to UIs, but I'm not sure how they should be formed... specifically, it's for this
Also, if anybody has an online tutorials or guides to C, that'll help a lot. |
