Compatibility with LDG version 1.xx

LDG 2.xx is a major evolution compare to LDG version 1.xx (the last was 1.20). We list the difference between the two versions and say few words about the compatibility.

1. LDG manager disappears.
   With LDG 1.xx, the manager loads and unloads libraries requested by clients and handles special library flags (locked, resident, unshareable). This job is now performed directly by the LDG TSR.
    
2. GEM protocol disappears.
   It is a consequent of the previous point. Because client can call directly from the TSR functions, GEM messages are obsolets. The consequence is the system is now really fast. Time idle parameter is unusefull. However, the message LDG_QUIT (see ldg_open()) is kept and used to inform clients their libraries have been unloaded from the memory.
    
3. Library are loaded with the same way from an application or from a library.
    

Libraries and clients compiled with LDG 1.xx are fully compatible with LDG 2.00 if LDG manager is installed in LDG paths. Even, for some clients using directly cookie functions, LDG manager is not used.

Calls for loading and unloading are now very simple. There are only two functions : ldg_open() and ldg_close(). LDG 1.xx made the distinction between library loaded by client and library loaded by a library. It is not necessary to change your code if you compile your application with LDG 2.00 because the header LDG.H provides some macros allowing the backward compatibility.