On Wed, 24 Jan 2007, Michel Meunier wrote:
> Michael Van Canneyt a écrit :
> > On Wed, 24 Jan 2007, Michel Meunier wrote:
> >
> > [cut code]
> >
> > > xxx
> > > and IT DOESN'T WORK, why? It is exactly the same code!
> > > More and more I
Michael Van Canneyt a écrit :
On Wed, 24 Jan 2007, Michel Meunier wrote:
[cut code]
xxx
and IT DOESN'T WORK, why? It is exactly the same code!
More and more I think I am going to translate my code in C, because FPC seems
unable to manag
Felipe Monteiro de Carvalho a écrit :
Another relevant question: on which directory and how did you install
lazarus/fpc?
d:\lazarus, without any space
Installing on directories with spaces can have nasty effects on the
gnu tools.
--
Michel Meunier
www.etoiles-a-bleau.fr
___
Flávio Etrusco a écrit :
I am trying again without any hope, to use dll in a wondows application.
(...)
More and more I think I am going to translate my code in C, because FPC
seems unable to manage properly dll library.
Thanks for your help.
Do you think whining and shouting "I will turn to C
Felipe Monteiro de Carvalho a écrit :
I tested here and everything worked fine on the Application with a Form.
Further, I´ve written dozens of DLLs with Free Pascal and all worked
fine.
My guess is that there is something wrong with your Setup.
What Windows version are you using?
Windows XP
On Wed, 24 Jan 2007, Michel Meunier wrote:
[cut code]
> xxx
> and IT DOESN'T WORK, why? It is exactly the same code!
> More and more I think I am going to translate my code in C, because FPC seems
> unable to manage properly dll library.
I
Another relevant question: on which directory and how did you install
lazarus/fpc?
Installing on directories with spaces can have nasty effects on the gnu tools.
--
Felipe Monteiro de Carvalho
___
fpc-pascal maillist - fpc-pascal@lists.freepascal.org
I am trying again without any hope, to use dll in a wondows application.
(...)
More and more I think I am going to translate my code in C, because FPC
seems unable to manage properly dll library.
Thanks for your help.
Do you think whining and shouting "I will turn to C" will get you
better repl
I tested here and everything worked fine on the Application with a Form.
Further, I´ve written dozens of DLLs with Free Pascal and all worked fine.
My guess is that there is something wrong with your Setup.
What Windows version are you using?
What FPC and Lazarus versions are you using?
Maybe
Hello,
I am trying again without any hope, to use dll in a wondows application.
It's very strange it's working with console application but not with
windows apllication.
My dll code is very very simple:
library dlltest;
{$mode objfpc}{$H+}
uses
Cla
Op Wed, 24 Jan 2007, schreef Daniel Franzini:
> today (quite late) i've got myself some improvements...so far i was
> unable to even compile some parts od fpc within freedos (inside
> virtual pc)...the IDE that comes with fpc2.0.5 does not even start at
> all...now i can compile correctly all th
today (quite late) i've got myself some improvements...so far i was
unable to even compile some parts od fpc within freedos (inside
virtual pc)...the IDE that comes with fpc2.0.5 does not even start at
all...now i can compile correctly all the packages needed to build the
ide (as Pierre pointed)..
> > However, reliable warning without explanations seems to be a good
> > thing.
> How? I think it's completely useless if you have no idea what it's
> caused by and what to do about it.
> Jonas
Because I know, that I have to fiddle with program structure or something. One
less reason to loo
MSEide+MSEgui version 1.0 is released:
http://mypage.bluewin.ch/msegui/
Have a lot of fun!
Martin
___
fpc-pascal maillist - fpc-pascal@lists.freepascal.org
http://lists.freepascal.org/mailman/listinfo/fpc-pascal
On 24 jan 2007, at 13:01, Пётр Косаревский wrote:
Implementing it for all cases is non-trivial and has low priority.
Actually, implementing the warning is easy, but always adding the
reason why it isn't inlined is more difficult.
I think, that there are many reasons, which will not help me
> > Implementing it for all cases is non-trivial and has low priority.
> Actually, implementing the warning is easy, but always adding the
> reason why it isn't inlined is more difficult.
> Jonas
I think, that there are many reasons, which will not help me a single bit.
However, reliable warni
On 24 jan 2007, at 12:46, Jonas Maebe wrote:
No, inline is and will always only be a hint. There are currently
no provisions in the compiler which allow it to inform you in all
cases where it does not perform the inlining (if you turn on
warnings, it will warn for some cases).
Implementi
On 24 jan 2007, at 12:03, Пётр Косаревский wrote:
Add {$inline on} to your source
So I can be sure, that if it compiles, all inlines are implemented/
forced?
No, inline is and will always only be a hint. There are currently no
provisions in the compiler which allow it to inform you in al
On Wed, 24 Jan 2007 10:49:07 +0100
Jonas Maebe wrote
HASINLINE is simply a temporary internal compiler define which was
introduced to indicate that the compiler supports the "inline"
directive. It is not to be used your own code, since it will be
removed from the compiler (it even has already bee
On 24 jan 2007, at 11:57, Пётр Косаревский wrote:
on. As of 2.1.1, it won't matter anymore either since the compiler
will always accept the inline specifier, but only actually do
something with it if inlining is turned on.
Is there a way to know (in terms of $if etc.) that compiler
actually
> on. As of 2.1.1, it won't matter anymore either since the compiler
> will always accept the inline specifier, but only actually do
> something with it if inlining is turned on.
Is there a way to know (in terms of $if etc.) that compiler actually does
something?
_
On 23 Jan 2007, at 17:19, Alexander Todorov wrote:
What is the name of the conditional when we have inline on?
I thought I can do {$IFDEF HASINLINE} but it doesn't work?
HASINLINE is simply a temporary internal compiler define which was
introduced to indicate that the compiler supports the
22 matches
Mail list logo
