Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-developers-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin-developers AT sources DOT redhat DOT com Date: Mon, 19 Mar 2001 19:17:34 -0500 From: Christopher Faylor To: cygwin-developers AT cygwin DOT com Subject: Re: exceptions Message-ID: <20010319191734.A29768@redhat.com> Reply-To: cygwin-developers AT cygwin DOT com Mail-Followup-To: cygwin-developers AT cygwin DOT com References: <021a01c0b0cb$42253c00$0200a8c0 AT lifelesswks> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.11i In-Reply-To: <021a01c0b0cb$42253c00$0200a8c0@lifelesswks>; from robert.collins@itdomain.com.au on Tue, Mar 20, 2001 at 10:20:38AM +1100 On Tue, Mar 20, 2001 at 10:20:38AM +1100, Robert Collins wrote: >are we able to use c++ exception handling within cygwin1.dll? No, not currently. I don't remember if this doesn't work in DLLs or if it bloated the code alarmingly. >ie to guard against invalid memory access on user supplied parameters? check_null_empty_path is the method for doing that. It validates an address. Probably should change the name... cgf