Am 22.10.2010 09:18, schrieb Graeme Geldenhuys:
Hi,
If the source code only contains tabs characters, instead of spaces,
does... that means the source code files are a lot smaller. Does that also
result in the compiler parsing those files faster? After all, there is a
lot less characters to
Jonas Maebe schrieb:
What is constref,
A const parameter that is always passed by reference.
What's the guarantee, that (in detail external) subroutines will honor
the const attribute?
AFAIK constref was invented for passing values to external
subroutines, that expect a reference. In
On 22 Oct 2010, at 12:17, Hans-Peter Diettrich wrote:
Jonas Maebe schrieb:
What is constref,
A const parameter that is always passed by reference.
What's the guarantee, that (in detail external) subroutines will
honor the const attribute?
None. const (and constref) is a hint from the
Graeme Geldenhuys schrieb:
If the source code only contains tabs characters, instead of spaces,
does... that means the source code files are a lot smaller. Does that also
result in the compiler parsing those files faster? After all, there is a
lot less characters to parse.
Anybody actually
On 22/10/2010 12:28, Jonas Maebe wrote:
AFAIK constref was invented for passing values to external
subroutines, that expect a reference. In how far does constref
affect the *caller*, in contrast to e.g. var? Can constref pass
properties, which are not allowed as var parameters?
Right now
On Fri, 22 Oct 2010, Mark Morgan Lloyd wrote:
Mark Morgan Lloyd wrote:
The only niggle I've got is that when I tried to build using 2.2 it went
part way through and then barfed because of an out parameter. Could the
compiler version be checked right at the start of the build?
Also trying
On 22 Oct 2010, at 15:09, Martin wrote:
On 22/10/2010 12:28, Jonas Maebe wrote:
AFAIK constref was invented for passing values to external subroutines,
that expect a reference. In how far does constref affect the *caller*, in
contrast to e.g. var? Can constref pass properties, which are
On 22 Oct 2010, at 15:32, Michael Van Canneyt wrote:
On Fri, 22 Oct 2010, Mark Morgan Lloyd wrote:
Also trying to make -j 12 on a 12-CPU system wasn't reliable. I don't
understand the build process well enough to know where to start on that one.
I regularly use make -j 8 and it works fine
On Fri, 22 Oct 2010, Jonas Maebe wrote:
On 22 Oct 2010, at 15:32, Michael Van Canneyt wrote:
On Fri, 22 Oct 2010, Mark Morgan Lloyd wrote:
Also trying to make -j 12 on a 12-CPU system wasn't reliable. I don't
understand the build process well enough to know where to start on that one.
On 22/10/2010 15:24, Jonas Maebe wrote:
On 22 Oct 2010, at 15:09, Martin wrote:
On 22/10/2010 12:28, Jonas Maebe wrote:
AFAIK constref was invented for passing values to external subroutines, that expect a reference.
In how far does constref affect the *caller*, in contrast to e.g. var? Can
On 22/10/2010 15:56, Martin wrote:
On 22/10/2010 15:24, Jonas Maebe wrote:
On 22 Oct 2010, at 15:09, Martin wrote:
On 22/10/2010 12:28, Jonas Maebe wrote:
AFAIK constref was invented for passing values to external
subroutines, that expect a reference. In how far does constref
affect the
On 22 Oct 2010, at 16:35, Michael Van Canneyt wrote:
On Fri, 22 Oct 2010, Jonas Maebe wrote:
The dependencies are specified in the Makefiles themselves.
But manually, if I'm correct ?
Yes.
But what happens if 2 units use each other ?
The dependencies are specified at the package
Jonas Maebe wrote:
On 22 Oct 2010, at 16:35, Michael Van Canneyt wrote:
On Fri, 22 Oct 2010, Jonas Maebe wrote:
The dependencies are specified in the Makefiles themselves.
But manually, if I'm correct ?
Yes.
But what happens if 2 units use each other ?
The dependencies are specified
Jonas Maebe schrieb:
What's the guarantee, that (in detail external) subroutines will honor
the const attribute?
None. const (and constref) is a hint from the programmer that the
argument can be considered by the compiler as constant inside the
called routine.
What about reference
On 22 Oct 2010, at 21:35, Hans-Peter Diettrich wrote:
Jonas Maebe schrieb:
What's the guarantee, that (in detail external) subroutines will honor the
const attribute?
None. const (and constref) is a hint from the programmer that the argument
can be considered by the compiler as constant
Looking to get some resolution to an immediate problem with postgres
component I have...
Field definitions for blob can be mapped to bytea and enable support
for blob data as I am pretty sure byte for byte output/input would
suffice. Some debugging may be needed to make sure we don't need
Hello!
I'm still stuck with cross-compiling fpc from x64 to i386 on an Ubuntu
10.10 machine.
I did:
make distclean;make all;sudo make install PREFIX=/usr;make clean
Worked as expected so far.
Then I did:
make all CPU_TARGET=i386
This build script stops.
Output is:
make compiler_cycle
Benchmarking included 3*10^6 calls to Add and Find methods
with the arguments of various lengths.
Average string length 5 characters:
ShortString: 1.15 s
AnsiString: 1.56 s
Average string length 45 characters:
ShortString: 12.0 s
AnsiString: 3.2 s
I agree that the first case is more relevant
Am 22.10.2010 23:17, schrieb Dariusz Mazur:
full source in attachment (should I prepare it different?)
The best would be a diff against compiler sources.
Second: when I review assembler list I've notice some strange lines (all
optimizations are enabled):
# [124] dec(ii);
movl
19 matches
Mail list logo
