> Actually my problem was with units. All my compiles failed on unit
> dependancies. I tried to recompile the units it was looking for, and
> theb copied the .ppu and .o files to /usr/lib/fpc/1.0.7/units/linux, but
> it still could not find them. copying them into the source directory
> likewize f
Actually my problem was with units. All my compiles failed on unit
dependancies. I tried to recompile the units it was looking for, and
theb copied the .ppu and .o files to /usr/lib/fpc/1.0.7/units/linux, but
it still could not find them. copying them into the source directory
likewize failed.
I
> However I'm quite sure that it has to with the
> OO-methods for accessing array-elements
Having no idea what this object is doing, I might be
way out of line here, but maybe it would speed things
up to implement some sort of a "ForEach" callback,
rather than indexing the array on each call.
> >> routines, which was also the case (the non-OO routines uses 10 sec for a
> >> 500x500 matrix inversion, while the OO routines uses 110 secs (!) for the
> >> same).
> >
> > Which compiler did you use? Which OO model did you use?
> >
> > If the answers are 1.0.6 and class then you should try the
Peter Vreman wrote:
>> I expected my OO routines to be somewhat slower than my equivalent non-OO
>> routines, which was also the case (the non-OO routines uses 10 sec for a
>> 500x500 matrix inversion, while the OO routines uses 110 secs (!) for the
>> same).
>
> Which compiler did you use? Which
> Peter Vreman wrote:
>> Which compiler did you use? Which OO model did you use?
>> If the answers are 1.0.6 and class
>
> Right answer... :-)
>
>> then you should try the 1.1 compiler and
>> add {$implicitexceptions off}
>
> OK, I'll try the 1.1. What does the {$implicitexceptions off} do (I gues
Peter Vreman wrote:
> Which compiler did you use? Which OO model did you use?
> If the answers are 1.0.6 and class
Right answer... :-)
> then you should try the 1.1 compiler and
> add {$implicitexceptions off}
OK, I'll try the 1.1. What does the {$implicitexceptions off} do (I guess it
turns im
> Hi all, I am trying to write a basic object-oriented matrix library, but
> have
> run into a problem.
>
> I expected my OO routines to be somewhat slower than my equivalent non-OO
> routines, which was also the case (the non-OO routines uses 10 sec for a
> 500x500 matrix inversion, while the OO r
Hi all, I am trying to write a basic object-oriented matrix library, but have
run into a problem.
I expected my OO routines to be somewhat slower than my equivalent non-OO
routines, which was also the case (the non-OO routines uses 10 sec for a
500x500 matrix inversion, while the OO routines uses
