Sign in Join

Live chat for Free Pascal, Lazarus, Delphi and every Pascal programmer.

Mailing lists / lazarus / 1999-10

FPC Problem running today

7 messages · 3 people ·

Reply by email Subscribe to this list Your subscription

Read-only archive. Use j and k to move between messages.

Shane Miller

Peter, it's still occuring.
When you have a class with a property like Caption (in TCOntrol) and try to specifiy it again in TCustomForm like below, it thinks you are defining a new variable and wants a TYPE like TCaption. What it should do is look at the parent class (and it's parents) and see if that variable exists. If so, they are the same variable.

It had worked until I pulled from CVS yesterday.
If you are looking for code, simply compile our forms.pp.

Shane

Show quoted text 11 lines
>> Peter Vreman 10/27/99 05:38AM >>> Today, when I compile with the newest build not only am I getting the error in thread.inc, but when I comment that line out I am getting errors in EVERY unit whenever I do something like TCustomForm = class (sdgfdfgh) public property Caption; end; It claims that I need to put a colon after the caption and specify a type, but it should work this way. As a matter of fact, it worked yesterday! Thoughts?

Please supply always a full example.

I'll take a look at it, maybe it's something by my latest fixes in the compiler.

Peter

_________________________________________________________________ To unsubscribe: mail with
"unsubscribe" as the Subject
archives at http://www.miraclec.com/list_archives/lazarus

Reply by email

Peter Vreman
to Shane Miller
you wrote 9 lines
Peter, it's still occuring. When you have a class with a property like Caption (in TCOntrol) and try to specifiy it again in TCustomForm like below, it thinks you are defining a new variable and wants a TYPE like TCaption. What it should do is look at the parent class (and it's parents) and see if that variable exists. If so, they are the same variable. It had worked until I pulled from CVS yesterday. If you are looking for code, simply compile our forms.pp.

That was all i needed to know, where i could find a file which reproduced the bug.

Peter

Peter

Reply by email

Shane Miller

I can't do anything while the problem with the

Property Caption;

error still exists. There would simply be way too many temporary changes I would have to make. Any thoughts on what it is and when it could be fixed?

Shane

Reply by email

Shane Miller

THANK YOU!

I updated CVS. I fixed the problem in gtkcallback with getting the "can't access protected ..." error.

I converted my WINDOWS.PP file to LCLLINUX.PP

We'll try that for now....
Shane

>> Florian Klaempfl 10/27/99 09:00AM >>>
Shane Miller wrote 8 lines
I can't do anything while the problem with the Property Caption; error still exists. There would simply be way too many temporary changes I would have to make. Any thoughts on what it is and when it could be fixed?

I commited a fix.

_________________________________________________________________ To unsubscribe: mail with
"unsubscribe" as the Subject
archives at http://www.miraclec.com/list_archives/lazarus

Reply by email

Peter Vreman
to Shane Miller: Today, when I compile with the newest build not only am I getting the error in…
Show quoted text 10 lines
Today, when I compile with the newest build not only am I getting the error in thread.inc, but when I comment that line out I am getting errors in EVERY unit whenever I do something like TCustomForm = class (sdgfdfgh) public property Caption; end; It claims that I need to put a colon after the caption and specify a type, but it should work this way. As a matter of fact, it worked yesterday! Thoughts?

Please supply always a full example.

I'll take a look at it, maybe it's something by my latest fixes in the compiler.

Peter

Reply by email

Shane Miller

Today, when I compile with the newest build not only am I getting the error in thread.inc, but when I comment that line out I am getting errors in EVERY unit whenever I do something like

TCustomForm = class (sdgfdfgh)
public
  property Caption;
end;

It claims that I need to put a colon after the caption and specify a type, but it should work this way. As a matter of fact, it worked yesterday!

Thoughts?

Shane

Reply by email