Re: RFC: library entry name collision

2002-10-07 Thread Juergen Boemmels
Dan Sugalski <[EMAIL PROTECTED]> writes: > At 9:37 PM -0400 9/29/02, Mike Lambert wrote: > >intlist is not the only culprit. ./classes/key.c and ./key.c have a > >similar problem. > > Then let's start a convention. > > Classes start with a CL_ prefix, encodings with an EN_ prefix, and > charact

RE: RFC: library entry name collision

2002-10-06 Thread Dan Sugalski
At 11:51 PM -0700 10/5/02, Brent Dax wrote: >Dan Sugalski: ># At 9:37 PM -0400 9/29/02, Mike Lambert wrote: ># >intlist is not the only culprit. ./classes/key.c and ./key.c have a ># >similar problem. ># ># Then let's start a convention. ># ># Classes start with a CL_ prefix, encodings with an EN_

RE: RFC: library entry name collision

2002-10-05 Thread Brent Dax
Dan Sugalski: # At 9:37 PM -0400 9/29/02, Mike Lambert wrote: # >intlist is not the only culprit. ./classes/key.c and ./key.c have a # >similar problem. # # Then let's start a convention. # # Classes start with a CL_ prefix, encodings with an EN_ prefix, and # character set stuff starts with a

Re: RFC: library entry name collision

2002-10-01 Thread Dan Sugalski
At 9:37 PM -0400 9/29/02, Mike Lambert wrote: >intlist is not the only culprit. ./classes/key.c and ./key.c have a >similar problem. Then let's start a convention. Classes start with a CL_ prefix, encodings with an EN_ prefix, and character set stuff starts with a CS_ prefix. --

Re: RFC: library entry name collision

2002-09-29 Thread Mike Lambert
> I was beating my head on the wall yesterday trying to figure out why > an intlist test was failing on a freshly updated source tree. (I > rarely use 'make clean', because that's almost always just covering up > dependency problems.) I'll leave out the gory details, but the problem > boiled down

RFC: library entry name collision

2002-09-29 Thread Steve Fink
I was beating my head on the wall yesterday trying to figure out why an intlist test was failing on a freshly updated source tree. (I rarely use 'make clean', because that's almost always just covering up dependency problems.) I'll leave out the gory details, but the problem boiled down to parrot/