Just a general comment:
Have you thought about writing a generic/general linked list unit first and
then using that to implement the widget stuff ?
Since writing linked lists can be tricky... best is to make a generic unit
for it... test it well... and use it ;)
I can think up some reasons why n
[EMAIL PROTECTED] wrote:
On Fri, 9 Jul 2004, Ron Weidner wrote:
--- Marcel Martin <[EMAIL PROTECTED]> wrote:
Anton Tichawa a ?crit :
Hello List!
Compiling the unit
===
unit test;
interface
procedure test.do_test;
implementation
procedure test.do_test;
begin
end;
end.
===
results in c
Hello, Ron!
Ron Weidner wrote:
Note: I don't see the definition of PWidget in your
code peace. I assume
it's a pointer to a record containing a string
member named meta. But in
your procedure
procedure AddWidget(PWidget:pointer);
you use the very same identifier, PWidget, for a
variable name. Th
On Fri, 9 Jul 2004, Ron Weidner wrote:
> > Note: I don't see the definition of PWidget in your
> > code peace. I assume
> > it's a pointer to a record containing a string
> > member named meta. But in
> > your procedure
> >
> > procedure AddWidget(PWidget:pointer);
> >
> > you use the very
On Fri, 9 Jul 2004, Ron Weidner wrote:
> --- Marcel Martin <[EMAIL PROTECTED]> wrote:
> > Anton Tichawa a écrit :
> > >
> > > Hello List!
> > >
> > > Compiling the unit
> > >
> > > ===
> > >
> > > unit test;
> > >
> > > interface
> > >
> > > procedure test.do_test;
> > >
> > > implementat
Hello,
I saw in the file fpc/rtl/i386/int64p.inc that the function
fpc_mod_qword was disabled with the comment "This does not work
correctly".
The problem is a bad instruction (presumably a typo):
.Lqwordmodr_big_divisior:
|
|
shrdl %cl,%edx,%eax
shrl %cl,%edx
rorl $1,%ed
