Hello, Eduardo
> IMO, all functions inhirited from Clipper, should at least, behaves
> like this.
>
That's pretty simple: xHarbour behaves like Clipper AND has a
documented extension. It may look useless to you but not to others who
are familiar with C. We do not need to have "limitation c
lipper ERROR
COMPATIBILITY". So I'm very sorry, but I will not continue arguing this
matter.
Ron
--
From: "Eduardo Fernandes"
Sent: Thursday, April 02, 2009 5:23 PM
To: "xHarbour Developers Mailing List"
; " xH
of str('1',2) in real application.
regards,
Eduardo
--- Em qui, 2/4/09, Patrick Mast, xHarbour.
escreveu:
> De: Patrick Mast, xHarbour.
> Assunto: Re: [xHarbour-developers] Str() function.
> Para: "xHarbour Developers Mailing List"
>
> Data: Quinta-feir
: "Marcelo Lombardo"
Cc: "xHarbour Developers Mailing List"
Subject: Re: [xHarbour-developers] Str() function.
> Hello Marcelo,
>
>> As Ron said, this is intentional. This is a xHB extension like:
>> a := "ABCD"
>> ? a[2]// prints "B", n
Hello Marcelo,
> As Ron said, this is intentional. This is a xHB extension like:
> a := "ABCD"
> ? a[2] // prints "B", no RT error
Yes, I understand, but:
Str("a",1,0) is useless no?
The first parameter of STR() should be numeric.. I'm only talking
about giving a character parameter to STR().
Patrick,
As Ron said, this is intentional. This is a xHB extension like:
a := "ABCD"
? a[2]// prints "B", no RT error
These are similar extensions because in C, 1 byte char can be read as
numeric, as well as a multiple by char can be adressed as array of
char. It means you can use C-like
Hello,
> I would like error/base instead these results:
>
> ? str('1') // null char
> ? str('1',0) // 49
> ? str('1',1) // *
> ? str('1',2) // 49
I agree. Str("a",1,0) should produce an error.
Patrick
do
--- Em qua, 1/4/09, Miguel Angel Marchuet escreveu:
> De: Miguel Angel Marchuet
> Assunto: Re: [xHarbour-developers] Str() function.
> Para: "Eduardo Fernandes"
> Cc: "Ron Pinkas" , "Xharbour-Developers List"
>
> Data: Quarta-feira,
,
Eduardo
--- Em seg, 30/3/09, Ron Pinkas escreveu:
De: Ron Pinkas
Assunto: Re: [xHarbour-developers] Str() function.
Para: "Eduardo Fernandes" , "Xharbour-Developers List"
Data: Segunda-feira, 30 de Março de 2009, 23:24
Eduardo,
The feature has nothing to do w
;
>
> --- Em seg, 30/3/09, Ron Pinkas escreveu:
>
>> De: Ron Pinkas
>> Assunto: Re: [xHarbour-developers] Str() function.
>> Para: "Eduardo Fernandes" , "Xharbour-Developers
>> List"
>> Data: Segunda-feira, 30 de Março de 2009, 23:24
>>
Ron,
Ron,
OK, since this has nothing to do with str/strzero, I can fix these functions to
return error base if the arguments are not numbers, like Clipper ?
regards,
Eduardo
--- Em seg, 30/3/09, Ron Pinkas escreveu:
> De: Ron Pinkas
> Assunto: Re: [xHarbour-developers] Str() fu
2009 4:33 PM
To: "Xharbour-Developers List" ;
"Ron Pinkas"
Subject: Re: [xHarbour-developers] Str() function.
>
> Ron,
>
> Sorry, by I don't understand what benefit the users will have with this
> feature on str/strzero functions. This is not Clipper compliant a
Ron,
Sorry, by I don't understand what benefit the users will have with this feature
on str/strzero functions. This is not Clipper compliant and return unexpected
results.
regards,
Eduardo
--- Em seg, 30/3/09, Ron Pinkas escreveu:
> De: Ron Pinkas
> Assunto: Re: [xHarbour-deve
bour-Developers List"
Subject: [xHarbour-developers] Str() function.
>
> Sorry my curiosity,
>
> ? str( '1', 3,0) returns 49 = asc code of character 1
> ? str( 'a', 3,0) returns 97 = asc code of character a
>
> This is intentional or an undocum
Sorry my curiosity,
? str( '1', 3,0) returns 49 = asc code of character 1
? str( 'a', 3,0) returns 97 = asc code of character a
This is intentional or an undocumented issue ?
What's the benefit, instead an argument error ?
regards,
Eduardo
Veja quais são os assuntos do momento no Yahoo
15 matches
Mail list logo
