Board index » delphi » About FastCode library

2006-01-10 03:03:13 PM
delphi252
Hello,
For the one (like me), who has not been around too long, has more than less
trouble to get hang of the project.
Like were is the library? which version is it? What it contains? Where is
project going (gloals)? so on...
Project clearly produces good code, but code is more than less hidden.
And community.
Many people would be willing to help. If there would be (kind of what I
suggested before) B&V tool(s) that could send reports to some setraliced DB,
so code would be tested on various platforms. And even those {*word*118} VIAs and
so would be tested agains. Even if code will not be targeted for VIA tool
could still tell which version of code would be most suotable, and most
importantly which is definetly not.
-Tommi-The Grape-
 

Hi Tommi
Some words from the former manager. I hope that someone from the community
will answer also and provide a better balanced view ;-)
under this cryptic named link RTL Replacement Pkg v0.3 at
fastcode.sourceforge.net/
There exist no descriptions or user guides for this new library. It is
essentially untested.
Under the link Info on Fastcode Libraries you will find all the old official
libraries which have been s{*word*99}ped by the community. These should be
considered unofficial libraries now. They are described OK, but only 20% of
them have been made. Nobody except for me and Dennis Lauritzen have been
willing to work on them.
A well known and much used unofficial library is FastMove by John O'Harrow.
It can be found under the broken link
Unofficial Versions
on the "Info on Fastcode Libraries" page.
As you can see the site is in a mess!
"The Fastcode project provides highly optimized functions for the Delphi
community. Functions are faster versions of Delphi runtime library
functions, VCL functions or functions meant as extensions for these. The
project is running on a volunteer basis."
We just continue to do what we did and do.
maintaining the library and the site.
done to improve a situation that was quite good before.
The VIA bug in FastMove slipped through because the FastMove library is not
a Fastcode library and has not been validated as part of the Fastcode
validation.
All help is appreciated, but our main problem is a lack of overall
management. Finding people that are willing and able to finish what they
started is also a problem. It is so easy to vent clever ideas and promise to
deliver implementations, but it takes a lot of effort to complete tasks. As
a result of this we currently have a lot of unfinished and potential buggy
code{*word*154} around.
Regards
Dennis
 

Even to find the last release of FastMM is a challenge.
because so many people can get involved when they can/want that you are
guaranteed to end up most of the time with half coded buggy functions
which is totally counterproductive. No code/function is better than
boggey ones.
The JCL/JCVL team are doing a better job because anybody can get the
libraries and contribute easily. The JCL has got many bugs though and
in this respect this group does a much better job.
I have no web development skills at all. But it is very likely that
many of the visitors here have. They could help in just a few nights to
get:
- a webpage that lists:
- libraries and their status
- latest important news or a newsletter written every month or so
- a centralised source code repository
I am sure that someone in a university can host this without too much
hassle.
Michael
--
----------------------------------------------
michael.moreno.free.fr/
 

It won't compile:
[Error] FastCode.pas(54): Identifier redeclared: 'FastCodePos'
[Error] FastCode.pas(55): Identifier redeclared: 'FastCodeLowerCase'
[Error] FastCode.pas(56): Identifier redeclared: 'FastCodeUpperCase'
[Error] FastCode.pas(57): Identifier redeclared: 'FastCodeCompareText'
[Error] FastCode.pas(58): Identifier redeclared: 'FastCodeStrComp'
[Error] FastCode.pas(59): Identifier redeclared: 'FastCodeStrCopy'
[Error] FastCode.pas(60): Identifier redeclared: 'FastcodeFillChar'
[Error] FastCode.pas(61): Identifier redeclared: 'FastcodeCompareStr'
[Error] FastCode.pas(62): Identifier redeclared: 'FastcodeCompareMem'
[Fatal Error] Project1.dpr(17): Could not compile used unit 'FastCode.pas'
Maybe this sould be defined like following
var
GFastCodePos : TFastCodePosFunction;
GFastCodeLowerCase : TFastCodeLowerCaseFunction;
...
T usually if front to types and G as Global. Maybe. I could make this kind
of changes if Help is needed...
-Tommi-
 

What version of Delphi are you using. It compiles Ok for me under D2006
--
regards,
John
The Fastcode Project:
www.fastcodeproject.org/
"Tommi Prami" <tommi (piste) prami (at) ecomond (dot) com>writes

D6
Look (UnOfficial)RTL Replacement Pkg v0.31.7z from Attachements. That'll
compile in Delphi 6 also...
-TP-
"John O'Harrow" <XXXX@XXXXX.COM>writes

You are correct. Under Delphi 6 you cannot have a local variable with the
same name as a used unit.
I propose renaming all of the local variable from FastCodeXXXXXX to
fcXXXXXX.
There is another problem with this library now. Since the FastcodeCPUID.PAS
file has been updated (with different fastcode target processors), this
library cannot use the latest FastcodeCPUID unit. For example a P3
processor will be treated as a fastcode blended target and would therefore
not be able to use SSE instructions.
--
regards,
John
The Fastcode Project:
www.fastcodeproject.org/
"Tommi Prami" <tommi (piste) prami (at) ecomond (dot) com>writes

Hi Michael and Tommi
Remember that is so easy to critisize, but so difficult to actually make a
project a success. The Fastcode project has delivered so much high quality
code and some of it is delivered directly to you in Delphi. Why do you find
yourself in a situation where you can just rant about what we have not done?
Have you earned that rigth by providing hard work? Perhaps you should bother
visit our site before start ranting.
www.fastcodeproject.org/
newsletter is not an especially good idea. Have you followed the project
closely for a long time since you know so much about what we should do?
Dennis C
 

Sure it is easy to critisize, but I am not doing it because of that.
Criticism is not a generally bad thing. IF I'd say you are just bunch of
W@??€S, that would be. If I suggest a change or point out some thing that
I think is a drawback, why is that such a bad thing. I know that everyone is
complaining about something and it will not cheer you up to answer.
I saw a big flaw, library did not compile in D6. I made changes, hopefully
someone will merge my chages to current code base.
I'll just try to find out ways to help, thats all.
-Tommi-
 

Hi Tommi
OK. I am in a better mood today ;-)
Best regards
Dennis Kjaer Christensen