<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Luís Oliveira wrote:
<blockquote
cite="mid:391f79580908211909m42d56575s6caf7f25bbbf0a11@mail.gmail.com"
type="cite"><br>
<pre wrap=""><!---->
uffi.asd was added by popular demand. (Or maybe it was just *one*
user, I don't recall.) I'd be glad to rename it, but as I've mentioned
in a previous email, I'm worried that it'd do more harm than good.
Suggestions on how to solve the problem are most welcome.
</pre>
</blockquote>
<ol>
<li>As it stands, even using asdf:<b class="moz-txt-star"><span
class="moz-txt-tag">*</span>central-registry<span class="moz-txt-tag">*</span></b><span
class="moz-txt-star"><span class="moz-txt-tag"> is a problem, because
there's no way to use both. Since they both have the same name only one
can exist with it using the asdf system in any normal fashion. <br>
</span></span></li>
<li><span class="moz-txt-star"><span class="moz-txt-tag">Both UFFI
and CFFI have a right to exist. The gcc analogy isn't valid - these
aren't compilers that users expect to be substituting one for another.
It doesn't matter that the CFFI people don't like the style of code
writing that goes on in the ELEPHANT group. They chose to use UFFI for
whatever reason and should have the right to expect that some other
development group won't break their code via the ASDF package system
unless there is a dependency relationship. <br>
</span></span></li>
<li><span class="moz-txt-star"><span class="moz-txt-tag">Since UFFI
came up with the name first, I believe most people would agree they
have a prior right to the name. <br>
</span></span></li>
</ol>
I think you should change the name of your file to <b>uffi-cffi-compat.asd<br>
<br>
</b>Then, inform your users of the fact, and if they were relying on an
implicit use of CFFI in place of UFFI they should change their projects
to <b>explicitly</b> use CFFI by way of this definition file. <br>
<br>
I think it is the right thing to do. <br>
<br>
--Jeff<br>
<br>
<br>
</body>
</html>