I'm attempting to port GExperts from Delphi to Lazaurus and noticed the
definition of TPropInfo differs from Delphi's.
In FPC's TPropInfo the PropType field is PTypeInfo whereas in Delphi it is
PPTypeInfo. I'm not sure what is actually gained by this extra level of
indirection but it exists none t
On Thu, Jul 18, 2013 at 2:22 PM, Juha Manninen wrote:
> On Thu, Jul 18, 2013 at 6:26 PM, Kenneth Cochran
> wrote:
> > Anyone have
> > a ballpark guess as to how much effort would it take to extend the
> tooltip
> > for the component pallet to display the tag from the
On Wed, Jul 17, 2013 at 4:24 PM, Kenneth Cochran
wrote:
>
>
>
> On Wed, Jul 17, 2013 at 3:53 AM, Mattias Gaertner <
> nc-gaert...@netcologne.de> wrote:
>
>> Do you mean hovering over the component in the designer?
>> At the moment the hint shows only the c
On Wed, Jul 17, 2013 at 3:53 AM, Mattias Gaertner wrote:
> Do you mean hovering over the component in the designer?
> At the moment the hint shows only the caption and some common values.
> It could be extended to show the help for the variable. Feel free to
> create a feature request.
>
>
I thin
On Fri, Jul 12, 2013 at 1:07 AM, vfclists . wrote:
>
> This attitude which exists in the Pascal community needs to end. I say
> Pascal not FreePascal because when I examine a lot of free Delphi libraries
> I see the same thing. Lots and lots of code and not a comment in sight. It
> makes stuff ne
Just curious how your efforts turned out?
On Fri, Mar 22, 2013 at 9:59 AM, Graeme Geldenhuys
wrote:
> On 2013-03-22 13:29, Michael Van Canneyt wrote:
> >
> > That looks dangerously much, almost verbatim, like the appendix A of the
> > Delphi language guide as found in the D7 manual.
>
> Umm, I d
Btw, there is already an object pascal implementation targeting llvm.
https://code.google.com/p/llvm-pascal/
On Thu, Feb 28, 2013 at 8:36 AM, Marco van de Voort wrote:
> In our previous episode, Kenneth Cochran said:
> > Ironically this is the direction Embarcadero is moving. They&#
On Feb 28, 2013 5:23 AM, "Henry Vermaak" wrote:
>
> On Thu, Feb 28, 2013 at 10:45:08AM +, Graeme Geldenhuys wrote:
> > On 2013-02-28 09:28, Marc Pertron wrote:
> > >
> > > We need better optimisations at least as much as fancy 123.tostring.
> >
> >
> > Bottom line optimisation work is just
On Wed, Nov 21, 2012 at 5:34 PM, Graeme Geldenhuys
wrote:
>
> That is an incorrect assumptions. The compiler will happily accept both
> types without needing typecasting.
I stand corrected. I assumed it behaved the same as Delphi in this respect.
It doesn't, not even when Delphi mode is enabled.
Yes.
type newString = type string;
Any function that accepts newString as a parameter will cause a compilation
error if you try to pass a normal string. You'll have to cast it to
newString first.
On Wed, Nov 21, 2012 at 1:37 PM, Frank Church wrote:
> Lets say I am using some string variables,
y use
different parsers.
On Sep 1, 2012 3:54 AM, "Bernd" wrote:
> 2012/8/31 Kenneth Cochran :
>
> > I'm finding myself in need of a parser for object pascal. I'm wondering
> if
> > fpc exposes any of the output (syntax trees, graphs, etc) from the parser
First I'll say I know very little about the inner workings of an actual
compiler. I took a course on formal language theory ages ago so I do have
some understanding of the theory. Lately my interests have been pulling me
toward projects that either benefit from or depend on static analysis. So
I'm
12 matches
Mail list logo
