Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
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.
libraries hold algorithms....
the thing about computer programs, is they all do the same thing, they put things on your screen, they load and save files, they make noises, they talk to other machines over the internet........
it would be a waste of time if every time a programmer made a program they had to write there own Disk accessing functions !!! and programs would be HUGE.
so, the disk accessing functions are written only once, and saved in a library that any other application can use.
unless you are programming in Assembly, then computer programming is all about writing algorithms, and calling library functions, getting them to do what you want.
1. are there many cases of libraries for libraries? (I came across a "libglib" once).
2. Are reverse compatibilities respected in library upgrades? It would seem so, due to the convention of renewing symlinks a generic library name to the latest library version. But it would also seem it's a free-for-all sometimes.
Distribution: Red Hat, openBSD,Mandrake,freeBSD,SunOS
When I saw the title for this thread the first thing I thought of was the Seinfield episode where Jerry Seinfield intentionally tries to screw up his stand up comedy routine and starts off with:
"What's the deal with Cancer?"....and gets booed off the stage....hehehehe
Just thought I would share....made my morning
If you don't know what Seinfield is....just carry on...ignore this thread.
Sorry for taking up space on a valid and interesting thread with banal information :}
Originally posted by SciYro so libraries are sometimes not binary compatible with other versions? who cares, its called compiling, solves this little problem
Could we do a quick rewind and slow-mo over this one? SO there's binary compatibility and source code compatibility then?
Typically, how does the (RE)compilation of the source get over the incompatibilities that the (PRE)compiled display?
This is the newbie forum don't forget.
lets say i have some source code.. (called My-Program)
and my program uses a function (called My-Function)
from a library called (My-Library version 1.2)
When i compile my program, it gets linked to My-Library version 1.2
at this linking stage, it looks inside My-Library, and gets the address of the function.
Now.. lets say i give the compiled binary of My-Program to someone who has version 1.1 of My-Library on there machine.... the older library probably still has a function called My-function, but the binary library is different, the function may be at a different address or whatever, anyway, My-Porgram will not reconise My-Library.
However, if instead i gave the other person the source code to My-Prigram, when they compiled it, the linker would link the compiled program to THEIR version of My-Library, which is version 1.1. and will still work.
well... thats a simplified version of what really happens.