Am 18.11.2010 15:27, schrieb Thaddy:
On 18-11-2010 13:21, Žilvinas Ledas wrote:
But it might be an advantage for some projects as the discussions
over the years implied.
What about using GC for fpc itself? If it is usable for fpc, then the
problem of fpc leaking memory when compilation
On Fri, 19 Nov 2010, Florian Klaempfl wrote:
Am 18.11.2010 15:27, schrieb Thaddy:
On 18-11-2010 13:21, Žilvinas Ledas wrote:
But it might be an advantage for some projects as the discussions
over the years implied.
What about using GC for fpc itself? If it is usable for fpc, then the
It works, but there is a small problem: the compiler itself is a
nightmare for any heap manager and it shows*THE* disadvantages of GC:
it is sloow.
Compiling the system unit with the default heap manager:
0.4 sec
with the BoehmGC port
98.9 sec (creates a ppu, but crashes on exit)
On Thu, Nov 18, 2010 at 10:39 AM, Felipe Monteiro de Carvalho
felipemonteiro.carva...@gmail.com wrote:
cd fpcbuild/fpcsrc
svn merge -r 15670:15671 http://svn.freepascal.org/svn/fpc/trunk/
Is this correct?
No, that doesn't work because fpcsrc is not a working copy =(
So I just applied the fix
Hello FPC,
In fpc 2.5.1 trunk today the QueryInterface in rtl\inc\objpash.inc is
defined as:
IUnknown = interface
['{---C000-0046}']
function QueryInterface({$IFDEF FPC_HAS_CONSTREF}constref{$ELSE}const{$ENDIF}
iid : tguid;out obj) : longint;{$IFNDEF
On Fri, 2010-11-19 at 12:37 +0100, Felipe Monteiro de Carvalho wrote:
On Thu, Nov 18, 2010 at 10:39 AM, Felipe Monteiro de Carvalho
felipemonteiro.carva...@gmail.com wrote:
cd fpcbuild/fpcsrc
svn merge -r 15670:15671 http://svn.freepascal.org/svn/fpc/trunk/
Is this correct?
No, that
Now it builds the docs, but then it fails to build the RPM =(
Processing files: fpc-2.4.2-1
Finding Provides: /usr/lib/rpm/mandriva/filter.sh ' ' ' '
'/home/felipe/Programas/fpcbuild/build/rpm/BUILDROOT/fpc-2.4.2-1.i386'
/usr/lib/rpm/mandriva/find-provides
Finding Requires:
In our previous episode, Felipe Monteiro de Carvalho said:
cd fpcbuild/fpcsrc
svn merge -r 15670:15671 http://svn.freepascal.org/svn/fpc/trunk/
Is this correct?
No, that doesn't work because fpcsrc is not a working copy =(
So I just applied the fix manually since it is very simple:
Ok,
You can download Free Pascal 2.4.2 for Mandriva Linux here:
http://magnifier.sourceforge.net/tmp/fpc-2.4.2-1mandriva.i386.rpm
It build Lazarus, LNet, EpikTimer and OpenPoker fine. Generics are working too.
thanks,
--
Felipe Monteiro de Carvalho
Ah, I forgot to add the requires list:
Requires: bash libc.so.6 libc.so.6(GLIBC_2.0) libc.so.6(GLIBC_2.1)
libc.so.6(GLIBC_2.1.3) libc.so.6(GLIBC_2.2.3) libc.so.6(GLIBC_2.3)
libc.so.6(GLIBC_2.3.4) libdl.so.2 libdl.so.2(GLIBC_2.0)
libdl.so.2(GLIBC_2.1) libm.so.6 libm.so.6(GLIBC_2.0) libncurses.so.5
On Fri, 2010-11-19 at 12:39 +0100, José Mejuto wrote:
Hello FPC,
In fpc 2.5.1 trunk today the QueryInterface in rtl\inc\objpash.inc is
defined as:
IUnknown = interface
['{---C000-0046}']
function QueryInterface({$IFDEF
On Fri, 2010-11-19 at 12:49 +0100, Felipe Monteiro de Carvalho wrote:
Now it builds the docs, but then it fails to build the RPM =(
Processing files: fpc-2.4.2-1
Finding Provides: /usr/lib/rpm/mandriva/filter.sh ' ' ' '
'/home/felipe/Programas/fpcbuild/build/rpm/BUILDROOT/fpc-2.4.2-1.i386'
On Fri, Nov 19, 2010 at 8:39 AM, José Mejuto joshy...@gmail.com wrote:
Hello FPC,
In fpc 2.5.1 trunk today the QueryInterface in rtl\inc\objpash.inc is
defined as:
IUnknown = interface
['{---C000-0046}']
function QueryInterface({$IFDEF
In our previous episode, Joost van der Sluis said:
1: Change the behavior of const-parameters. That can lead to
unpredictable problems which are not noticed by the compiler. It could
be an option to use some setting to define the behavior of 'const', but
in that case that setting have to be
On Fri, 2010-11-19 at 13:34 +0100, Marco van de Voort wrote:
In our previous episode, Joost van der Sluis said:
1: Change the behavior of const-parameters. That can lead to
unpredictable problems which are not noticed by the compiler. It could
be an option to use some setting to define the
Hello Joost,
Friday, November 19, 2010, 1:02:59 PM, you wrote:
JvdS Well, this issue leaded to a large discussion elsewhere. I was wondering
JvdS when someone else would even notice this incompatibility. A lot of
JvdS alternatives have been discussed, but I coud not find any which is less
JvdS
In our previous episode, Joost van der Sluis said:
Only code that actually overrides those methods, not all interface code.
No, also the places where QueryInterface is called. Because the caller
need to know that it has to pass the GUID by reference, not value. So
the caller need to know
Henry Vermaak wrote:
On 15/11/10 13:13, Paul Breneman wrote:
Michael Schnell wrote:
On 11/14/2010 03:09 AM, Paul Breneman wrote:
This web page has i386 Win32 and ARM WinCE cross-compiler zips that
include everything needed (no install necessary) to test FPC 2.4.2
with the fpGUI 0.7 release
19.11.2010 20:33, Joost van der Sluis wrote:
No, also the places where QueryInterface is called. Because the caller
need to know that it has to pass the GUID by reference, not value. So
the caller need to know that 'const' actually means 'constref' in this
case.
Can const = constref on stdcall
On 19 Nov 2010, at 17:18, Paul Ishenin wrote:
Can const = constref on stdcall convention?
Only on Windows, because on other platforms that would change the
meaning of existing stdcall routines (and on all non-i386 platforms,
the default calling convention is pocall_stdcall).
Jonas
On 19 Nov 2010, at 17:38, Jonas Maebe wrote:
On 19 Nov 2010, at 17:18, Paul Ishenin wrote:
Can const = constref on stdcall convention?
Only on Windows, because on other platforms that would change the
meaning of existing stdcall routines (and on all non-i386 platforms,
the default
19.11.2010 23:47, Jonas Maebe wrote:
Well, it could be done since const is implementation-dependent, but
it would force all non-x86 platforms to pass all const parameters by
reference by default, which may not be desirable from an efficiency
point of view.
As I understand not all const
If debug info is written to a file on windows, are filenames encoded as
utf8, or in system-ascii ?
gdb returns \344 for a umlaut = that looks like ascii
but it also happens to be the unicode codepoint E4 (
http://www.utf8-chartable.de/unicode-utf8-table.pl?unicodeinhtml=dechtmlent=1
)
Paul Ishenin schrieb:
Well, it could be done since const is implementation-dependent, but
it would force all non-x86 platforms to pass all const parameters by
reference by default, which may not be desirable from an efficiency
point of view.
As I understand not all const parameters are passed
24 matches
Mail list logo
