Re: Fastcode Voting - IntToStr Result Length Rule
- From: "Avatar Zondertau" <avatarzt@xxxxxxxxx (please reply to newsgroup)>
- Date: 30 Sep 2005 05:14:46 -0700
> Let us vote for a rule regarding the length of the result string in
> IntToStr
>
> 1) Result Length must be the exact length of the result eg Result :=
> 'ABC' + #0 => Length(Result) = 4.
> 2) Use global rule
> 3) Allow Length(Result) to be the max length of the result always eg.
> Length(Result) = 11 always.
>
> Please rephrase the rule suggestions and vote.
Since i think it's good to use consistent rules i vote for (2). Option
(1) is more strict than needed. Option (3) potentially wastes memory
and may not be acceptable for Borland (if i knew it were acceptable i
would vote for it BTW).
I think adding an extra challenge like Aleks suggested is a bad idea.
Even though it's easy to implement this is the B&V people shouldn't
have to choose; Fastcode should provide the fasted function (according
to our benchmark) that does the specified job within the specified
constraints.
Current results (with the new wordings; voters please correct me if i'm
wrong):
1) Allocate result string of needed length exactly.
2) Allocate result string of length according our global rule and then
correct length to valid value
Avatar
Dennis
3) Always allocate result string of length 11 and then correct length
to
valid value
Dave
Eric
Pierre
4) Different challenges for rules 2 and 3
Aleksander
.
- References:
- Fastcode Voting - IntToStr Result Length Rule
- From: Dennis
- Fastcode Voting - IntToStr Result Length Rule
- Prev by Date: Re: FastMM4 - Congratulations Pierre
- Next by Date: Re: Fastcode Voting - IntToStr Result Length Rule
- Previous by thread: Re: Fastcode Voting - IntToStr Result Length Rule
- Next by thread: Re: Fastcode Voting - IntToStr Result Length Rule
- Index(es):
Relevant Pages
|
|