I'm new to this list and want to introduce myself and my intended
contributions to FreePascal.
You are not new to everybody:-)
archive files (cpio, tar...). I've already update or implemented some
of these modules, now I want to define a common interface and API for
compressed and archive
On Thu, 30 Dec 2004, DrDiettrich wrote:
Hi there,
I'm new to this list and want to introduce myself and my intended
contributions to FreePascal.
My name is Dr. Hans-Peter Diettrich, and I live in Flensburg (Germany).
For brevity I use to sign my messages as DoDi. My main interests are
Just don't use anything conflicting with other prefixes: lib, z, db, im, sys.
If we can agree on an implementation for archive handling that can be
considered a standard implementation for FPC (i.e. distributed with the
FCL), 'fp' can (and should) be used.
Naming a unit with 'u'
On Thu, 30 Dec 2004, Marco van de Voort wrote:
Just don't use anything conflicting with other prefixes: lib, z, db, im,
sys.
If we can agree on an implementation for archive handling that can be
considered a standard implementation for FPC (i.e. distributed with the
FCL), 'fp'
--- peter green [EMAIL PROTECTED] escribió:
you are forciblly putting an out of range value in a variable what
do you
expect to happen?
Of course the program was made to do that evident, but what happen
when you find a procedure, for example:
procedure doAorB(value: boolean);
begin
El Jueves, 30 de Diciembre de 2004 22:48, Jesus Reyes escribiste:
procedure doAorB(value: boolean);
begin
case value of
true: doA;
false: doB;
end;
end;
if Value then
DoA
else
BoB;
--
saludos,
Nico Aragón
http://espira.net/nico/
I think the old saying goes garbage in garbage out.
range checking should probablly catch this sort of stuff but that has a high
performance penalty and is therefore usually disabled.
At the end of the day if you force out of range data into your booleans then
its your problem.
-Original
