Return-Path: pg_adm@postgres.berkeley.edu
Received: by postgres.Berkeley.EDU (5.61/1.29)
	id AA04542; Fri, 22 Jan 93 09:23:12 -0800
Date: Fri, 22 Jan 93 09:23:12 -0800
Message-Id: <9301221723.AA04542@postgres.Berkeley.EDU>
From: witr@rwwa.COM
Subject: Suggestion: remove nonportability in dynloaded object names
To: postgres@postgres.berkeley.edu
Sender: pg_adm@postgres.berkeley.edu
Content-Type: text
Content-Length: 582

I would like to suggest that the next release of postgres remove the
assumption (in the documents, and in the code) that a dynamically
loaded object has a name ending in .o.  The port dynloading code
should know what the correct extension is, since it varies from
platform to platform (for example, on svr4 it would be .so).  Thus I
suggest that all references to dynloaded objects have *no extension*.

Thanks for listening.
---
 Robert Withrow, Tel: +1 617 598 4480, Fax: +1 617 598 4430, Net: witr@rwwa.COM
 R.W. Withrow Associates, 21 Railroad Ave, Swampscott MA 01907-1821 USA