On 17 May 2012, at 23:32, Joost van der Sluis wrote:
> I'm trying to implement extended RTTI property attributes as supported
> by recent Delphi versions.
Please add this functionality first to a separate branch for easier reviewing.
Thanks,
Jonas__
On Fri, May 18, 2012 at 12:16 PM, Joost van der Sluis wrote:
> I think I can. But in Delphi you can also give a non-exsisting
> attribute, ie:
>
> TMyClass=class
> private
> FName: string;
> published
> [TThisTypeIsNowhereDefined('You','Can','Enter','Anything','here'1)]
> property Name
On Fri, 2012-05-18 at 11:31 +0200, Sven Barth wrote:
> Am 18.05.2012 09:49 schrieb "Joost van der Sluis" :
> > Also not. (I know, it is strange behavior. But there are more
> strange
> > things, as there is no type-checking in attributes. It seems like
> they
> > just hacked this together rather qu
Am 18.05.2012 09:49 schrieb "Joost van der Sluis" :
> Also not. (I know, it is strange behavior. But there are more strange
> things, as there is no type-checking in attributes. It seems like they
> just hacked this together rather quickly...)
>
You mean typechecking regarding the constructor argu
18.05.2012 15:49, Joost van der Sluis написал:
Indeed. And I do have the symbol of the corresponding type and a list of
parameters already. I thought I needed a symbol/definition to store the
references. Else I would have to store those references in the
TPropertySym, but also in the symbol of t
On Fri, 2012-05-18 at 15:13 +0800, Paul Ishenin wrote:
> 18.05.2012 14:23, Joost van der Sluis wrote:
>
> > This information can be bound to a properties but also whole classes at
> > least. (I'll have to test for methods and public fields) So no, not only
> > properties may have this information.
18.05.2012 14:23, Joost van der Sluis wrote:
This information can be bound to a properties but also whole classes at
least. (I'll have to test for methods and public fields) So no, not only
properties may have this information.
If methods may have this information then it is not possible to pu
Am 17.05.2012 23:32 schrieb "Joost van der Sluis" :
>
> Hi all,
>
> I'm trying to implement extended RTTI property attributes as supported
> by recent Delphi versions. Extending the parser to allow the property
> attributes syntax was easy.
Nice :D
It might be good to write tests that can be adde
On Fri, 2012-05-18 at 06:30 +0800, Paul Ishenin wrote:
> 18.05.12 5:32, Joost van der Sluis wrote:
>
> > Now I'm wondering if I should make this new field of Tpropertysym a TDef
> > or a TSym(table). I know that Tsym can store itself to a ppu while a
> > TDef does not. But There was something else
18.05.12 5:32, Joost van der Sluis wrote:
Now I'm wondering if I should make this new field of Tpropertysym a TDef
or a TSym(table). I know that Tsym can store itself to a ppu while a
TDef does not. But There was something else, too. But I don't remember
exactly.
TSym is about symbol and TDef
Hi all,
I'm trying to implement extended RTTI property attributes as supported
by recent Delphi versions. Extending the parser to allow the property
attributes syntax was easy.
Now I want to add the extended-attribute information to Tpropertysym,
but have to decide how to do that. It is possible
11 matches
Mail list logo