Template matching, a different perspective

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org>
Subject: Template matching, a different perspective
Date: 2000-07-12 22:53:48
Message-ID: Pine.LNX.4.21.0007130048150.790-100000@localhost.localdomain
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

One thing that occurred to me, if I'm going to rejuggle the templates, why
not name them like the Makefile.${os} and the include/port/${os}.h? We
don't really need two matching logics and no matter how smart we make the
template matching, there's still nothing to be gained if we don't find the
right Makefile.port and include/port/os.h (which we apparently do). So
perhaps get rid of all the fanciness and just use the name detected by the
big case statement at the top of configure.in? (And then treat the subtle
differences *within* the template files.)

--
Peter Eisentraut Sernanders väg 10:115
peter_e(at)gmx(dot)net 75262 Uppsala
http://yi.org/peter-e/ Sweden

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message The Hermit Hacker 2000-07-12 23:01:32 [7.0.2] INDEX' TUPLES != HEAP' ..
Previous Message Tom Lane 2000-07-12 22:53:47 Proposal for aggregate-function cleanups in 7.1