Mail Archives: cygwin-developers/2002/07/27/18:01:14

Mailing-List: contact cygwin-developers-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-developers-subscribe AT cygwin DOT com>
List-Archive: <>
List-Post: <mailto:cygwin-developers AT cygwin DOT com>
List-Help: <mailto:cygwin-developers-help AT cygwin DOT com>, <>
Sender: cygwin-developers-owner AT cygwin DOT com
Delivered-To: mailing list cygwin-developers AT cygwin DOT com
Message-ID: <02ed01c235b9$7060a900$6132bc3e@BABEL>
From: "Conrad Scott" <Conrad DOT Scott AT dsl DOT pipex DOT com>
To: <cygwin-developers AT cygwin DOT com>
References: <028701c235ac$b1c303f0$6132bc3e AT BABEL> <20020727211653 DOT GA8923 AT redhat DOT com> <02b901c235b5$f9fdfcc0$6132bc3e AT BABEL>
Subject: Re: -fno-rtti
Date: Sat, 27 Jul 2002 23:03:28 +0100
MIME-Version: 1.0
X-Priority: 3
X-MSMail-Priority: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000

"Conrad Scott" <Conrad DOT Scott AT dsl DOT pipex DOT com> wrote:
> Would the alternative of compiling just the cygserver with rtti
> acceptable?  For the problem I've got (which is defining
> operators on a class hierarchy) rolling my own code would
> cost more in terms of space and time than the native C++ rtti.

I've found a way of doing this w/o dynamic_cast (and w/o being too
extremely horrible either), so I'll change over to that and avoid
the issue.  As you said in your reply "I'd rather not make a
conscious decision to do this when it can be avoided."  I'll go
with that :-)

// Conrad

- Raw text -

  webmaster     delorie software   privacy  
  Copyright 2019   by DJ Delorie     Updated Jul 2019