Subject: Redeem Gift-Card

From: Southwest Reward Center <[email-masked]>
Date: Tue, 01 Jul 2014 08:32:00 -0700

SOUTHWEST

Greetings Ipp-archive,

We are extending you Rapid Rewards!

To Enjoy Your Southwest Rewards, all you need to do:

Redeem Southwest Gift-Card Here!

Do you love to fly Southwest?

Share your opinion and Southwest experiences by completing the survey and

Claim your Southwest gift card Here!

If you would like to stop further reward notifications write: Current Update Alerts

1644 Doral DrBrookings, SD 57006 or please click here.

On Windows/Mac (no package manager) there is really no good reason to use dynamic libraries over static. Since Windows DLLs are not relocatable, code sharing often does not work (and usually each app ships and uses its own versions of the library anyways). The only real benefit is that it is easier to update the library. Zifre May 11 '09 at 21:02

What, specifically, do you mean by relocatable? Orion Adrian May 12 '09 at 14:05
3
on the mac, I use a lot of dynamic libraries. for example, mac os x has sqlite3 embed. i created a program that has a sqlite3 database feature for performance storing. however, because it is rarely used dynamic linking saves on compile time, makes testing easier/faster however, if I were to build a release version, I think I would always use static library just in case of compatibility issues ReachConnection Oct 16 '09 at 19:34
2
@Zifre: relocatable = can be loaded at different virtual address. DLL certainly supports this. dma_k Oct 2 '10 at 12:35
7
@dma_k: Windows DLLs can be loaded at different addresses, but only because the linker copies all the code and changes the address numbers. With shared objects, all the address references are relative, so multiple processes can share the same memory for the shared object. In other words, on Windows, A 1 MB DLL used by 3 programs = 3 MB. On Linux, A MB SO used by 3 programs = 1 MB. Zifre Oct 17 '10 at 1:15
1
Both Windows and Linux has the concept of load-timte relocation of shared libraries eli.thegreenplace.net/2011/08/25/ The biggest thing that allowed Position Independent Code wasn't something special to Linux, rather RIP-relative addressing added with the x64 instruction set; both Windows and Linux can make use of RIP relative addressing do reduce the number of fixups when relocating libraries. clemahieu Aug 3 '13 at 15:47