Date: Fri, 26 Apr 2002 20:42:03 -0400 From: The Anarcat <anarcat@anarcat.dyndns.org> To: Max Okumoto <okumoto@ucsd.edu> Cc: freebsd-libh@FreeBSD.ORG Subject: Re: Would anyone object if I made format of *.cd.cc files more strict? Message-ID: <20020427004203.GA315@lenny.anarcat.dyndns.org> In-Reply-To: <hfg01if4yj.fsf@multivac.sdsc.edu> References: <hfg01if4yj.fsf@multivac.sdsc.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
--DocE+STaALJfprDB
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
That's fine with me, I guess. As long as it works as before.
The thing I was hoping though was to get rid of the parser concept
altogether. Wouldn't it be theorically possible to generate those
files from the compiled data itself?
Right now, the parser finds the class names in a given .cd.cc file and
takes them as the members of the subsystem.
Wouldn't it be possible to have a declaration in the .cd.cc file that
would list those classes? I was thinking of something like:
[I am inventing some class names here :)]
vector<ClassNames> disk_classes =3D { "Disk", "DiskChunk", ...};
Then a runtime executable could be linked with the .cd.cc file to
generate the class descriptions files (which is pretty unavoidable).
What does the parser do apart from finding the class names and
generate the code anyways?
Parsing C++ code is the job of the compiler, not a script suite. ;)
But I'm just ranting, and I have no concrete solution, so please feel
free to kill the perl parser in favor of a better one.
A.
--=20
=46rom the age of uniformity, from the age of solitude, from the age of
Big Brother, from the age of doublethink - greetings!
On Fri Apr 26, 2002 at 03:52:20PM -0700, Max Okumoto wrote:
>=20
> I am working on the *.cd.cc parser right now. The goal would be to
> get ride of the perl script and the extra binaries built used to
> create the tcl<->C++ glue code.
>=20
> Max Okumoto
--DocE+STaALJfprDB
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (FreeBSD)
Comment: For info see http://www.gnupg.org
iEYEARECAAYFAjzJ89sACgkQttcWHAnWiGfeaACfZqprRx26ZSQAC74X+f6C83dS
2akAniMAAcUXWvtMz1TZUz7v/syMyY8s
=sKNT
-----END PGP SIGNATURE-----
--DocE+STaALJfprDB--
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-libh" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020427004203.GA315>