From owner-freebsd-hackers Wed Jul 7 1: 8:41 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from agamaweb.agama.ru (www.agama.com [195.94.226.130]) by hub.freebsd.org (Postfix) with SMTP id 5A21F14FA7 for ; Wed, 7 Jul 1999 01:08:17 -0700 (PDT) (envelope-from andrey@agama.com) Received: from [195.94.226.144] by agamaweb.agama.com (NTMail 4.01.0008/NU2432.00.3e8112ca) with ESMTP id gqgbaaaa for ; Wed, 7 Jul 1999 12:04:12 +0400 Message-ID: <000701bec850$311d3850$90e25ec3@agama.ru> From: "Andrew Iltchenko" To: References: <199907061659.JAA15453@vashon.polstra.com> Subject: Re: Dynamic linking Date: Wed, 7 Jul 1999 12:10:35 +0400 Organization: Agama MIME-Version: 1.0 Content-Type: text/plain; charset="koi8-r" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2314.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG How clever Jhon. I know that a void function cannot return a value, the same is also true of destructors and constractors, to be exact. I asked, how I can make dlopen return an error from the shared object's _init function, and not what value I should return from the void function to fail dlopen. I mean what function shall I call from _init so that dlopen will return error. I am sure it is possible, because dlopen calls _init prior to returning. ----- Original Message ----- From: John Polstra To: Cc: Sent: Tuesday, July 06, 1999 8:59 PM Subject: Re: Dynamic linking > In article <3780AEB2.206160E0@agama.com>, > Andrew Iltchenko wrote: > > Hi everyone! > > > > Is there a way of making dlopen return an error from the shared object's > > _init function? > > No. The _init function by definition is "void _init(void)", and so > it cannot return a value. > > John > -- > John Polstra jdp@polstra.com > John D. Polstra & Co., Inc. Seattle, Washington USA > "No matter how cynical I get, I just can't keep up." -- Nora Ephron To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message