Hi Johan:

I was thinking of conflicting class names. You are right that 
this would justify qualified class names in cds.

Do you mean a syntax like:

A = *extends* 'netscape.util.Button'.

?

That would be a good way to do it.

I thought that such class conflicts are unlikely and therefore
the current solution is good. But experience will tell.

-- Karl


	From johan@ccs.neu.edu Tue Feb 25 10:34:47 1997
	From: Johan Ovlinger <johan@ccs.neu.edu>
	To: lieber@ccs.neu.edu
	CC: dmann@mars.org, dougo@ccs.neu.edu, lieber@ccs.neu.edu
	Subject: Re: There must be a better way....

	Ok, so replying to mail before having read the entire thread is not
	always the best method. I still think that there is a case to be made
	for fully qualified classnames in cd files. One case would be where
	you want to use two external classes with the same name, but from
	differing packages. Unless java has some sort of renaming gunk (in
	haskell one can say:
	  import Foo renaming blarg to blox
	) but the machinery to support this is nasty.

	So. I guess I'm suggesting extending demjava.cd to modify along the
	lines of:
	 ClassName =Ident | QuotedIdent.
	 QuotedIdent = "'" Ident "'".

	This should insulate the internal periods enough, I think, from EOC. 

	Johan