In our previous episode, Graeme Geldenhuys said:
> > Just in case: not Delphi compatible.
>
> In this case I can't use it, because this project must stay Delphi
> compatible. Still a very useful tip though. Thanks again.
Then you must test with $ifopt, set a define if it is enabled, and then
rest
On 2014-04-06 13:41, Sven Barth wrote:
>
> Pop will restore the state that it was at the Push directive.
My appologies, I completely forgot about that. Thanks for reminding me.
I've made a note in my offline documentation so as not to forget this
tip again.
> Just in case: not Delphi compatible
Am 06.04.2014 12:42 schrieb "Graeme Geldenhuys" <
mailingli...@geldenhuys.co.uk>:
> My usage of the $HINTS directive was to switch hints off for one or more
> lines of code, then switch hints back on. An example of this would be
> around the FillChar() call.
I wrote you that already some time ago:
On Sun, April 6, 2014 02:59, Graeme Geldenhuys wrote:
Hi Graeme,
>> file). This is just to check if the behaviour depends on the compiled
>> sources in any way.
>
> You were on to something. Using your simple unit as an example, all the
> various -v options work perfectly.
.
.
> So there was n
Hi Tomas,
On 2014-04-05 23:39, Tomas Hajny wrote:
> file). This is just to check if the behaviour depends on the compiled
> sources in any way.
You were on to something. Using your simple unit as an example, all the
various -v options work perfectly.
That made me double check the code I'm compil
On Sat, April 5, 2014 21:13, Graeme Geldenhuys wrote:
> On 2014-04-05 17:00, Sven Barth wrote:
>>
>> Could you test by disabling the usage of a config file (-n)? You'll need
>> to pass all paths using -Fu then,
>
> No problem. Just did the test with -n and it made no difference when it
> comes to t
On 2014-04-05 17:00, Sven Barth wrote:
>
> Could you test by disabling the usage of a config file (-n)? You'll need
> to pass all paths using -Fu then,
No problem. Just did the test with -n and it made no difference when it
comes to the -v parameter options. The -vh- , -vw- and -v0 parameters
ar
On 2014-04-05 16:23, Jonas Maebe wrote:
>
> -ve does not switch anything off, it only enables showing errors
Ah, now I understand. Thanks for the info.
For an immediate solution (work-around), I enabled message numbers
(-vq), and then created a long list of -vm[x],[y] options to suppress
the mes
On Sat, April 5, 2014 17:26, Michael Van Canneyt wrote:
>
>
> On Sat, 5 Apr 2014, Jonas Maebe wrote:
>
>> On 05/04/14 15:11, Graeme Geldenhuys wrote:
>>> On 2014-04-05 13:07, Jonas Maebe wrote:
>
>-v- doesn't do anything, it's -v0 that should switch off all output
>(except for errors
On 05.04.2014 15:18, Graeme Geldenhuys wrote:
On 2014-04-05 13:09, Pierre Free Pascal wrote:
$FPC -va -h | grep "Reading options from"
and check which configuration file is loaded.
That is pretty much what I did...
--
[freebsd (tiopf2)]$ fpc -va -h | grep "Reading options
On Sat, 5 Apr 2014, Jonas Maebe wrote:
On 05/04/14 15:11, Graeme Geldenhuys wrote:
On 2014-04-05 13:07, Jonas Maebe wrote:
>
>-v- doesn't do anything, it's -v0 that should switch off all output
>(except for errors and fatal errors).
Thanks. So what is the difference between -ve and -v0?
-
On 05/04/14 15:11, Graeme Geldenhuys wrote:
On 2014-04-05 13:07, Jonas Maebe wrote:
>
>-v- doesn't do anything, it's -v0 that should switch off all output
>(except for errors and fatal errors).
Thanks. So what is the difference between -ve and -v0?
-ve does not switch anything off, it only en
On 2014-04-05 13:09, Pierre Free Pascal wrote:
> $FPC -va -h | grep "Reading options from"
> and check which configuration file is loaded.
That is pretty much what I did...
--
[freebsd (tiopf2)]$ fpc -va -h | grep "Reading options from"
[0.000] Reading options from file /home/
On 2014-04-05 13:07, Jonas Maebe wrote:
>
> -v- doesn't do anything, it's -v0 that should switch off all output
> (except for errors and fatal errors).
Thanks. So what is the difference between -ve and -v0? From the compiler
help output it sounds like they do the same thing. But neither of them
On 2014-04-05 13:36, Marco van de Voort wrote:
> I doubt it, filtering log output isn't really platform dependent.
That is what I assume too. So the issue is probably across all platforms
then (but I haven't tested elsewhere yet).
Regards,
- Graeme -
--
fpGUI Toolkit - a cross-platform GUI
In our previous episode, Graeme Geldenhuys said:
> > maybe it's loading some config file anyway.
> > Do a strace and see if it opens a config file.
>
> 'strace' is not available/supported by 64-bit FreeBSD (only 32-bit
> FreeBSD).
That's because it is a port. The normal tool to use on BSDs is k
; Envoyé : vendredi 4 avril 2014 19:42
> À : fpc-pascal@lists.freepascal.org
> Objet : Re: [fpc-pascal] How to remove verbose compiler output
>
> On 2014-04-04 15:32, Henry Vermaak wrote:
> >
> > I use -vi-n-h- for my release builds, which removes info, notes and
> >
On 05/04/14 13:29, Graeme Geldenhuys wrote:
That is the only config file it found and loaded. That config file
contains a -v- option, but even removing that option completely makes no
difference.
-v- doesn't do anything, it's -v0 that should switch off all output
(except for errors and fatal e
On 2014-04-05 11:48, Michael Van Canneyt wrote:
>
> maybe it's loading some config file anyway.
> Do a strace and see if it opens a config file.
'strace' is not available/supported by 64-bit FreeBSD (only 32-bit
FreeBSD). But I did remember that FPC has a very verbose output option.
Amazingly tha
On Fri, 4 Apr 2014, Graeme Geldenhuys wrote:
On 2014-04-04 15:32, Henry Vermaak wrote:
I use -vi-n-h- for my release builds, which removes info, notes and
hints, otherwise it becomes hard to see the wood from the trees!
Exactly what I want to try and do, but it seems FPC is really stubborn
On 2014-04-04 15:32, Henry Vermaak wrote:
>
> I use -vi-n-h- for my release builds, which removes info, notes and
> hints, otherwise it becomes hard to see the wood from the trees!
Exactly what I want to try and do, but it seems FPC is really stubborn
under FreeBSD. I tried the exact same -v para
On Fri, April 4, 2014 05:03, Graeme Geldenhuys wrote:
> Hi,
>
> I'm trying to reduce the compiler output for cron jobs.
>
> I have tried to specify -v0 or even -v- -v0 but still the compiler
> outputs loads of 'Hint' and 'Warning' message about unused parameters,
> unused units, deprecated meth
On Fri, Apr 04, 2014 at 04:03:10AM +0100, Graeme Geldenhuys wrote:
> Hi,
>
> I'm trying to reduce the compiler output for cron jobs.
>
> I have tried to specify -v0 or even -v- -v0 but still the compiler
> outputs loads of 'Hint' and 'Warning' message about unused parameters,
> unused units,
23 matches
Mail list logo
