Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
Groups keyboard shortcuts have been updated
Dismiss
See shortcuts

Repository moved to https://github.com/ronpinkas/xharbour

1,334 views
Skip to first unread message

Ron Pinkas

unread,
Apr 9, 2023, 2:39:25 AM4/9/23
to
Hi All,

This is to inform you that the xHarbour SourceForge repository has been ported with History to GitHub -> https://github.com/ronpinkas/xharbour

I was not able to set all contributors emails, and contributors should have a GitHub account with respective email to be credited for their contributions. Should any contributor require assistance please feel welcome to contact me.

Developers that wish to contribute, please contact me to get Write Access, and/or Admin access rights if applicable.

For what its worth I believe the Harbour project: https://github.com/harbour/core may provide a better solution due to much improved core code. While it does not offer all of xHarbour's features and extensions, it does provide optional support for most extensions by means of the contrib/xhb module.

In the alternate, should any developer[s] wish to bring xHarbour up to date I would recommend forking Harbour and reimplementing remaining xHarbour's unique features on top of Harbour's cleaner code base.

Greetings,

Ron

Ron Pinkas

unread,
Apr 9, 2023, 3:12:12 AM4/9/23
to
FWIW, I hope to soon release as open source: xEdit, xBuild, and WinAPI including wrappers to set Functions and Methods as direct Windows Callback pointers.

Eduardo Motta

unread,
Apr 10, 2023, 7:02:51 AM4/10/23
to
Fantastic Ron.

Will SQLRDD also be open source?

Enrico Maria Giordano

unread,
Apr 10, 2023, 8:14:08 AM4/10/23
to


Il 09/04/2023 08:39, Ron Pinkas ha scritto:

> Hi All,
>
> This is to inform you that the xHarbour SourceForge repository has been ported with History to GitHub -> https://github.com/ronpinkas/xharbour

I changed the Changelog url in xharbour.org to reflect the new one. But
I noticed one difference in the id section at the very top of the file:

/*
* $Id: ChangeLog 10269 2022-11-18 22:32:16Z enricomaria $
*/

is now empty:

/*
* $Id$
*/

How to fix it?

> For what its worth I believe the Harbour project: https://github.com/harbour/core may provide a better solution due to much improved core code. While it does not offer all of xHarbour's features and extensions, it does provide optional support for most extensions by means of the contrib/xhb module.
>
> In the alternate, should any developer[s] wish to bring xHarbour up to date I would recommend forking Harbour and reimplementing remaining xHarbour's unique features on top of Harbour's cleaner code base.

I don't think there is still anybody that is able or willing to do that
work (a lot of work!). :-(

--
Enrico Maria Giordano

http://www.emagsoftware.it
http://www.emagsoftware.it/emgmusic
http://www.emagsoftware.it/spectrum
http://www.emagsoftware.it/tbosg

Message has been deleted

Ron Pinkas

unread,
Apr 10, 2023, 11:29:26 AM4/10/23
to
On Monday, April 10, 2023 at 6:02:51 AM UTC-5, Eduardo Motta wrote:
> Fantastic Ron.
>
> Will SQLRDD also be open source?

SQLRDD is not my code, and it is still in commercial use by its owner.

Ron Pinkas

unread,
Apr 10, 2023, 11:34:35 AM4/10/23
to
> I changed the Changelog url in xharbour.org to reflect the new one. But
> I noticed one difference in the id section at the very top of the file:
>
> /*
> * $Id: ChangeLog 10269 2022-11-18 22:32:16Z enricomaria $
> */
>
> is now empty:
>
> /*
> * $Id$
> */
>
> How to fix it?

I have no clue. :)

> > For what its worth I believe the Harbour project: https://github.com/harbour/core may provide a better solution due to much improved core code. While it does not offer all of xHarbour's features and extensions, it does provide optional support for most extensions by means of the contrib/xhb module.
> >
> > In the alternate, should any developer[s] wish to bring xHarbour up to date I would recommend forking Harbour and reimplementing remaining xHarbour's unique features on top of Harbour's cleaner code base.
> I don't think there is still anybody that is able or willing to do that
> work (a lot of work!). :-(

Where there's a will there's a way. :)

Ron

Enrico Maria Giordano

unread,
Apr 10, 2023, 12:49:14 PM4/10/23
to


Il 10/04/2023 17:34, Ron Pinkas ha scritto:

>> I changed the Changelog url in xharbour.org to reflect the new one. But
>> I noticed one difference in the id section at the very top of the file:
>>
>> /*
>> * $Id: ChangeLog 10269 2022-11-18 22:32:16Z enricomaria $
>> */
>>
>> is now empty:
>>
>> /*
>> * $Id$
>> */
>>
>> How to fix it?
>
> I have no clue. :)

Ok. :-(

>> I don't think there is still anybody that is able or willing to do that
>> work (a lot of work!). :-(
>
> Where there's a will there's a way. :)

Of course.

CV

unread,
Apr 10, 2023, 8:18:59 PM4/10/23
to
Hi Ron

Thank you for porting it.

The rdd "RMDBFCDX" is owned by xharbour.com, should it be available in this repo or will be kept maintained private?
As a regular user of xharbour.com, I used it in some apps; my main concern is about the future.

Regards,
--
Claudio Voskian
Buenos Aires - Argentina

Ron Pinkas

unread,
Apr 13, 2023, 3:02:01 PM4/13/23
to
Hi Claudio,

> The rdd "RMDBFCDX" is owned by xharbour.com, should it be available in this repo or will be kept maintained private?
> As a regular user of xharbour.com, I used it in some apps; my main concern is about the future.

I just spoke to Patrick, and I am happy to announce that we have decided to release ALL of xHarbour.com's proprietary sources (including Visual[x]Harbour, and RMDBFCDX) to Open Source. Please note that SQLRDD is not owned by xHarbour.com so it is excluded.

Ron

Eduardo Motta

unread,
Apr 13, 2023, 3:11:36 PM4/13/23
to
Great news Ron.

Have you had the opportunity to talk to Lombardo about the release of SQLRDD or haven't you talked to him yet?

Eduardo Motta

Ron Pinkas

unread,
Apr 13, 2023, 3:51:51 PM4/13/23
to
> /*
> * $Id: ChangeLog 10269 2022-11-18 22:32:16Z enricomaria $
> */
>
> is now empty:
>
> /*
> * $Id$
> */
>
> How to fix it?

FWIW I just moved /xharbour/* to the root to avoid redundancy. So you might need to revise natch files, etc.

Ron Pinkas

unread,
Apr 13, 2023, 3:55:06 PM4/13/23
to
> Have you had the opportunity to talk to Lombardo about the release of SQLRDD or haven't you talked to him yet?

We have a talk scheduled for later this eve, but to be honest I think this is not very likely because Marcelo has a very successful company built around his SQLRDD.

Ron

Eduardo Motta

unread,
Apr 13, 2023, 4:29:27 PM4/13/23
to
I know Omie.

Lombardo is a reference.

Ron Pinkas

unread,
Apr 13, 2023, 6:20:46 PM4/13/23
to
> > Have you had the opportunity to talk to Lombardo about the release of SQLRDD or haven't you talked to him yet?

> We have a talk scheduled for later this eve, but to be honest I think this is not very likely because Marcelo has a very successful company built around his SQLRDD.

I Just spoke to Marcelo and he agreed to release SQLRDD as open source - so I will upload that too.

Ron

Ron Pinkas

unread,
Apr 14, 2023, 1:11:50 AM4/14/23
to
Enrico,

> /*
> * $Id: ChangeLog 10269 2022-11-18 22:32:16Z enricomaria $
> */
>
> is now empty:
>
> /*
> * $Id$
> */
>
> How to fix it?

I found out that git does not support version control in that way, instead it can expand $Id$ to a hash of the commit. I did enable it and found that the build was failing because ppgen.c was expecting the OLD stile $Id tag. I am importing such modifications from Harbour, but it also entails many file related sources to be moved from source/rtl to source/common. I am working on this commit but it may take some time.

Ron

Eduardo Motta

unread,
Apr 14, 2023, 7:45:59 AM4/14/23
to
Ron this is amazing!

thank you so much to all of you for what you have done for the community.

When it's available on github please let me know.

Patrick Mast

unread,
Apr 14, 2023, 8:49:51 AM4/14/23
to

> > The rdd "RMDBFCDX" is owned by xharbour.com, should it be available in this repo or will be kept maintained private?
> > As a regular user of xharbour.com, I used it in some apps; my main concern is about the future.
> I just spoke to Patrick, and I am happy to announce that we have decided to release ALL of xHarbour.com's proprietary sources (including Visual[x]Harbour, and RMDBFCDX) to Open Source. Please note that SQLRDD is not owned by xHarbour.com so it is excluded.

Thrilled to see all these wonderful tools being released on GitHub, allowing developers everywhere to utilize and improve them.

Patrick

Ella Stern

unread,
Apr 14, 2023, 3:19:53 PM4/14/23
to
I'm glad to hear such good news. I hope to find there VRW as well.

Ella

Patrick Mast

unread,
Apr 14, 2023, 7:19:02 PM4/14/23
to
> I'm glad to hear such good news. I hope to find there VRW as well.

The start of it, yes.

😀

Patrick

Ron Pinkas

unread,
Apr 14, 2023, 8:54:20 PM4/14/23
to
> > How to fix it?

> I found out that git does not support version control in that way, instead it can expand $Id$ to a hash of the commit. I did enable it and found that the build was failing because ppgen.c was expecting the OLD stile $Id tag. I am importing such modifications from Harbour, but it also entails many file related sources to be moved from source/rtl to source/common. I am working on this commit but it may take some time.
>

I just temporarily hacked the ChangeLog $Id to the last one used by SVN just to allow me to build cleanly without modifications to the ported sources, so I could confirm we are ok. I am currently using MacOS so I had to commit few fixes, and we can now use make_drw.sh to build correctly.

I will now start fixing ppgen to use the git generated $Id.

Ron

Ron Pinkas

unread,
Apr 15, 2023, 2:42:32 AM4/15/23
to
> I will now start fixing ppgen to use the git generated $Id.

2023-04-15 00:52 UTC-0500 Ron Pinkas <ronpinkas/AT/gmail/com>
* source/pp/ppgen.c
* Modified to process new ChangeLog header after port to GIT from SVN

Ella Stern

unread,
Apr 15, 2023, 3:51:19 AM4/15/23
to
Thank you Patrick :-)

Enrico Maria Giordano

unread,
Apr 15, 2023, 5:54:14 AM4/15/23
to
The changelog still starts with

/*
* $Id$
*/

Do we have to wait the next commit for seeing the new Id?

Ron Pinkas

unread,
Apr 15, 2023, 4:24:05 PM4/15/23
to
On Saturday, April 15, 2023 at 2:54:14 AM UTC-7, Enrico Maria Giordano wrote:
> Il 15/04/2023 08:42, Ron Pinkas ha scritto:
>
> >> I will now start fixing ppgen to use the git generated $Id.
> >
> > 2023-04-15 00:52 UTC-0500 Ron Pinkas <ronpinkas/AT/gmail/com>
> > * source/pp/ppgen.c
> > * Modified to process new ChangeLog header after port to GIT from SVN
> The changelog still starts with
>
> /*
> * $Id$
> */
>
> Do we have to wait the next commit for seeing the new Id?
> --
>
No, it's a subtlty og GIT because you had it from before the tag. Remove your repository and clone it again, or ar the root just type git checkout ChangeLog

Enrico Maria Giordano

unread,
Apr 15, 2023, 5:15:09 PM4/15/23
to


Il 15/04/2023 22:24, Ron Pinkas ha scritto:

>> The changelog still starts with
>>
>> /*
>> * $Id$
>> */
>>
>> Do we have to wait the next commit for seeing the new Id?
>
> No, it's a subtlty og GIT because you had it from before the tag. Remove your repository and clone it again, or ar the root just type git checkout ChangeLog

Sorry, I don't understand. I am not familiar with GitHub.

Ron Pinkas

unread,
Apr 15, 2023, 5:50:54 PM4/15/23
to

> > No, it's a subtlty og GIT because you had it from before the tag. Remove your repository and clone it again, or ar the root just type git checkout ChangeLog
> Sorry, I don't understand. I am not familiar with GitHub.

Enrico, just remove the xharbour folder and then get it again same as you did before, or at the xharbour folder type:

git checkout ChangeLog

Eitherway it will fix your problem.

Ron

Enrico Maria Giordano

unread,
Apr 16, 2023, 2:44:05 AM4/16/23
to


Il 15/04/2023 23:50, Ron Pinkas ha scritto:

>> Sorry, I don't understand. I am not familiar with GitHub.
>
> Enrico, just remove the xharbour folder and then get it again same as you did before, or at the xharbour folder type:
>
> git checkout ChangeLog
>
> Eitherway it will fix your problem.

It is not MY problem, it is GitHub problem:

https://github.com/ronpinkas/xharbour/blob/main/ChangeLog

Ron Pinkas

unread,
Apr 16, 2023, 3:12:18 AM4/16/23
to
Enrico this is not a problem. This is how git works. The ID is generated when the file is being checked out. Just try erasing and starting from scratch.

Enrico Maria Giordano

unread,
Apr 16, 2023, 5:26:56 AM4/16/23
to


Il 16/04/2023 09:12, Ron Pinkas ha scritto:

> Enrico this is not a problem. This is how git works. The ID is generated when the file is being checked out. Just try erasing and starting from scratch.

Ok. I downloaded the ZIP file from GitHub and get this in the changelog:

/*
* $Id: e21093e66657719fd8e9737f1915db80fd52e83d $
*/

It is not very friendly as version number, is it? What do we have to use
as version number now?

Ron Pinkas

unread,
Apr 16, 2023, 12:13:42 PM4/16/23
to
Enrico,

> Ok. I downloaded the ZIP file from GitHub and get this in the changelog:

Git is an open source distributed version control system - you should use it much like you used SVN. Instead of downloading sources using a ZIP file you should install Git for your O/S and then "checkout" xHarbour code using the command (or GUI Equivalent):

git clone https://github.com/ronpinkas/xharbour.git

If you are not familiar yet with Visual Studio Code (VSCode), I highly recommend you give it a try. It is open source, written in JavaScript and It is probably today's most popular IDE. It has a very reach echo system with infinite plug-ins covering every aspect of modern development, including built-in support for Git.

> /*
> * $Id: e21093e66657719fd8e9737f1915db80fd52e83d $
> */
>
> It is not very friendly as version number, is it? What do we have to use
> as version number now?

Yes, it's the source of many heated discussions - the ID is a HASH representing a unique commit state of the source file. But no worries, I already committed changes to ppgen.c that simulate a Version Number based on the DATE and TIME.

Ron

Enrico Maria Giordano

unread,
Apr 16, 2023, 12:54:31 PM4/16/23
to


Il 16/04/2023 18:13, Ron Pinkas ha scritto:

> Enrico,
>
>> Ok. I downloaded the ZIP file from GitHub and get this in the changelog:
>
> Git is an open source distributed version control system - you should use it much like you used SVN.

Yes, I know, but I haven't planned to use it yet. Is TortoiseGit a good
tool for that?

> If you are not familiar yet with Visual Studio Code (VSCode), I highly recommend you give it a try. It is open source, written in JavaScript and It is probably today's most popular IDE. It has a very reach echo system with infinite plug-ins covering every aspect of modern development, including built-in support for Git.

Thank you, but I prefer my personal tools for my development work.

>> /*
>> * $Id: e21093e66657719fd8e9737f1915db80fd52e83d $
>> */
>>
>> It is not very friendly as version number, is it? What do we have to use
>> as version number now?
>
> Yes, it's the source of many heated discussions - the ID is a HASH representing a unique commit state of the source file. But no worries, I already committed changes to ppgen.c that simulate a Version Number based on the DATE and TIME.

Ok, good. Is it possible to see it here?

https://github.com/ronpinkas/xharbour/blob/main/ChangeLog

If I understood correctly, it is not possible, right?

Ron Pinkas

unread,
Apr 16, 2023, 3:15:29 PM4/16/23
to
> https://github.com/ronpinkas/xharbour/blob/main/ChangeLog
>
> If I understood correctly, it is not possible, right?

I am not an expert in Git - I suspect that because of its distributed nature it would not make sense. Each checked out version of the file gets its own ID.

FWIW, I just posted:

2023-04-16 14:10 UTC-0500 Ron Pinkas <ronpinkas/AT/gmail/com>
* .gitignore
+ Added tests\*.c to ignore generated test files.
* source/pp/ppgen.c
+ Added missing legacy #define HB_VER_CVSID
* tests/Makefile
! Fixed multiple errors in Makefile.
+ tests/make_gnu.sh
+ New script to build tests using GNU make.
* tests/test.prg
+ Added sample use of HB_VER_CVSID and HB_VER_GITFAKEID

Enrico Maria Giordano

unread,
Apr 16, 2023, 3:26:10 PM4/16/23
to


Il 16/04/2023 21:15, Ron Pinkas ha scritto:

>> https://github.com/ronpinkas/xharbour/blob/main/ChangeLog
>>
>> If I understood correctly, it is not possible, right?
>
> I am not an expert in Git - I suspect that because of its distributed nature it would not make sense. Each checked out version of the file gets its own ID.

With SVN it is possible.

> FWIW, I just posted:
>
> 2023-04-16 14:10 UTC-0500 Ron Pinkas <ronpinkas/AT/gmail/com>
> * .gitignore
> + Added tests\*.c to ignore generated test files.
> * source/pp/ppgen.c
> + Added missing legacy #define HB_VER_CVSID
> * tests/Makefile
> ! Fixed multiple errors in Makefile.
> + tests/make_gnu.sh
> + New script to build tests using GNU make.
> * tests/test.prg
> + Added sample use of HB_VER_CVSID and HB_VER_GITFAKEID

They are not in the changelog:

https://github.com/ronpinkas/xharbour/blob/main/ChangeLog

Ron Pinkas

unread,
Apr 16, 2023, 3:32:20 PM4/16/23
to
>> ...
> > + Added sample use of HB_VER_CVSID and HB_VER_GITFAKEID
> They are not in the changelog:
>

Sorry, I forgot to commit (push) - Or I was just making sure someone is checking :)

Should be there now.

Ron

Enrico Maria Giordano

unread,
Apr 16, 2023, 4:55:51 PM4/16/23
to


Il 16/04/2023 21:32, Ron Pinkas ha scritto:

>> They are not in the changelog:
>>
>
> Sorry, I forgot to commit (push) - Or I was just making sure someone is checking :)
>
> Should be there now.

Yes, it's ok now. :-)

Jayadev U

unread,
Apr 16, 2023, 11:21:56 PM4/16/23
to
Hi,

We could use Git 'Tag' command to give meaningful ids to each version.

More details here:
https://www.atlassian.com/git/tutorials/inspecting-a-repository/git-tag

HTH,

Wbr,

Jayadev

Eduardo Motta

unread,
Apr 19, 2023, 9:24:53 AM4/19/23
to
Em quinta-feira, 13 de abril de 2023 às 19:20:46 UTC-3, Ron Pinkas escreveu:
Ron good morning.

I understand that your work on the xHarbour project is voluntary work and I am very grateful for the many years of effort and dedication you have put into this project, so please do not take this as a charge, but there is a prediction of when the source codes of the part that belonged to xHarbour Commercial will be put on github?

Sorry for my bad english.

Ron Pinkas

unread,
Apr 19, 2023, 9:35:22 AM4/19/23
to
> I understand that your work on the xHarbour project is voluntary work and I am very grateful for the many years of effort and dedication you have put into this project, so please do not take this as a charge, but there is a prediction of when the source codes of the part that belonged to xHarbour Commercial will be put on github?
>
> Sorry for my bad english.

Few Days.

Ron

reina...@gmail.com

unread,
Apr 20, 2023, 8:35:25 PM4/20/23
to
Hi,
There are the folloing error before,

MAKE Version 5.41 Copyright (c) 1987, 2014 Embarcadero Technologies, Inc.
source\pp\ppgen.c:
Warning W8004 source\pp\ppgen.c 714: 'szUTC' is assigned a value that is never used in function hb_pp_parseChangelog
Warning W8004 source\pp\ppgen.c 714: 'szTo' is assigned a value that is never used in function hb_pp_parseChangelog
Warning W8004 source\pp\ppgen.c 714: 'szFrom' is assigned a value that is never used in function hb_pp_parseChangelog
*** 1 errors in Compile ***

Thanks

Reynaldo Henrique

Ron Pinkas

unread,
Apr 20, 2023, 11:06:39 PM4/20/23
to
Thanks! Should now be fixed after:

2023-04-20 11:08 UTC-0500 Ron Pinkas <ronpinkas/AT/gmail/com>
* source/pp/ppgen.c
* Fixed compiler warnings.

reina...@gmail.com

unread,
Apr 21, 2023, 2:29:35 AM4/21/23
to
Ron,

> Thanks! Should now be fixed after:
>
> 2023-04-20 11:08 UTC-0500 Ron Pinkas <ronpinkas/AT/gmail/com>
> * source/pp/ppgen.c
> * Fixed compiler warnings.
now this error appears
obj\b32\comptool.c:
Warning W8056 obj\b32\comptool.c 631: Integer arithmetic overflow in function hb_verCvsID
*** 1 errors in Compile ***

Thanks for your help,

Reynaldo Henrque

reina...@gmail.com

unread,
Apr 21, 2023, 2:34:09 AM4/21/23
to

> now this error appears
> obj\b32\comptool.c:
> Warning W8056 obj\b32\comptool.c 631: Integer arithmetic overflow in function hb_verCvsID
> *** 1 errors in Compile ***

obj\b32\hbrc.c:
Warning W8056 obj\b32\hbrc.c 359: Integer arithmetic overflow in function main
Warning W8056 obj\b32\hbrc.c 360: Integer arithmetic overflow in function main
Warning W8056 obj\b32\hbrc.c 380: Integer arithmetic overflow in function main
Warning W8056 obj\b32\hbrc.c 384: Integer arithmetic overflow in function main
*** 1 errors in Compile ***

Reynaldo Henrique

Ron Pinkas

unread,
Apr 23, 2023, 1:06:08 AM4/23/23
to
I just attempted to fix ALL outstanding compile warnings, except CODEPAGE related warnings. Should be fixed after:

2023-04-22 23:55 UTC-0500 Ron Pinkas <ronpinkas/AT/gmail/com>
* .gitignore
+ *.log|ppo|pp$ tests/*.c
* make_drw.sh
* Added to C_USR "-Wno-invalid-source-encoding"

* contrib/hbssl/err.c
* contrib/hbssl/ssl.c
* contrib/hbssl/sslciph.c
* contrib/rdd_ads/adsfunc.c
* source/common/hbwince.c
* source/odbc/odbc.c
* source/rtl/filesys.c
* source/rtl/fstemp.c
! Fixed compiler warnings - Corrected char iniitialization from '\0' to 0

* include/hbapi.h
* source/compiler/comptool.c
* source/pp/ppgen.c
* source/vm/cmdarg.c
! Fixed compiler warning - return value of hb_verCvsID() int to long long int

* include/set.ch
+ Added missing constants:
#define HB_SET_TRACESTACK_NONE 0
#define HB_SET_TRACESTACK_CURRENT 1
#define HB_SET_TRACESTACK_ALL 2

* source/common/hbmem.c
* Protected with #ifndef HB_NO_DV_MEMCPY

* source/compiler/cmdcheck.c
* Fixed compiler warnings - apparent typo in bit masking: & ( 2 ^ 6 ) -> & ((1 << 6) - 1) !!!

* source/compiler/harbour.sly
* Corrected deprecated %name-prefix "hb_comp_yy" to %define api.prefix {hb_comp_yy}

* source/ct/dattime2.c
! Fixed compiler warning - Apparent typo, corrected: && to || !!!

* source/ct/disk.c
! Fixed compiler warning - protected windows specific code with #ifdef HB_OS_WIN

* source/ct/files.c
! Fixed compiler warning - added: HB_SYMBOL_UNUSED( szFile );

* source/ct/settime.c
! Fixed compiler warning - commented unused variable: fResult

* source/macro/Makefile
- Removed -p hb_comp_yy from YACC_FLAGS
* source/macro/macro.slx
* Added #define YYSTYPE HB_MACRO_YYSTYPE
* source/macro/macro.y
* Fixed compiler warnings - Corrected deprecated %pure-parser to %define api.pure
and %name-prefix "hb_macro_yy" to %define api.prefix {hb_macro_yy}
* source/macro/macroyy.c
* Fixed compiler warnings - corrected deprecated %name-prefix "hb_macro_yy" to %define api.prefix {hb_macro_yy}

* source/rdd/hbsix/sxtable.c
! Fixed compiler warning - Apparent typo, corrected: || to && !!!

* source/rtl/filenet.c
! Fixed compiler warning - %hu to %u and cast to void * by interim (intptr_t) cast

* source/rtl/gtcrs/gtcrs.c
* source/rtl/gttrm/gttrm.c
! Fixed compiler warning - %hd to %d

* source/rtl/gtxwc/gtxwc.c
! Fixed compiler warning - type cast to const char * and Commented un used variable: whiteColor

* source/rtl/pcre/pcre_study.c
! Fixed compiler warning - Apparent typo corrected: && to & on line 1258 !!!

* source/tip/cgi.prg
! Fixed compiler warning - commented out 2 unused STATIC function_exists

* source/vm/classes.c
! Fixed compiler warning - Apparent typo corrected: && to & !!!

* source/vm/hbservmt.c
! Fixed compiler warning - Unused variable: pStack

* source/vm/itemapi.c
! Fixed compiler warning - Added:
#elif defined(__APPLE__)
#define HB_FINITE_DBL( d ) ( isfinite( d ) != 0 )

* tests/tsttrace.prg
- Removed no longer needed: #defines

* utils/hbfilere/hbfilere.c
! Fixed compiler warning - wrong type of main, wrong format specifiers and missing type casts

* utils/misc/hbrc.c
! Fixed compiler warning - wrong format specifiers

* utils/xbscript/xbscript.prg
! Fixed bug in NextExp() - missing LOOP after ++/-- post op

* winmake/makefile.gc
- Removed -p hb_comp_yy from Bison flags

reina...@gmail.com

unread,
Apr 23, 2023, 11:02:44 PM4/23/23
to
Thanks! great job!


Reynaldo Henrique

Leonardo Machado

unread,
Apr 24, 2023, 10:06:40 AM4/24/23
to
Em domingo, 9 de abril de 2023 às 03:39:25 UTC-3, Ron Pinkas escreveu:
> Hi All,
>
> This is to inform you that the xHarbour SourceForge repository has been ported with History to GitHub -> https://github.com/ronpinkas/xharbour
>
> I was not able to set all contributors emails, and contributors should have a GitHub account with respective email to be credited for their contributions. Should any contributor require assistance please feel welcome to contact me.
>
> Developers that wish to contribute, please contact me to get Write Access, and/or Admin access rights if applicable.
>
> For what its worth I believe the Harbour project: https://github.com/harbour/core may provide a better solution due to much improved core code. While it does not offer all of xHarbour's features and extensions, it does provide optional support for most extensions by means of the contrib/xhb module.
>
> In the alternate, should any developer[s] wish to bring xHarbour up to date I would recommend forking Harbour and reimplementing remaining xHarbour's unique features on top of Harbour's cleaner code base.
>
> Greetings,
>
> Ron
Good morning.
Congratulations on the initiative, for me who use xharbour every day this sounds like music in my ear, if I can be of any help I am available. A great week everyone.

Anderson Cardoso

unread,
May 7, 2023, 10:15:26 AM5/7/23
to
It´s not compiling...
I got this:

MAKE Version 5.2 Copyright (c) 1987, 2000 Borland
obj\b32\harboury.c:
Error E2141 harboury.c 4545: Declaration syntax error in function hb_comp_yyparse
*** 1 errors in Compile ***

** error 1 ** deleting obj\b32\harboury.obj

I have Borland C at \BCC58 and Bison at \GnuWin32, I think it should be ok.
How to compile from this source?

Dan Campbell

unread,
May 7, 2023, 3:03:16 PM5/7/23
to
On Sunday, April 9, 2023 at 2:39:25 AM UTC-4, Ron Pinkas wrote:
> Hi All,
>
> This is to inform you that the xHarbour SourceForge repository has been ported with History to GitHub -> https://github.com/ronpinkas/xharbour
>
> I was not able to set all contributors emails, and contributors should have a GitHub account with respective email to be credited for their contributions. Should any contributor require assistance please feel welcome to contact me.
>
> Developers that wish to contribute, please contact me to get Write Access, and/or Admin access rights if applicable.
>
> For what its worth I believe the Harbour project: https://github.com/harbour/core may provide a better solution due to much improved core code. While it does not offer all of xHarbour's features and extensions, it does provide optional support for most extensions by means of the contrib/xhb module.
>
> In the alternate, should any developer[s] wish to bring xHarbour up to date I would recommend forking Harbour and reimplementing remaining xHarbour's unique features on top of Harbour's cleaner code base.
>
> Greetings,
>
> Ron

Pat & Ron,

Congratulations on a long run, and thanks for helping to keep Xbase alive.


Two questions:

1. Will the executables be available, without having to build them?

2. Do you or Pat have a Paypal donation option, so we can send a thanks from time to time?



Pere Cordonet

unread,
May 9, 2023, 11:24:55 AM5/9/23
to
El dia divendres, 14 d’abril de 2023 a les 0:20:46 UTC+2, Ron Pinkas va escriure:
> > > Have you had the opportunity to talk to Lombardo about the release of SQLRDD or haven't you talked to him yet?
>
> > We have a talk scheduled for later this eve, but to be honest I think this is not very likely because Marcelo has a very successful company built around his SQLRDD.
> I Just spoke to Marcelo and he agreed to release SQLRDD as open source - so I will upload that too.
>
> Ron

Hi Ron,
It's a fantastic new.

Have you any date to upload the list of sources ?

Thank you.
Peter

Ron Pinkas

unread,
May 9, 2023, 6:06:49 PM5/9/23
to
> It's a fantastic new.
>
> Have you any date to upload the list of sources ?
>
> Thank you.
> Peter

As soon as I can.

Ron

Pere Cordonet

unread,
May 10, 2023, 3:37:35 AM5/10/23
to
El dia dimecres, 10 de maig de 2023 a les 0:06:49 UTC+2, Ron Pinkas va escriure:
Hi, Ron
It's fantastic, i wait impatiently...
:-)

Marco Aurélio

unread,
Jun 16, 2023, 8:24:51 AM6/16/23
to
Just for up this topic, waiting the release
Message has been deleted

Anderson Cardoso

unread,
Jun 24, 2023, 12:08:00 PM6/24/23
to
I didn´t succeeded to compile source with BCC58.
It compiled with GCC 13.1.0 and Bison.

Anderson Cardoso

unread,
Jul 3, 2023, 6:49:45 PM7/3/23
to
GTDOS LIB FOR CONSOLE MODE

C:\MinGW32\bin\gcc @makefile.lnk
C:/MinGW32/bin/../lib/gcc/i686-w64-mingw32/13.1.0/../../../../i686-w64-mingw32/bin/ld.exe: cannot find -lgtdos: No such file or directory
collect2.exe: error: ld returned 1 exit status

kenny.ooi

unread,
Jul 5, 2023, 7:02:21 AM7/5/23
to
hi Anderson Cardoso,
GTDOS is for dos only,
the GCC 13.1.0 not for dos is for windows or linux.
for console mode you can use gtwin or gtwvt.


kenny.

Marco Aurélio

unread,
Jul 25, 2023, 11:05:11 AM7/25/23
to
Dear Ron,

Some news about commit with other libraries (SQLRDD, Visual xHarbour, etc) ?

Ron Pinkas

unread,
Jul 25, 2023, 12:26:14 PM7/25/23
to
On Tuesday, July 25, 2023 at 10:05:11 AM UTC-5, Marco Aurélio wrote:

> Dear Ron,
>
> Some news about commit with other libraries (SQLRDD, Visual xHarbour, etc) ?

Sadly not yet. It seems that moving sub folders of GIT with history is not so trivial - I did spend many hours tryinbg to learn - I will find someway to do it but it takes more time and effort than I currently havem but I am still committed.

Ron

Eduardo Motta

unread,
Jul 25, 2023, 1:27:25 PM7/25/23
to
Ron, I don't think it's that important to keep history in these cases.

Anderson Cardoso

unread,
Aug 7, 2023, 5:50:46 PM8/7/23
to
Ron, I agree with Eduardo.
Let´s get it working and start a new history from now on! Don´t worry about it.

Pere Cordonet

unread,
Aug 9, 2023, 6:38:24 AM8/9/23
to
El dia dilluns, 7 d’agost de 2023 a les 23:50:46 UTC+2, Anderson Cardoso va escriure:
Hi Ron,

I agree with Eduardo too.

Thank you.
Pere.
0 new messages