hi daruischange this line
Params[i] :=
@Parameters[i];with thisParams[i]^ := Parameters[i];hope it works.marianop
___
fpc-pascal maillist - fpc-pascal@lists.freepascal.org
http://lists.freepascal.org/mailman/listinfo/fpc-pascal
None of the FPC developers currently has the time nor wish to supportany of the .NET enhancements, and that includes the dot in the unit
names.despite it was originally intended for .net, i don't see it as a .net specific enhancement, but it's ok.
i appreciate your answer. Michael.marianop
We don't support every bug/strange thing delphi supports.ok, i understand your point.
in my very humble opinion it was an interesting idea.If you want to insult people you might do it somewhere else. Thank you.
it was a joke. not aiming to offend anybody.thanks,marianop
> > This looks to me like a delphi bug.a bug? are you serious?
A unit must be a valid pascal> > identifier.
fpc just support valid standard pascal? this is not what i heard. delphi7 supports it since 2002. not a .net release.
Or is there any use in supporting this?ofcourse there is a use.you see
hi,does fpc support unit names with more than one dot or is planned?in delphi 7 you can compile this:// unit main.dprprogram main;uses test.sec;begin test.sec.doit;end.
// unit test.sec.pasunit test.sec;interfaceprocedure doit;implementationprocedure doit;begin writeln('anda');end;end.thanks,mar
Well... :-P i'm not good too... but i think that the problems is:
List0 and List1 are pointers to an TStringList Object...
so, the right sentence must be:
List0 := TStringList.Create;
List1 := TStringList.create;
intead
List0.create;
List1.create;
".Create" are a class method that give a point
