This is the mail archive of the kawa@sourceware.org mailing list for the Kawa project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: cond-expand feature testing for presence of a Java class

From: Per Bothner <per at bothner dot com>
To: kawa at sourceware dot org
Date: Sun, 10 Apr 2011 19:00:50 -0700
Subject: Re: cond-expand feature testing for presence of a Java class
References: <F7EC14B8-FA08-410A-A966-48DD299DBB3D@theptrgroup.com> <4D990F6E.5050008@bothner.com> <0203FC98-7B10-4EE5-9C20-E1D66EA40149@theptrgroup.com> <5450113A-7E9D-419F-BDA1-1DF90AB10CDD@theptrgroup.com> <4D996556.3070504@bothner.com> <7E4BD012-9FE8-4A71-8B64-46AFA32715EA@theptrgroup.com>

On 04/04/2011 06:18 AM, Jamison Hope wrote:

I have no objection to class-exists:CLASS_NAME as the syntax. It's a
little on the long side, but it does make the intended meaning of the
corresponding cond-expand feature requirement fairly self-evident.


I checked this in.
--
	--Per Bothner
per@bothner.com   http://per.bothner.com/

References:
- cond-expand feature testing for presence of a Java class
  - From: Jamison Hope
- Re: cond-expand feature testing for presence of a Java class
  - From: Per Bothner
- Re: cond-expand feature testing for presence of a Java class
  - From: Jamison Hope
- Re: cond-expand feature testing for presence of a Java class
  - From: Jamison Hope
- Re: cond-expand feature testing for presence of a Java class
  - From: Per Bothner
- Re: cond-expand feature testing for presence of a Java class
  - From: Jamison Hope

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]