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.

--
Enrico Maria Giordano

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

> > 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

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

--
Enrico Maria Giordano

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

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

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?

--
Enrico Maria Giordano

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

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.

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?

--
Enrico Maria Giordano

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

> 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

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

--
Enrico Maria Giordano

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

>> ...
> > + 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

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. :-)

--
Enrico Maria Giordano

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

On 17/04/2023 12:45:28 am, Ron Pinkas wrote:
>> 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
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

Em quinta-feira, 13 de abril de 2023 às 19:20:46 UTC-3, Ron Pinkas escreveu:
> > > 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 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.

> 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

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

> 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! 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.

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

> 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

> > 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
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

> 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

Thanks! great job!

Reynaldo Henrique

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.

Em segunda-feira, 24 de abril de 2023 às 11:06:40 UTC-3, Leonardo Machado escreveu:
> 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.

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?

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?

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

> It's a fantastic new.
>
> Have you any date to upload the list of sources ?
>
> Thank you.
> Peter

As soon as I can.

Ron