Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!spool2.mu.edu!uunet!bria!mike
From: mike@bria
Newsgroups: comp.lang.c
Subject: Re: Splitting (Turbo C) library modules
Keywords: libraries, modules
Message-ID: <367@bria>
Date: 19 Jan 91 21:35:47 GMT
References: <1991Jan12.222446.26899@odin.diku.dk> <350@bria> <19618@hydra.gatech.EDU> <27@christmas.UUCP>
Reply-To: mike@bria.UUCP (Michael Stefanik)
Distribution: comp
Organization: Briareus Corporation, Los Angeles, CA
Lines: 19

In article <27@christmas.UUCP> rtm@island.COM (Richard Minner) writes:
>Actually, I think it could really be handled by a smart enough editor,
>assuming an OS with decent directory structure.  If an editor allowed
>you to group several `physical' files together as one `logical' file
>for editing, it would make maintaining such broken up libraries much
>easier.  (I've occasionally resorted to catting files together, editing,
>then breaking them apart.)

Why not simply write a program that looks for a special comment, such
as /*FUNCTION fubar*/ that would extract the code into a file, fubar.c,
stop when the next /*FUNCTION*/ comment was found, compile fubar.c, and
add it to a library?  You could compare the date of the source with the
date of the object to see if recompilation is really needed.
-- 
Michael Stefanik, Systems Engineer (JOAT), Briareus Corporation
UUCP: ...!uunet!bria!mike
--
technoignorami (tek'no-ig'no-ram`i) a group of individuals that are constantly
found to be saying things like "Well, it works on my DOS machine ..."