On Tue, 24 Sep 2013 14:28:42 +0200
Sven Barth wrote:
> Am 24.09.2013 14:17, schrieb Mattias Gaertner:
> > Hi,
> >
> > When calling "fpc -d foo test.pas" there are two mistakes:
> > First the -d parameter is missing a value, which fpc silently ignores.
> > And second there are two files to compile
On 24 Sep 2013, at 14:34, Mattias Gaertner wrote:
On Tue, 24 Sep 2013 14:23:52 +0200
Jonas Maebe wrote:
By design, FPC gives a warning (not a hint) when two file names are
specified.
You are right, it is a warning.
Why not an error?
FPC used to silently ignore multiple file names, so I a
On Tue, 24 Sep 2013 14:23:52 +0200
Jonas Maebe wrote:
>
> On 24 Sep 2013, at 14:17, Mattias Gaertner wrote:
>
> > When calling "fpc -d foo test.pas" there are two mistakes:
> > First the -d parameter is missing a value, which fpc silently ignores.
> > And second there are two files to compile.
Am 24.09.2013 14:17, schrieb Mattias Gaertner:
Hi,
When calling "fpc -d foo test.pas" there are two mistakes:
First the -d parameter is missing a value, which fpc silently ignores.
And second there are two files to compile. FPC ignores that too, gives
a hint, but compiles anyway.
Design or bug?
On 24 Sep 2013, at 14:17, Mattias Gaertner wrote:
When calling "fpc -d foo test.pas" there are two mistakes:
First the -d parameter is missing a value, which fpc silently ignores.
And second there are two files to compile. FPC ignores that too, gives
a hint, but compiles anyway.
Design or bug?
