|
From: | Daniel J Sebald |
Subject: | Re: Renaming libcruft |
Date: | Fri, 24 Aug 2012 15:14:17 -0500 |
User-agent: | Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.24) Gecko/20111108 Fedora/3.1.16-1.fc14 Thunderbird/3.1.16 |
On 08/24/2012 02:15 PM, Rik wrote:
On 08/24/2012 09:07 AM, John W. Eaton wrote:
libcruft crufty old fortran code (split this into individual component libraries if you prefer and completely eliminate the name libcruft)I would keep the code together since it is a very distinct entity and makes a natural convenience sub-library for liboctave. The fact that it is Fortran really segregates it in my mind from the rest of the C++ sources. I would still change the directory name away from libcruft to libfortran.
The "libcruft" name would be good for items that are really seen as "cruft", i.e., things that would preferably be replaced with something better. If there are some fortran files in there worth holding onto, those could be put in an additional "libfortran" directory.
Dan
[Prev in Thread] | Current Thread | [Next in Thread] |