Re: Semantic error recovery

geoff@flash.bellcore.com (Geoffrey Clemm)
Sun, 28 Nov 1993 03:48:02 GMT

          From comp.compilers
Related articles
[9 earlier articles]
Re: Semantic error recovery kanze@us-es.sel.de (James Kanze) (1993-11-15)
Re: Semantic error recovery delano@snake.CS.Berkeley.EDU (1993-11-17)
Re: Semantic error recovery bill@amber.csd.harris.com (1993-11-17)
Re: Semantic error recovery weberwu@inf.fu-berlin.de (1993-11-18)
Re: Semantic error recovery bj@hatch.socal.com (1993-11-22)
Re: Semantic error recovery sommerfeld@apollo.hp.com (1993-11-23)
Re: Semantic error recovery geoff@flash.bellcore.com (1993-11-28)
Re: Semantic error recovery bill@amber.csd.harris.com (1993-12-01)
Re: Semantic error recovery geoff@flash.bellcore.com (1993-12-04)
| List of all articles for this month |
Newsgroups: comp.compilers
From: geoff@flash.bellcore.com (Geoffrey Clemm)
Keywords: tools
Organization: Bellcore
References: 93-11-102 93-11-118
Date: Sun, 28 Nov 1993 03:48:02 GMT

bill@amber.csd.harris.com (Bill Leonard) writes:
      Also, the speed of the compilation is not the only consideration. Most
      people working on larger projects tend to use make (or something similar).
      If you have hundreds of source files, it can take a long time for each
      "compilation", because make has to check to see which of those hundreds of
      source files need recompilation. If your source is also being accessed
      across a network, it can be even worse.


If you are encountering this problem, you might want to consider switching
from "make" to "odin" (found in pub/Odin/odin.tar.Z from bellcore.com -
192.4.13.90). When used with an editor like emacs, Odin accepts notifications
about files being changed, and only looks at those files when building.


Cheers,


Geoff
--
geoff@bellcore.com
--

Post a followup to this message

Return to the comp.compilers page.
Search the comp.compilers archives again.