Re: CACM article (Feb 2009): "Compiler research: the next 50 years"

Jason Evans <joevans@gmail.com>
Thu, 12 Feb 2009 09:02:06 -0800 (PST)

          From comp.compilers

Related articles
CACM article (Feb 2009): "Compiler research: the next 50 years" idbaxter@semdesigns.com (Ira Baxter) (2009-02-10)
Re: CACM article (Feb 2009): "Compiler research: the next 50 years" max@gustavus.edu (Max Hailperin) (2009-02-11)
Re: CACM article (Feb 2009): "Compiler research: the next 50 years" joevans@gmail.com (Jason Evans) (2009-02-12)
Re: CACM article (Feb 2009): "Compiler research: the next 50 years" max@gustavus.edu (Max Hailperin) (2009-02-14)
Re: CACM article (Feb 2009): "Compiler research: the next 50 years" idbaxter@semdesigns.com (Ira Baxter) (2009-02-14)
Re: CACM article (Feb 2009): "Compiler research: the next 50 years" cfc@shell01.TheWorld.com (Chris F Clark) (2009-02-14)
Re: CACM article (Feb 2009): "Compiler research: the next 50 years" gneuner2@comcast.net (George Neuner) (2009-02-14)
| List of all articles for this month |

From: Jason Evans <joevans@gmail.com>
Newsgroups: comp.compilers
Date: Thu, 12 Feb 2009 09:02:06 -0800 (PST)
Organization: Compilers Central
References: 09-02-027 09-02-034
Keywords: journal
Posted-Date: 14 Feb 2009 05:05:59 EST

On Feb 11, 6:46 am, Max Hailperin <m...@gustavus.edu> wrote:
> > [For those of us whose ACM memberships expired a decade ago, what else
> > does it say? -John]
>
> For those of you, I would point out that you should really take a look
> at the revitalized CACM and decide whether it merits reactivating your
> membership. The CACM has not been so good since the 1970s, and
> depending on your perspective, perhaps not even then.


Indeed, there was recently a sudden major improvement in CACM. I've
been an ACM member off and on since the early 90s (more recently in
order to access the digital library), and this is the first period
during which CACM has ever been of real interest to me.


As far as the compiler research article is concerned, I have mixed
feelings about its message. The basic tenet is that we should be
working together on large systems, and stop wasting so much time
implementing the same infrastructure over and over. The problem with
that is similar to the problem with object-oriented programming and
class reuse: the existing components are rarely a perfect fit for the
project at hand. In each case, the cost/benefit of retrofitting has
to be weighed against the cost/benefit of reimplementation.


Jason Evans



Post a followup to this message

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