Hello Marco,
Thursday, November 10, 2005, 10:53:09 AM, you wrote:
Some files of RTL core are under the full GPL license, not a LGPL. Is it
a new politics of FPC?
MvdV No. Must have been an oversight/bad copy/paste.
MvdV If you have more files, don't hesitate to name them. The syscallh.inc
Hello all,
I didn't discuss about this idea but now I would say something. Is it
really important, to integrate templates support into compiler? Maybe
an external preprocessing utility should be better? I think, an
integrated complex preprocessor can slow the compiling process very
much even if a
Hello FPC Team,
Please explain me why my yesterday's work remained be ignored?
Practically, I think, I solved a problem at fixed a bug. Are you
discordant with my way of solution or are waiting for diff?
--
Best regards,
Pavelmailto:[EMAIL PROTECTED]
Hello all,
1) I tried now to build a dll with {$smartlink on} using 1.9.9 compiler
built at beginning of April. The created DLL did not contain export
names. An analysis of generated asm code pointed that although a
global label at beginning of .rva-containing asm-file has been
correctly created
Hello Jonas,
Wednesday, February 16, 2005, 11:24:00 AM, you wrote:
1) Properties for Object type.
Should already work with {$mode Delphi} - if this feature is not
broken again now.
___
fpc-devel maillist - fpc-devel@lists.freepascal.org
Hello Marco,
Wednesday, February 16, 2005, 1:32:58 PM, you wrote:
Currently FPC has special code that forbids property in objects for delphi
mode.
At least Delphi versions from 2 to 7 support propereties for old-style
objects. This feature is used BTW in KOL library. Some years ago I
implemented
Hello all,
Today I built last compiler (1.9.5) from sources. Then I tried to compile a
small test win32 dll with -CX -XX and got a binary without export
functions entries. That is interesting that using -a option (using
external assembler) solves this problem.
--
Best regards,
Pavel
Hello Peter,
Wednesday, April 28, 2004, 4:02:59 PM, you wrote:
Hello all,
I have some ideas about the bug #2363 (Unfixed Error export problem).
Second way: storing exported items info in PPU.
PV That is possible. It needs a new ppuentry that will contain the following
PV items per export:
Hello all,
I have some ideas about the bug #2363 (Unfixed Error export problem).
I see two ways to solve this problem but I'm not sure that I'm able to
realize them.
First way (may be wrong):
generating edata sections (or their analogs for non-Windows platforms)
vor every unit that contains
Hello all,
I found a problem with dynamic arrays of shortstrings and of static
arrays. These structures are not supported in Delphi but usually work
normally in FPC (except this case). But if a dynamic array is declared
as typized constant or a variable with initial value then trying to
resize
Hello all,
I found also a problem with TIniFile (1.9, win32). If I try to read an
information from the same .ini file using standard TIniFile methods
from several instances of application at the same time, sometimes I
get an error opening .INI file. I think, INI file creation flags should
be
I try to download last 1.9 sources but cannot access FPC archives via FTP, your
server (ftp://ftp.freepascal.org) seems to be down. What is happened with it?
--
Best regards,
Pavelmailto:[EMAIL PROTECTED]
___
fpc-devel
Hello Ingmar,
Wednesday, December 24, 2003, 1:21:32 PM, you wrote:
IT Bad news :(
IT Is this true for all {$mode }'s or only {$mode delphi} ?
Why bad, Try to add {$calling oldfpccall} into your source
--
Best regards,
Pavelmailto:[EMAIL PROTECTED]
Hello,
After I replaced in t_win32.pas unit a line 698 - from
exportsSection.concat(Tai_symbol.Create(edatalabel,0));
to
exportsSection.concat(Tai_symbol.Create_Global(edatalabel,0));
the smartlinking of Win32 dlls main modules became possible again.
Sincerely, Pavel
14 matches
Mail list logo
