Michael Schnell schrieb:
>
> Thanks. Please keep me posted on this issue.
>
http://svn.freepascal.org/svn/logs/fpc-trunk.log
;)
___
fpc-devel maillist - fpc-devel@lists.freepascal.org
http://lists.freepascal.org/mailman/listinfo/fpc-devel
Hi,
Since this weekend the classes unit is based upon the fgl unit. What are the
advantages of this change.
Does it make the code in the classes unit (for example TFPList, TList and
TStringList) faster or does this just improve maintainability, e.g. because changes
made in the fgl unit are a
Luiz Americo Pereira Camara wrote:
While developing with simpleipc i found that there's no
straightforward way to identify the type of a message (see the forth
paragraph of
http://lazarusroad.blogspot.com/2006/12/only-one-instance.html), so i
looked what i could do to improve it.
Look forwa
On Tue, 19 Dec 2006, Vincent Snijders wrote:
> Hi,
>
> Since this weekend the classes unit is based upon the fgl unit. What are the
> advantages of this change.
>
> Does it make the code in the classes unit (for example TFPList, TList and
> TStringList) faster or does this just improve maintai
Hi to all, and excuse me if i'm writing to the wrong list but i just
subrscibed ;)
I got a problem that i'm not able to resolve... i'm using lazarus and
freepascal compiler tools to cross-compile a software i'm developing to
a Pocket PC with Windows 2003 inside.
The system is winCe (widget)
Kris Leech schreef:
Luiz Americo Pereira Camara wrote:
While developing with simpleipc i found that there's no
straightforward way to identify the type of a message (see the forth
paragraph of
http://lazarusroad.blogspot.com/2006/12/only-one-instance.html), so i
looked what i could do to imp
Is there any documentation on simpleipc ?
-Michael
___
fpc-devel maillist - fpc-devel@lists.freepascal.org
http://lists.freepascal.org/mailman/listinfo/fpc-devel
Hello.
I made dylib with FPC (compiled in delphi mode if it is important). I have
functions that I want to export listed in "exports" section, a few hundreds
exported and that works fine but when I run otool it shows me thousands - class
methods, functions, almost everything, and it seems like
On 19 dec 2006, at 15:50, Vlad wrote:
I made dylib with FPC (compiled in delphi mode if it is important).
I have functions that I want to export listed in "exports" section,
a few hundreds exported and that works fine but when I run otool it
shows me thousands - class methods, functions, a
Jonas Maebe schrieb:
>
> On 19 dec 2006, at 15:50, Vlad wrote:
>
>> I made dylib with FPC (compiled in delphi mode if it is important). I
>> have functions that I want to export listed in "exports" section, a
>> few hundreds exported and that works fine but when I run otool it
>> shows me thousan
On 19 dec 2006, at 17:23, Florian Klaempfl wrote:
The reason they are also exported, is that they are global symbols
(i.e., they appear in the interface of a unit). I know the manual
states
that no symbols will be exported unless you mention them in the
export
statement, but afaik this is w
Jonas Maebe schrieb:
>
> On 19 dec 2006, at 17:23, Florian Klaempfl wrote:
>
>>> The reason they are also exported, is that they are global symbols
>>> (i.e., they appear in the interface of a unit). I know the manual states
>>> that no symbols will be exported unless you mention them in the expo
On 19 dec 2006, at 18:04, Jonas Maebe wrote:
All these "T" symbols are exported afaik.
It should be fairly easy to fix for Mac OS X: just make all global
symbols "private extern", then they are only global for other object
files within the same library/binary. This doesn't seem to exist i
13 matches
Mail list logo
