On Thursday, February 5, 2004, at 03:38 PM, J. Landman Gay wrote:
I am starting to lose track of what we are talking about, but maybe this helps: you can start using a stack any number of times, but it only actually gets used once. So it doesn't matter who starts to use what when.
But what if it is not in the expected location?
Library A' from vender A needs library B' from vender B. Library A' has some notion where B' is and refers to it there. Developer C puts B' in a different location and then makes the developer's app C' start using B' and then A'. Should C expect this to work?
In general, the track goes like this: What are common styles of stack organization that might be considered good practice? What might a library supplier do as good practice to make a library easy to use in styles of stack organization?
Dar Scott
_______________________________________________ use-revolution mailing list [EMAIL PROTECTED] http://lists.runrev.com/mailman/listinfo/use-revolution
