On Sun, Feb 2, 2014 at 2:44 AM, Fred van Stappen wrote:
>
>
> Many thanks for that brilliant explanations.
>
> Ok, so i have to re-consider all the unit and forget the oop way and
> re-write more procedural (Yes/No ?).
>
> Yes. The simpler - the better.
summarized here:
http://wiki.freepascal.org
> > Yep, thanks Michael.
> >
> > Hum, may i export dynamic array ?
>
> No, you'll need to export these as (typed) pointers and a count.
>
> Regards,
> Sven
Re-Argh, ok, (and i understand now why the library-examples are so simple
:-) ).
Many thanks for that brilliant explanations.
Ok, so
On 01.02.2014 21:44, Howard Page-Clark wrote:
On 01/02/2014 18:54, Sven Barth wrote:
On 01.02.2014 19:10, Howard Page-Clark wrote:
In a situation where
PPropInfo^.PropType^.Kind=tkMethod
does RTTI enable you to determine the number and/or types of the
parameters that method uses (if any)?
On 01/02/2014 18:54, Sven Barth wrote:
On 01.02.2014 19:10, Howard Page-Clark wrote:
In a situation where
PPropInfo^.PropType^.Kind=tkMethod
does RTTI enable you to determine the number and/or types of the
parameters that method uses (if any)?
Yes, please take a look at the tkMethod part
On 01.02.2014 19:10, Howard Page-Clark wrote:
In a situation where
PPropInfo^.PropType^.Kind=tkMethod
does RTTI enable you to determine the number and/or types of the
parameters that method uses (if any)?
Yes, please take a look at the tkMethod part of the case inside
TTypeData in $fpcdir
In a situation where
PPropInfo^.PropType^.Kind=tkMethod
does RTTI enable you to determine the number and/or types of the
parameters that method uses (if any)?
If not, is there a programmatic way to determine that information apart
from parsing the source?
Howard
___
On 01.02.2014 17:20, Fred van Stappen wrote:
Yep, thanks Michael.
Hum, may i export dynamic array ?
No, you'll need to export these as (typed) pointers and a count.
Regards,
Sven
___
fpc-pascal maillist - fpc-pascal@lists.freepascal.org
http://lis
> > > On Sat, 1 Feb 2014, Fred van Stappen wrote:
> > >
> > > > Hello everybody.
> > > >
> > > > Ok, i jump...
> > >
> > > [snip]
> > >
> > > >
> > > > Stop compil showing error at dot of function TMyClass.
> > > >
> > > > => libtest.pas(14,18) Fatal: Syntax error, ":" expected but "." found
> > >
On Sat, 1 Feb 2014, Fred van Stappen wrote:
> Date: Sat, 1 Feb 2014 17:00:02 +0100
> From: mich...@freepascal.org
> To: fpc-pascal@lists.freepascal.org
> Subject: Re: [fpc-pascal] fp universal library ?
>
>
>
> On Sat, 1 Feb 2014, Fred van Stappen wrote:
>
> > Hello everybody.
> >
> > Ok, i ju
> Date: Sat, 1 Feb 2014 17:00:02 +0100
> From: mich...@freepascal.org
> To: fpc-pascal@lists.freepascal.org
> Subject: Re: [fpc-pascal] fp universal library ?
>
>
>
> On Sat, 1 Feb 2014, Fred van Stappen wrote:
>
> > Hello everybody.
> >
> > Ok, i jump...
>
> [snip]
>
> >
> > Stop compil sh
On Sat, 1 Feb 2014, Fred van Stappen wrote:
Hello everybody.
Ok, i jump...
[snip]
Stop compil showing error at dot of function TMyClass.
=> libtest.pas(14,18) Fatal: Syntax error, ":" expected but "." found
PS : I promise, if i can do the conversion, to create a nice wiki, for dummies
Hello everybody.
Ok, i jump...
I decide to begin the conversion of a unit (wrapper to other libraries + lot of
functions who link those libraries) into a universal fp library.
After Googling a while (and finding very poor doc, only few for Delphi, with
always the hypra-simple same example...),
On Sat, 1 Feb 2014, Martin Schreiber wrote:
Hi,
MSEide+MSEgui version 3.2 has been released:
http://sourceforge.net/projects/mseide-msegui/files/mseide-msegui/3.2/
There is also a new programming course for beginners:
http://sourceforge.net/projects/mseuniverse/files/book/
The example projec
13 matches
Mail list logo
