Op Thu, 7 Sep 2006, schreef Jonas Maebe:
>
> On 7 sep 2006, at 07:52, Peter Vreman wrote:
>
> > This is not a generic optimization that will give real benefits. Your
> > code
> > also relies on the fact that (a > garantueed. A boolean is defined as 0=false and everything else is true.
>
> Afa
On 7 sep 2006, at 07:52, Peter Vreman wrote:
This is not a generic optimization that will give real benefits.
Your code
also relies on the fact that (ais not
garantueed. A boolean is defined as 0=false and everything else is
true.
Afaik only in case of reading a boolean everything <> 0 is
> Hello,
>
> I wonder if FPC optimize a code such as:
>
> if a < b then
> c := d
> else
> c := b;
>
> as :
>
> r := b + ((d - b) and -(a < b));
>
> If so, do you check the type of CPU (because as I understand, some CPU
> will not execute as fast as other CPU's.
>
> If not, then why, and how wou
Daniël Mantione schrieb:
Op Wed, 6 Sep 2006, schreef ik:
Hello,
I wonder if FPC optimize a code such as:
if a < b then
c := d
else
c := b;
as :
r := b + ((d - b) and -(a < b));
If so, do you check the type of CPU (because as I understand, some CPU
will not execute as fast as other CPU's.
Op Wed, 6 Sep 2006, schreef ik:
> Hello,
>
> I wonder if FPC optimize a code such as:
>
> if a < b then
> c := d
> else
> c := b;
>
> as :
>
> r := b + ((d - b) and -(a < b));
>
> If so, do you check the type of CPU (because as I understand, some CPU
> will not execute as fast as other CPU
Hello,
I wonder if FPC optimize a code such as:
if a < b then
c := d
else
c := b;
as :
r := b + ((d - b) and -(a < b));
If so, do you check the type of CPU (because as I understand, some CPU
will not execute as fast as other CPU's.
If not, then why, and how would you optimize such code ?
Am Mittwoch, 6. September 2006 11:05 schrieb Michael Van Canneyt:
> On Wed, 6 Sep 2006, Ale Katona wrote:
> > The problem here is that if you introduce a changing type to Tag,
> > you're going to break streaming of the components between various
> > platforms. However I think simplest would be to s
Michael Van Canneyt wrote:
> If you want to store objects, use a TCollection, and store
> TCollectionItem.ID in the component tag. ID is a unique identifier, even
> when elements are added and removed from the collection.
>
> Slightly more work, but clean and portable.
And much slower.
Micha
___
Dope!!! :-)
See attached...
Regards,
- Graeme -
On 9/6/06, Vincent Snijders <[EMAIL PROTECTED]> wrote:
Graeme Geldenhuys schreef:
> Hi,
>
> I sent a patch for this before on the 25 July, but it hasn't been
> applied yet. I think the reason might have been due to that patch
> file containi
Graeme Geldenhuys schreef:
Hi,
I sent a patch for this before on the 25 July, but it hasn't been
applied yet. I think the reason might have been due to that patch
file containing a new Size() method as well which caused some
problems.
Anyway, this patch only contains the InflateRect() function
Hi,
I sent a patch for this before on the 25 July, but it hasn't been
applied yet. I think the reason might have been due to that patch
file containing a new Size() method as well which caused some
problems.
Anyway, this patch only contains the InflateRect() function.
Regards,
- Graeme -
--
On Wed, 6 Sep 2006, Ale Katona wrote:
The problem here is that if you introduce a changing type to Tag, you're
going to break streaming of the components between various platforms.
However I think simplest would be to simply make the tag something huge
for years to come, like Int64.
The idea
The problem here is that if you introduce a changing type to Tag, you're
going to break streaming of the components between various platforms.
However I think simplest would be to simply make the tag something huge
for years to come, like Int64.
The idea with hidden union is nice tho. But you'll n
Thanks. That worked fine.
> > Now I get in Lazarus in this code:
> > {$IFDEF UNIX}{$IFDEF UseCThreads} // a break here with error:
> > Ymproject.lpr(6,28) Fatal: Can't find unit Interfaces
> You need to rebuild the LCL for the new compiler.
> Do, Tools, Configure Build Lazarus and recompile the
Hi,
Attached is a small patch to fix a error in the TCollectionItem docs
Regards,
- Graeme -
--
There's no place like 127.0.0.1
Index: classes.xml
===
--- classes.xml (revision 197)
+++ classes.xml (working copy)
@@ -2346,7 +234
15 matches
Mail list logo
