Xref: utzoo comp.software-eng:2674 comp.misc:7663 Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!cs.utexas.edu!wuarchive!texbell!sugar!ficc!peter From: peter@ficc.uu.net (Peter da Silva) Newsgroups: comp.software-eng,comp.misc Subject: Re: Linkers Message-ID: <7277@ficc.uu.net> Date: 12 Dec 89 23:05:42 GMT References: <530@enea.se) <7226@ficc.uu.net) <547@enea.se> Reply-To: peter@ficc.uu.net (Peter da Silva) Organization: Xenix Support, FICC Lines: 25 > )In which case the routine would be referenced in the *database*, and so > )would be linked in. > Eh? You link relational databases with your executeable? Database != relational database. In this case it just means a table of function names and locations. > To make it even worse, one code may map to different routines > at different sites, since two customers want different behaviour. So far, so good. > To make it simple, you link both routines with your executeable, > and the contents in the menu databases at the customer site decide > which variant they will run. Say what? You have an external relational database containing absolute addresses in your executable? What happens when you want to ship them a new version of the program? They have to rebuild the database? -- `-_-' Peter da Silva. +1 713 274 5180. . 'U` Also or . "It was just dumb luck that Unix managed to break through the Stupidity Barrier and become popular in spite of its inherent elegance." -- gavin@krypton.sgi.com