Re: [xHarbour-developers] Str() function.
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 compatibility" with Clipper. As an example, following your idea, array( 4097 ) should also raise a RT error simply because that's what Clipper does. Marcelo -- ___ xHarbour-developers mailing list xHarbour-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xharbour-developers
Re: [xHarbour-developers] Str() function.
Eduardo,
I tried to explain a number of times, that this extension has nothing to do
with Str() in specific. As I explained, xHarbour has an additional (SUB)TYPE
called CHAR. That type CHAR, is NUMERIC compatible, period!
Please THINK what this RULE means.
Because Str() function accept a NUMERIC argument, than ANY NUMERIC is
accepted. Although it's NOT LIKELY that anyone will use a CHAR type as an
argument to the Str() function, it would not be acceptable for us to program
a SPECIFIC EXCEPTION to the general rule.
Not that it has any importance, but here is an example of intended usage of
Str() with CHAR argument.
//---//
PROCEDURE Main()
LOCAL sString := "HELLO"
LOCAL sAscii := ""
LOCAL cChar
FOR EACH cChar IN sString
sAscii += Str(cChar, 2 ) + ","
NEXT
sAscii[-1] := 0
? sAscii
RETURN
//---//
For further consideration, please review this C sample:
//--//
#include
#include
int main( int argc, char *argv[] )
{
char szString[3];
_itoa( 'a', szString, 10 );
printf( "%s\n", szString );
return 0;
}
//--//
Would you like to convince anyone to program exceptions into C, that would
DISCRIMINATE against the char type, in _itoa() "because it has no use in
real application"?
You just can't break general type rules, only because they don't look
reasonable in some usage.
IAE, if you are not convinced, I'm sorry to be blunt, but I must advise you
that when I created the xHarbour project, I made it perfectly clear, that
this project values extended functionality over "Clipper 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"
; " xHarbour.Patrick Mast"
Subject: Re: [xHarbour-developers] Str() function.
>
> Patrick,
>
> IMO, all functions inhirited from Clipper, should at least, behaves like
> this.
>
> For example:
>
> Val(1) returns an error/base, as expected.
> If str('1',2) extension is very important, so hb_str() should be created,
> instead implement it in str().
>
> I would like know what use 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-feira, 2 de Abril de 2009, 8:39
>> 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
>>
>> --
>> ___
>> xHarbour-developers mailing list
>> xHarbour-developers@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/xharbour-developers
>>
>
>
> Veja quais são os assuntos do momento no Yahoo! +Buscados
> http://br.maisbuscados.yahoo.com
>
> --
> ___
> xHarbour-developers mailing list
> xHarbour-developers@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/xharbour-developers
>
--
___
xHarbour-developers mailing list
xHarbour-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/xharbour-developers
Re: [xHarbour-developers] Str() function.
Patrick,
IMO, all functions inhirited from Clipper, should at least, behaves like this.
For example:
Val(1) returns an error/base, as expected.
If str('1',2) extension is very important, so hb_str() should be created,
instead implement it in str().
I would like know what use 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-feira, 2 de Abril de 2009, 8:39
> 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
>
> --
> ___
> xHarbour-developers mailing list
> xHarbour-developers@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/xharbour-developers
>
Veja quais são os assuntos do momento no Yahoo! +Buscados
http://br.maisbuscados.yahoo.com
--
___
xHarbour-developers mailing list
xHarbour-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/xharbour-developers
Re: [xHarbour-developers] Str() function.
Patrick,
You seem to keep ignoring the answers posted. Look:
1. In xHarbour, any string of 1 Character has a SUB TYPE called CHAR.
2. xHarbour type CHAR is compatible in ANY NUMERIC context, which means you
can do:
sString := "Hello"
sEncripted := ""
FOR EACH cChar IN sString
sEncripted += cChar - HB_EnumIndex()
NEXT
This also means that it's supported at the lowest SYSTEM LEVEL, so even
hb_itemGetNI()/hb_itemGetND(), etc, know to support CHAR as NUMERIC.
This extension has been created many years back, from the very start of
xHarbour, and it was exactly this kind of arguments that pushed me to create
xHarbour. Those that prefer to be error compatible should be using Clipper.
Ron
--
From: "Patrick Mast, xHarbour."
Sent: Thursday, April 02, 2009 12:46 PM
To: "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", 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(). STR() is not build to
> accept a character parameter and thus should produce a RT error.
>
> Patrick
>
> --
> ___
> xHarbour-developers mailing list
> xHarbour-developers@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/xharbour-developers
>
--
___
xHarbour-developers mailing list
xHarbour-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/xharbour-developers
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", 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(). STR() is not build to
accept a character parameter and thus should produce a RT error.
Patrick
--
___
xHarbour-developers mailing list
xHarbour-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/xharbour-developers
Re: [xHarbour-developers] Uploaded: xharbour-1.20.01.src.zip
Hi, On Thu, Apr 2, 2009 at 5:10 PM, Ron Pinkas wrote: > Phil, Luiz, Enrico, > > I just added "Release Technician" role to Luiz & Phil. Thanks, the source packages are done. -- Ph. -- ___ xHarbour-developers mailing list xHarbour-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xharbour-developers
Re: [xHarbour-developers] Uploaded: xharbour-1.20.01.src.zip
Hi,
On Thu, Apr 2, 2009 at 4:25 PM, Ron Pinkas wrote:
> I don't understand, what problem do we have with cmd.exe?
>
> Don't we just need to add few more calls to zip command for the missing
> files?
If we go this way we will need to add few more calls whenever a new
directory or files with unsupported extensions are added to the
repository, and remove some calls whenever we remove a directory. What
my script does is:
0. checkout a clean CVS tree with given tag.
1. determine 'binary' files using */CVS/Entries. These files should be
added as binary to zip archive, the rest - as text, so that EOL format
difference on DOS and UNIX is respected. Probably you don't have to do
it to make Windows sources under Windows, but have to do it to make
Unix sources undet Windows or Windows sources under Unix.
2. remove all directories named CVS.
3. move contrib and tests subdirs out of the main tree. This is
because of our tradition to provide separate archives for them.
4. rename main directory to xharbour-${VERSION} where ${VERSION} is 1.2.1 now.
5. make .tar.gz archive of xharbour-${VERSION} dir.
6. make zip archive with binary files from xharbour-${VERSION} dir.
7. add text files to the zip archive with -l zip option which changes
EOLs to DOS style (remember, I'm doing it under Unix where CVS checks
out text files with Unix EOLs)
8. rename xharbour-${VERSION} to xharbour-core-${VERSION}.
9. create a fresh xharbour-${VERSION} and move contrib there, so that
we have xharbour-${VERSION}/contrib
10. repeat steps 5,6,7 creating xharbour-${VERSION}.src.contrib.(tar.gz|zip)
11. rename xharbour-${VERSION} to xharbour-contrib-${VERSION}.
12. create a fresh xharbour-${VERSION} and move tests there, so that
we have xharbour-${VERSION}/tests
13. repeat steps 5,6,7 creating xharbour-${VERSION}.src.tests.(tar.gz|zip)
I make xharbour source packages using this script since
xharbour-0.99.60, and all I had to change is version name and CVS tag
name.
Probably someone who speaks cmd.exe language well could implement it
as a Windows batch file. My .bat experience is still on the
command.com or 4DOS level, and I don't know how that EOL trick can be
done under Windows.
-- Ph.
--
___
xHarbour-developers mailing list
xHarbour-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/xharbour-developers
Re: [xHarbour-developers] Uploaded: xharbour-1.20.01.src.zip
Ron
I'll move the release tonight
Regards
Luiz
- Original Message -
From: "Ron Pinkas"
To: "Phil Krylov" ; "Luiz Rafael Culik Guimaraes"
Cc: "Enrico Maria Giordano" ;
Sent: Thursday, April 02, 2009 10:10 AM
Subject: Re: [xHarbour-developers] Uploaded: xharbour-1.20.01.src.zip
> Phil, Luiz, Enrico,
>
> I just added "Release Technician" role to Luiz & Phil.
>
> Ron
> --
> From: "Phil Krylov"
> Sent: Thursday, April 02, 2009 2:05 AM
> To: "Luiz Rafael Culik Guimaraes"
> Cc: "Ron Pinkas" ; "Enrico Maria Giordano"
> ;
>
> Subject: Re: [xHarbour-developers] Uploaded: xharbour-1.20.01.src.zip
>
>> Hi,
>>
>> On Thu, Apr 2, 2009 at 5:21 AM, Luiz Rafael Culik Guimaraes
>> wrote:
>>> I also can not see your uploads. I suspect the same problem as with
>>> Luiz -
>>> the files probably uploaded to different project, like xbgtk
>>
>> It seems the files are uploaded to directory of my SF user account,
>> and project admin can only add to release files which are in _his_
>> directory. Anyway, here are the files:
>> http://89.179.241.181/~phil/xharbour/
>>
>> Ron, I can't update pack_src.bat, cmd.exe won't manage this task. Here
>> is a bash script I use to build both UNIX and DOS source packages.
>>
>> #!/bin/bash
>>
>> # CVSROOT should be set!
>> export VERSION=1.2.1
>> export TAG=xharbour-1-2-1
>>
>> rm -fr /tmp/tmpcvs
>> mkdir /tmp/tmpcvs
>> cd /tmp/tmpcvs
>>
>> cvs -z3 checkout -P -r $TAG xharbour
>>
>> mv xharbour xharbour-$VERSION
>> rm -fr xharbour-$VERSION/CVSROOT
>>
>> # Determine binary sources
>> for F in `find xharbour-$VERSION -name Entries`; do
>>DIR=`dirname \`dirname $F\``
>>for G in `grep "/\-kb/" $F | sed "s/^\/\([^/]*\)\/.*$/\1/"`; do
>>echo "$DIR/$G" >> binlist
>>done
>> done
>>
>> rm -fr `find xharbour-$VERSION -name CVS`
>> mv xharbour-${VERSION}/contrib ./contrib
>> mv xharbour-${VERSION}/tests ./tests
>> tar czvf xharbour-${VERSION}.src.tar.gz xharbour-${VERSION}
>> zip -rlq xharbour-${VERSION}.src.zip xharbour-${VERSION} -...@binlist
>> zip -rq xharbour-${VERSION}.src.zip -@ < binlist
>> mv xharbour-${VERSION} xharbour-core-${VERSION}
>> mkdir xharbour-${VERSION}
>> mv contrib xharbour-${VERSION}/
>> tar czvf xharbour-${VERSION}.src.contrib.tar.gz xharbour-${VERSION}
>> zip -rlq xharbour-${VERSION}.src.contrib.zip
>> xharbour-${VERSION} -...@binlist
>> zip -rq xharbour-${VERSION}.src.contrib.zip -@ < binlist
>> mv xharbour-${VERSION} xharbour-contrib-${VERSION}
>> mkdir xharbour-${VERSION}
>> mv tests xharbour-${VERSION}/
>> tar czvf xharbour-${VERSION}.src.tests.tar.gz xharbour-${VERSION}
>> zip -rlq xharbour-${VERSION}.src.tests.zip xharbour-${VERSION} -...@binlist
>> zip -rq xharbour-${VERSION}.src.tests.zip -@ < binlist
>> mv xharbour-${VERSION} xharbour-tests-${VERSION}
>>
>> -- Ph.
>>
>
> --
> ___
> xHarbour-developers mailing list
> xHarbour-developers@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/xharbour-developers
>
--
___
xHarbour-developers mailing list
xHarbour-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/xharbour-developers
Re: [xHarbour-developers] Str() function.
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 techniques in PRG to speed up your
app.
Best Regards,
Marcelo Lombardo
www.xharbour.com.br
On Apr 2, 2009, at 8:39 AM, Patrick Mast, xHarbour. wrote:
> 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
>
> --
> ___
> xHarbour-developers mailing list
> xHarbour-developers@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/xharbour-developers
>
--
___
xHarbour-developers mailing list
xHarbour-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/xharbour-developers
Re: [xHarbour-developers] Uploaded: xharbour-1.20.01.src.zip
Phil, Luiz, Enrico,
I just added "Release Technician" role to Luiz & Phil.
Ron
--
From: "Phil Krylov"
Sent: Thursday, April 02, 2009 2:05 AM
To: "Luiz Rafael Culik Guimaraes"
Cc: "Ron Pinkas" ; "Enrico Maria Giordano"
;
Subject: Re: [xHarbour-developers] Uploaded: xharbour-1.20.01.src.zip
> Hi,
>
> On Thu, Apr 2, 2009 at 5:21 AM, Luiz Rafael Culik Guimaraes
> wrote:
>> I also can not see your uploads. I suspect the same problem as with
>> Luiz -
>> the files probably uploaded to different project, like xbgtk
>
> It seems the files are uploaded to directory of my SF user account,
> and project admin can only add to release files which are in _his_
> directory. Anyway, here are the files:
> http://89.179.241.181/~phil/xharbour/
>
> Ron, I can't update pack_src.bat, cmd.exe won't manage this task. Here
> is a bash script I use to build both UNIX and DOS source packages.
>
> #!/bin/bash
>
> # CVSROOT should be set!
> export VERSION=1.2.1
> export TAG=xharbour-1-2-1
>
> rm -fr /tmp/tmpcvs
> mkdir /tmp/tmpcvs
> cd /tmp/tmpcvs
>
> cvs -z3 checkout -P -r $TAG xharbour
>
> mv xharbour xharbour-$VERSION
> rm -fr xharbour-$VERSION/CVSROOT
>
> # Determine binary sources
> for F in `find xharbour-$VERSION -name Entries`; do
>DIR=`dirname \`dirname $F\``
>for G in `grep "/\-kb/" $F | sed "s/^\/\([^/]*\)\/.*$/\1/"`; do
>echo "$DIR/$G" >> binlist
>done
> done
>
> rm -fr `find xharbour-$VERSION -name CVS`
> mv xharbour-${VERSION}/contrib ./contrib
> mv xharbour-${VERSION}/tests ./tests
> tar czvf xharbour-${VERSION}.src.tar.gz xharbour-${VERSION}
> zip -rlq xharbour-${VERSION}.src.zip xharbour-${VERSION} -...@binlist
> zip -rq xharbour-${VERSION}.src.zip -@ < binlist
> mv xharbour-${VERSION} xharbour-core-${VERSION}
> mkdir xharbour-${VERSION}
> mv contrib xharbour-${VERSION}/
> tar czvf xharbour-${VERSION}.src.contrib.tar.gz xharbour-${VERSION}
> zip -rlq xharbour-${VERSION}.src.contrib.zip
> xharbour-${VERSION} -...@binlist
> zip -rq xharbour-${VERSION}.src.contrib.zip -@ < binlist
> mv xharbour-${VERSION} xharbour-contrib-${VERSION}
> mkdir xharbour-${VERSION}
> mv tests xharbour-${VERSION}/
> tar czvf xharbour-${VERSION}.src.tests.tar.gz xharbour-${VERSION}
> zip -rlq xharbour-${VERSION}.src.tests.zip xharbour-${VERSION} -...@binlist
> zip -rq xharbour-${VERSION}.src.tests.zip -@ < binlist
> mv xharbour-${VERSION} xharbour-tests-${VERSION}
>
> -- Ph.
>
--
___
xHarbour-developers mailing list
xHarbour-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/xharbour-developers
Re: [xHarbour-developers] Uploaded: xharbour-1.20.01.src.zip
Phil,
I don't understand, what problem do we have with cmd.exe?
Don't we just need to add few more calls to zip command for the missing
files?
Ron
--
From: "Phil Krylov"
Sent: Thursday, April 02, 2009 2:05 AM
To: "Luiz Rafael Culik Guimaraes"
Cc: "Ron Pinkas" ; "Enrico Maria Giordano"
;
Subject: Re: [xHarbour-developers] Uploaded: xharbour-1.20.01.src.zip
> Hi,
>
> On Thu, Apr 2, 2009 at 5:21 AM, Luiz Rafael Culik Guimaraes
> wrote:
>> I also can not see your uploads. I suspect the same problem as with
>> Luiz -
>> the files probably uploaded to different project, like xbgtk
>
> It seems the files are uploaded to directory of my SF user account,
> and project admin can only add to release files which are in _his_
> directory. Anyway, here are the files:
> http://89.179.241.181/~phil/xharbour/
>
> Ron, I can't update pack_src.bat, cmd.exe won't manage this task. Here
> is a bash script I use to build both UNIX and DOS source packages.
>
> #!/bin/bash
>
> # CVSROOT should be set!
> export VERSION=1.2.1
> export TAG=xharbour-1-2-1
>
> rm -fr /tmp/tmpcvs
> mkdir /tmp/tmpcvs
> cd /tmp/tmpcvs
>
> cvs -z3 checkout -P -r $TAG xharbour
>
> mv xharbour xharbour-$VERSION
> rm -fr xharbour-$VERSION/CVSROOT
>
> # Determine binary sources
> for F in `find xharbour-$VERSION -name Entries`; do
>DIR=`dirname \`dirname $F\``
>for G in `grep "/\-kb/" $F | sed "s/^\/\([^/]*\)\/.*$/\1/"`; do
>echo "$DIR/$G" >> binlist
>done
> done
>
> rm -fr `find xharbour-$VERSION -name CVS`
> mv xharbour-${VERSION}/contrib ./contrib
> mv xharbour-${VERSION}/tests ./tests
> tar czvf xharbour-${VERSION}.src.tar.gz xharbour-${VERSION}
> zip -rlq xharbour-${VERSION}.src.zip xharbour-${VERSION} -...@binlist
> zip -rq xharbour-${VERSION}.src.zip -@ < binlist
> mv xharbour-${VERSION} xharbour-core-${VERSION}
> mkdir xharbour-${VERSION}
> mv contrib xharbour-${VERSION}/
> tar czvf xharbour-${VERSION}.src.contrib.tar.gz xharbour-${VERSION}
> zip -rlq xharbour-${VERSION}.src.contrib.zip
> xharbour-${VERSION} -...@binlist
> zip -rq xharbour-${VERSION}.src.contrib.zip -@ < binlist
> mv xharbour-${VERSION} xharbour-contrib-${VERSION}
> mkdir xharbour-${VERSION}
> mv tests xharbour-${VERSION}/
> tar czvf xharbour-${VERSION}.src.tests.tar.gz xharbour-${VERSION}
> zip -rlq xharbour-${VERSION}.src.tests.zip xharbour-${VERSION} -...@binlist
> zip -rq xharbour-${VERSION}.src.tests.zip -@ < binlist
> mv xharbour-${VERSION} xharbour-tests-${VERSION}
>
> -- Ph.
>
--
___
xHarbour-developers mailing list
xHarbour-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/xharbour-developers
[xHarbour-developers] Upper function [2nd time]
Can we adopt upper() function in source/rtl/strcase.c instead of in include/hbexprb.c ? Eduardo Veja quais são os assuntos do momento no Yahoo! +Buscados http://br.maisbuscados.yahoo.com -- ___ xHarbour-developers mailing list xHarbour-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xharbour-developers
Re: [xHarbour-developers] Str() function.
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
--
___
xHarbour-developers mailing list
xHarbour-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/xharbour-developers
Re: [xHarbour-developers] Str() function.
Miguel,
I agree that extension is preferable, but in this case, on str function, this
have no sence. The unique purpose of str is convert a numeric var to string
one. For it we have asc() function. IMO, this extension is uselesss on str and
produce strange results, instead expected ones. In other way, xHarbour doesn't
compile with HB_C52_STRICT. I got many errors.
I would like error/base instead these results:
? str('1') // null char
? str('1',0) // 49
? str('1',1) // *
? str('1',2) // 49
My 2 cents !
regards,
Eduardo
--- 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, 1 de Abril de 2009, 16:10
>
>
>
>
>
>
>
> It
> is not always possible to maintain compatibility with the
> old clipper.
>
>
> Extending xHarbour is preferable. But of course if it is an
> appropriate
> use
>
> of Str should encounter no problem.
>
>
> Str works as expected actually. simply the expected is not
> the same as
> clipper.
>
>
>
> But, I think can be able to add under HB_C52_STRICT only,
> but you lost
> other extensions.
>
>
>
> Best regards,
>
> Miguel Angel Marchuet
>
>
>
> Eduardo Fernandes escribió:
>
> 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() 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 with Str() or StrZero()
> it's
> a GENERIC SUPPORT. You can use a CHAR type as NUMERIC in
> every context that numeric is supported.
>
> Ron
>
> --
> From: "Eduardo Fernandes"
> Sent: Monday, March 30, 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 and return unexpected results.
>
>
> regards,
> 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, 19:45
> Eduardo,
>
> This is a documented intentional feature. Every
>
>
>
> STRING of
>
>
>
> ONE CHARACTER is
> NUMERIC COMPATIBLE, as per xHarbour support of a
>
>
>
> CHAR sub
>
>
>
> type.
>
> Ron
>
>
>
>
>
> Veja quais são os assuntos do
>
>
> momento no Yahoo! +Buscados
>
>
> http://br.maisbuscados.yahoo.com
>
>
>
>
>
>
> Veja quais são os assuntos do momento no
> Yahoo! +Buscados
> http://br.maisbuscados.yahoo.com
>
> --
> ___
> xHarbour-developers mailing list
> xHarbour-developers@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/xharbour-developers
>
> __ Información de ESET Smart Security,
> versión de la base de firmas de virus 3981 (20090401)
> __
>
> ESET Smart Security ha comprobado este mensaje.
>
> http://www.eset.com
>
>
>
>
>
>
>
>
>
>
> -Anexo incorporado-
>
> --
>
> -Anexo incorporado-
>
> ___
> xHarbour-developers mailing list
> xHarbour-developers@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/xharbour-developers
>
Veja quais são os assuntos do momento no Yahoo! +Buscados
http://br.maisbuscados.yahoo.com
--
___
xHarbour-developers mailing list
xHarbour-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/xharbour-developers
Re: [xHarbour-developers] Uploaded: xharbour-1.20.01.src.zip
Hi,
On Thu, Apr 2, 2009 at 5:21 AM, Luiz Rafael Culik Guimaraes
wrote:
> I also can not see your uploads. I suspect the same problem as with Luiz -
> the files probably uploaded to different project, like xbgtk
It seems the files are uploaded to directory of my SF user account,
and project admin can only add to release files which are in _his_
directory. Anyway, here are the files:
http://89.179.241.181/~phil/xharbour/
Ron, I can't update pack_src.bat, cmd.exe won't manage this task. Here
is a bash script I use to build both UNIX and DOS source packages.
#!/bin/bash
# CVSROOT should be set!
export VERSION=1.2.1
export TAG=xharbour-1-2-1
rm -fr /tmp/tmpcvs
mkdir /tmp/tmpcvs
cd /tmp/tmpcvs
cvs -z3 checkout -P -r $TAG xharbour
mv xharbour xharbour-$VERSION
rm -fr xharbour-$VERSION/CVSROOT
# Determine binary sources
for F in `find xharbour-$VERSION -name Entries`; do
DIR=`dirname \`dirname $F\``
for G in `grep "/\-kb/" $F | sed "s/^\/\([^/]*\)\/.*$/\1/"`; do
echo "$DIR/$G" >> binlist
done
done
rm -fr `find xharbour-$VERSION -name CVS`
mv xharbour-${VERSION}/contrib ./contrib
mv xharbour-${VERSION}/tests ./tests
tar czvf xharbour-${VERSION}.src.tar.gz xharbour-${VERSION}
zip -rlq xharbour-${VERSION}.src.zip xharbour-${VERSION} -...@binlist
zip -rq xharbour-${VERSION}.src.zip -@ < binlist
mv xharbour-${VERSION} xharbour-core-${VERSION}
mkdir xharbour-${VERSION}
mv contrib xharbour-${VERSION}/
tar czvf xharbour-${VERSION}.src.contrib.tar.gz xharbour-${VERSION}
zip -rlq xharbour-${VERSION}.src.contrib.zip xharbour-${VERSION} -...@binlist
zip -rq xharbour-${VERSION}.src.contrib.zip -@ < binlist
mv xharbour-${VERSION} xharbour-contrib-${VERSION}
mkdir xharbour-${VERSION}
mv tests xharbour-${VERSION}/
tar czvf xharbour-${VERSION}.src.tests.tar.gz xharbour-${VERSION}
zip -rlq xharbour-${VERSION}.src.tests.zip xharbour-${VERSION} -...@binlist
zip -rq xharbour-${VERSION}.src.tests.zip -@ < binlist
mv xharbour-${VERSION} xharbour-tests-${VERSION}
-- Ph.
--
___
xHarbour-developers mailing list
xHarbour-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/xharbour-developers
