On Thu, Dec 18, 2014 at 4:55 AM, Heikki Linnakangas
wrote:
> If .lp and .ypp files are supposed to be Bison and Flex files with C++ code
> in them, it wouldn't work anyway, because the rules elsewhere in the MSVC
> scripts just check for /\.y$/) to decide whether to run bison on it.
>
> I committe
On 11/27/2014 06:39 AM, Michael Paquier wrote:
On Thu, Nov 27, 2014 at 1:40 AM, Tom Lane wrote:
Andrew Dunstan writes:
This doesn't seem to me to be terribly well expressed (I know it's not your
fault, quite possibly it's mine.) Perhaps we should replace
[r]?[cyl](pp)?
with
(c|cpp|
On Thu, Nov 27, 2014 at 1:40 AM, Tom Lane wrote:
> Andrew Dunstan writes:
>> This doesn't seem to me to be terribly well expressed (I know it's not your
>> fault, quite possibly it's mine.) Perhaps we should replace
>> [r]?[cyl](pp)?
>> with
>> (c|cpp|y|l|rc)
>
> +1 ... the original codi
Andrew Dunstan writes:
> This doesn't seem to me to be terribly well expressed (I know it's not your
> fault, quite possibly it's mine.) Perhaps we should replace
> [r]?[cyl](pp)?
> with
> (c|cpp|y|l|rc)
+1 ... the original coding is illegible already, not to mention wrong
since it will
On 11/25/2014 11:46 PM, Michael Paquier wrote:
Hi all,
In the stuff I work on in a daily basis there are a couple of
extensions written in C++, compiling them with MSVC on Windows using
slightly-different scripts available in src/tools after copying them
directly in contrib/. However, the build
Hi all,
In the stuff I work on in a daily basis there are a couple of
extensions written in C++, compiling them with MSVC on Windows using
slightly-different scripts available in src/tools after copying them
directly in contrib/. However, the build scripts available in
src/tools/msvc are not able
