Hi!
As some know.. CompactSysutils contains many functions for embedded or CGI
programmers to use when they don't wish to use full sysutils unit. i.e. anyone
looking for smaller footprint executable.
I've partly described it here:
Maybe it would better be a hint.
Seems reasonable to me.
The unused parameter hint is likewise also unavoidable with function
callback implementations sometimes.
There is a good reason for that the unreachable code is a warning: The compiler
_changes_ your
code by removing the if-branch.
Op Mon, 15 Oct 2007, schreef L:
Hi!
As some know.. CompactSysutils contains many functions for embedded or CGI
programmers to use when they don't wish to use full sysutils unit. i.e. anyone
looking for smaller footprint executable.
I've partly described it here:
Op Mon, 15 Oct 2007, schreef L:
I'm sure we can work together to get this unit shipped with FPC..
RTL or FCL? or wherever FPC team thinks it would be nice.
I'm not in favour of this. Suppose I don't want to use sysutils.
* For inttostr, floattostr I can use val, and str for strtoint,
Peter Vreman wrote:
There is a good reason for that the unreachable code is a warning: The compiler
_changes_ your
code by removing the if-branch. When it is a hint the compiler only has
recognized a pattern, but
it does not modify anything.
It changes it, but semantically it's the same
Micha Nelissen schrieb:
Peter Vreman wrote:
There is a good reason for that the unreachable code is a warning: The
compiler _changes_ your
code by removing the if-branch. When it is a hint the compiler only
has recognized a pattern, but
it does not modify anything.
It changes it, but
Florian Klaempfl wrote:
~ gcc -c test.c
test.c: In function ‘f’:
test.c:3: warning: comparison is always false due to limited range of
data type
test.c:3: warning: comparison is always false due to limited range of
data type
Yes, very annoying in gcc as well. It also warns when a variable is
So I guess the warning stays. We can discuss some extensions which makes
it easier to code such restrictions like merging parts of the tue branch.
Could the warning not simply be switched off and on (or set to some kind
of level) by a {$... line ?
-Michael
Op Mon, 15 Oct 2007, schreef Michael Schnell:
So I guess the warning stays. We can discuss some extensions which makes
it easier to code such restrictions like merging parts of the tue branch.
Could the warning not simply be switched off and on (or set to some kind of
level) by a
Daniel Wrote:
Basically, 2/3 of this unit is duplicated functionality. Interresting
functions I cannot get somewhere else are string and path manipulation
routines like extractfile*, trim*, wraptext.
Yes.. it duplicates functionality because it was a prototype or proof in
concept. I planned
Op Mon, 15 Oct 2007, schreef L:
Daniel Wrote:
Basically, 2/3 of this unit is duplicated functionality. Interresting
functions I cannot get somewhere else are string and path manipulation
routines like extractfile*, trim*, wraptext.
Yes.. it duplicates functionality because it was
On Mon, 15 Oct 2007, Daniël Mantione wrote:
Op Mon, 15 Oct 2007, schreef L:
Daniel Wrote:
Basically, 2/3 of this unit is duplicated functionality. Interresting
functions I cannot get somewhere else are string and path manipulation
routines like extractfile*, trim*,
12 matches
Mail list logo
