From owner-freebsd-libh Fri Apr 26 17:43:20 2002 Delivered-To: freebsd-libh@freebsd.org Received: from tomts10-srv.bellnexxia.net (tomts10.bellnexxia.net [209.226.175.54]) by hub.freebsd.org (Postfix) with ESMTP id 2361637B400 for ; Fri, 26 Apr 2002 17:43:08 -0700 (PDT) Received: from shall.anarcat.dyndns.org ([65.94.187.200]) by tomts10-srv.bellnexxia.net (InterMail vM.5.01.04.05 201-253-122-122-105-20011231) with ESMTP id <20020427004307.WERL12976.tomts10-srv.bellnexxia.net@shall.anarcat.dyndns.org>; Fri, 26 Apr 2002 20:43:07 -0400 Received: from lenny.anarcat.dyndns.org (lenny.anarcat.dyndns.org [192.168.0.4]) by shall.anarcat.dyndns.org (Postfix) with SMTP id 8E2754; Fri, 26 Apr 2002 20:42:17 -0400 (EDT) Received: by lenny.anarcat.dyndns.org (sSMTP sendmail emulation); Fri, 26 Apr 2002 20:42:04 -0400 Date: Fri, 26 Apr 2002 20:42:03 -0400 From: The Anarcat To: Max Okumoto 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> Mail-Followup-To: The Anarcat , Max Okumoto , freebsd-libh@FreeBSD.ORG References: Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="DocE+STaALJfprDB" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.3.27i Sender: owner-freebsd-libh@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --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 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