On Fri, 16 Jun 2006, Mattias Gaertner wrote:
3. Better/Faster IO usage ;)
Better designed I/O libraries/classes ?
Better way to control the I/O buffering etc... so we will not need to
"hack" our way to have bigger container then 255 chars...
Perhaps even better: Automatically adapting the buffer size.
The RTL must work with all kinds of programs. There is no single best buffer
size.
Because of this, there is the SetTextBuf() call. This is not a hack.
Only the programmer knows what the usage of a particular file will be,
so only he is qualified to make the call.
4. The amount of classes that comes with Java as part of the compiler
:P
Can live with them. Make your own libraries.
You are loosing the reason to work with Pascal. When you have ready to
use libraries that come with the language, you increase development,
and it means that you can show what the language can actually do. You
need a complex graph, plotting etc calculation ? use the "GraphMath"
unit... You need an XSLT(2) support ? use the xslt unit. You need SNMP
traps support ? use that unit ...etc..
AFAIK the FPC team adds happily new classes to the standard/extra packages.
Just contribute.
Exactly.
6. "inline" code inside class (like in C++/Java).
Not recommended. Bad design.
Huh ?!
destructor Destroy; override;
begin
inherited Destroy;
end;
Why should i place it somewhere else ?! To remind you, I could use
"inline" command in order to place code of functions in the interface
sections on TP... So the Pascal language do have history of such
things ...
The above code is superfluous. you don't need this code at all.
In OO the implementation should be separate from the interface. Of course
this is a matter of taste and the used Editor.
No, it's a matter of correct separation of interface and implementation.
Implementation should always be separate from interface.
7. Build in regex syntax like in Perl, Ruby Javascript.
Replace it, by a library.
Why ?!
S := 'We are programming in Perl';
S :=~ s/Perl/Pascal/s;
Doesn't it nicer then to use something like:
S := 'We are programming in Python';
Regex := TRegex.Create;
Regex.compile ('Python',S);
S := Regex.Replace ('Pascal', 's');
Sure it's cool to use external functions, but it's useful to use it as
a syntax structure :)
See ideintf/texttools.pas. Then the above would be
S := 'We are programming in Perl';
S := REReplace(S,'Perl','Pascal','s');
IMHO this is better to read and better to understand for newbies, than the
short but cryptic perl syntax.
Exactly.
Michael.
_________________________________________________________________
To unsubscribe: mail [EMAIL PROTECTED] with
"unsubscribe" as the Subject
archives at http://www.lazarus.freepascal.org/mailarchives
