Daniël Mantione schrieb:
The EU software directive says a few words about this matter:
"Protection in accordance with this Directive shall apply to the
expression in any form of a computer program. Ideas and principles which
underlie any element of a computer program, including those which
u
Op Sat, 28 Aug 2010, schreef Dimitri Smits:
Hi,
(just hate it when you send something after re-reading it a few times, and a
minute later you know that there is something important you forgot to ask)
Since objectnames and interfaces are cloned from Delphi everywhere in the
fpc-rtl, I was w
P. S. I know I didn't have to include
-FuE:\lazarus\components\fpprofiler\fpprof\
This log is from an experiment...
___
fpc-devel maillist - fpc-devel@lists.freepascal.org
http://lists.freepascal.org/mailman/listinfo/fpc-devel
Hi,
(just hate it when you send something after re-reading it a few times, and a
minute later you know that there is something important you forgot to ask)
Since objectnames and interfaces are cloned from Delphi everywhere in the
fpc-rtl, I was wondering if this is legitimate use and not a copy
On 2010-08-28 01:38, Graeme Geldenhuys wrote:
Alternatively (though not tested) - you should be able to download a
zip archive of the latest code via this URL:
http://github.com/graemeg/fpprofiler/zipball/HEAD
Tried sample project today. Some a comment and a question:
1) I have a strange e
Hi,
I was wondering if anybody could direct me in the right direction (either mail,
wiki) with regard to following questions.
What I want to do:
Since Delphi 2010, there is a new unit in the RTL that makes RTTI more of a
breeze. I'd like to port (meaning: compatible interface, fpc implementati
In our previous episode, Jonas Maebe said:
>
> > http://www.hu.freepascal.org/fpcircbot/cgifpcbot?channel=fpc&fromdate=2010-08-28&todate=2010-08-28&linecount=50&fromtime=14%3A20&totime=15%3A00&sender=&msg=
>
> Probably being predictable again:
Don't read too much into that.
> I don't like the a
On 28 Aug 2010, at 14:54, Joost van der Sluis wrote:
> I would say 'constref'. But what do you thing of the idea from Marco to
> use a directive? It will avoid problems with Delphi-compatibility.
>
> http://www.hu.freepascal.org/fpcircbot/cgifpcbot?channel=fpc&fromdate=2010-08-28&todate=2010-08
On Sat, 2010-08-28 at 14:39 +0200, Jonas Maebe wrote:
> On 28 Aug 2010, at 13:59, Joost van der Sluis wrote:
>
> > Now I see three options: pass all records with a size bigger then the
> > register-size by reference for all cdecl-params which are defined as
> > 'const'. The same happens for stdcal
On 28 Aug 2010, at 13:59, Joost van der Sluis wrote:
> Now I see three options: pass all records with a size bigger then the
> register-size by reference for all cdecl-params which are defined as
> 'const'. The same happens for stdcall parameters on Windows and this is
> suggested before by some
On Sat, 2010-08-28 at 14:14 +0200, Marco van de Voort wrote:
> In our previous episode, Joost van der Sluis said:
> >
> > Now I see three options: pass all records with a size bigger then the
> > register-size by reference for all cdecl-params which are defined as
> > 'const'. The same happens for
In our previous episode, Joost van der Sluis said:
>
> Now I see three options: pass all records with a size bigger then the
> register-size by reference for all cdecl-params which are defined as
> 'const'. The same happens for stdcall parameters on Windows and this is
> suggested before by some p
Hi all,
The safecall calling convention is now implemented for i386/linux in
fpc-trunk. The next step to get XPCom working now is to update the
QueryInterface (and AddRef and ReleaseRef) definitions in IInterface.
Problem is that they are defined as 'stdcall' but to make them work on
Linux/i386 t
In our previous episode, Hans-Peter Diettrich said:
> > Doesn't that depend on filemode? I see a lot of places in the compiler where
> > it is read/changed/preserved:
> [...]
> > None of them in options. So there could be something to it, specially since
> > it is so early in the startup.
>
> IMO
Several type redefinitions are reported in compiling the compiler, can
these be removed?
Most types (PByte...) are declared in systemh.inc and objpash.inc. I'm
not sure, but can't these redefinitions be excluded conditionally, for
e.g. mode OBJPAS (as set for the compiler)?
DoDi
___
Marco van de Voort schrieb:
Doesn't that depend on filemode? I see a lot of places in the compiler where
it is read/changed/preserved:
[...]
None of them in options. So there could be something to it, specially since
it is so early in the startup.
IMO we should add an (optional?) filemode pa
On 2010-08-28 01:38, Graeme Geldenhuys wrote:
Yes, I placed in on GitHub. You can clone the repository as follows:
via git protocol (faster):
git clone git://github.com/graemeg/fpprofiler.git
via http protocol:
git clone http://github.com/graemeg/fpprofiler.git
Alternatively (thou
On 28 Aug 2010, at 12:15, Martin wrote:
> On 28/08/2010 10:59, Jonas Maebe wrote:
>> On 28 Aug 2010, at 01:07, Martin wrote:
>>> But *if* fpc does lock the fpc.cfg file exclusively ( for a very short time
>>> only, e.g. just open+lock, read, close), then there is the slim chance of a
>>> confli
In our previous episode, Jonas Maebe said:
> > But *if* fpc does lock the fpc.cfg file exclusively ( for a very short
> > time only, e.g. just open+lock, read, close), then there is the slim
> > chance of a conflict, and this error could be explained.
>
> FPC opens it as a regular text file usin
On 28/08/2010 10:59, Jonas Maebe wrote:
On 28 Aug 2010, at 01:07, Martin wrote:
But *if* fpc does lock the fpc.cfg file exclusively ( for a very short time
only, e.g. just open+lock, read, close), then there is the slim chance of a
conflict, and this error could be explained.
FPC opens it as
On 28 Aug 2010, at 01:07, Martin wrote:
> But *if* fpc does lock the fpc.cfg file exclusively ( for a very short time
> only, e.g. just open+lock, read, close), then there is the slim chance of a
> conflict, and this error could be explained.
FPC opens it as a regular text file using a regular
21 matches
Mail list logo
