On Sun, Mar 6, 2011 at 6:20 AM, Juha Manninen juha.mannine...@gmail.com wrote:
Marcos Douglas kirjoitti sunnuntai 06 maaliskuu 2011 03:57:02:
type
TStringList = class(Classes.TStringList)
public
function Foo: string;
end;
In any case your class name is very confusing. I would
when you want to change to TColorEdit, just change TEditCtrl definition to
TColorEdit. Same type-savings as your proposal.
--
View this message in context:
http://free-pascal-lazarus.989080.n3.nabble.com/Lazarus-Code-completion-Error-ancestor-has-same-name-as-class-tp2640414p2642585.html
Sent from
On Sun, Mar 6, 2011 at 3:20 PM, leledumbo leledumbo_c...@yahoo.co.id wrote:
Maybe for the programmer of the unit, but for the users, it's almost always a
disadvantage. They will get unexpected behavior instead (especially if you
put it along with other things in the unit where one might need
The program below compiles. But if I try to use code completion here
writeln(s.F...
Occurs this error:
test.lpr(8,31) Error: ancestor has same name as class.
program test;
{$mode objfpc}{$H+}
uses SysUtils, Classes;
type
TStringList = class(Classes.TStringList)
public
function Foo:
Marcos Douglas kirjoitti sunnuntai 06 maaliskuu 2011 03:57:02:
type
TStringList = class(Classes.TStringList)
public
function Foo: string;
end;
In any case your class name is very confusing. I would always use a different
name. When someone else reads your code and sees TStringList
On Sat, 5 Mar 2011 22:57:02 -0300
Marcos Douglas m...@delfire.net wrote:
The program below compiles. But if I try to use code completion here
writeln(s.F...
Occurs this error:
test.lpr(8,31) Error: ancestor has same name as class.
program test;
{$mode objfpc}{$H+}
uses SysUtils,
