This is the mail archive of the
libstdc++@sources.redhat.com
mailing list for the libstdc++ project.
more include bits
- To: ncm at zembu dot com, ncm at cantrip dot org, libstdc++ at sources dot redhat dot com
- Subject: more include bits
- From: Benjamin Kosnik <bkoz at redhat dot com>
- Date: Wed, 4 Oct 2000 01:11:53 -0700
Kay.
<bkoz@haight> /mnt/hd/bliss/src.gcc/libstdc++-v3/include
%ls -al
total 36k
drwxrwxr-x 9 bkoz bkoz 4.0k Oct 4 01:04 ./
drwxrwxr-x 10 bkoz bkoz 4.0k Oct 4 00:49 ../
drwxrwxr-x 3 bkoz bkoz 4.0k Oct 4 00:15 backward/
drwxrwxr-x 3 bkoz bkoz 4.0k Oct 4 00:15 bits/
drwxrwxr-x 2 bkoz bkoz 4.0k Oct 4 01:04 c/
drwxrwxr-x 2 bkoz bkoz 4.0k Oct 4 01:04 c_std/
drwxrwxr-x 3 bkoz bkoz 4.0k Oct 4 00:15 ext/
drwxrwxr-x 3 bkoz bkoz 4.0k Oct 4 00:15 std/
As the directory structure.
I'm thinking of moving all the includes into one directory, called include.
where
std/
cNAME -> includes bits/std_cNAME.h
and
c/
bits/
std_cNAME.h -> include_next NAME.h
c_std
bits/
std_cNAME.h -> combined shadow header
This seems pretty clear to me, what do you think? (Notice the short
directory names!) Then --enable flags could pick either c_std or c for
the included headers.
This seems like the most sane approach.
-benjamin