Hi All,extensions by means of the contrib/xhb module.
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
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
Hi All,
This is to inform you that the xHarbour SourceForge repository has been ported with History to GitHub -> https://github.com/ronpinkas/xharbour
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 mostextensions 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.
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/xharbourI 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?
most extensions by means of the contrib/xhb module.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
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!). :-(
Fantastic Ron.
Will SQLRDD also be open source?
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?
most extensions by means of the contrib/xhb module.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
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!). :-(
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. :)
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. :)
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.
Hi Claudio,excluded.
The rdd "RMDBFCDX" is owned by xharbour.com, should it be available in this repo or will be kept maintained private?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
As a regular user of xharbour.com, I used it in some apps; my main concern is about the future.
Ron
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.
/*
* $Id: ChangeLog 10269 2022-11-18 22:32:16Z enricomaria $
*/
is now empty:
/*
* $Id$
*/
How to fix it?
Have you had the opportunity to talk to Lombardo about the release of SQLRDD or haven't you talked to him yet?
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
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.
/*
* $Id: ChangeLog 10269 2022-11-18 22:32:16Z enricomaria $
*/
is now empty:
/*
* $Id$
*/
How to fix it?
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
excluded.The rdd "RMDBFCDX" is owned by xharbour.com, should it be available in this repo or will be kept maintained private?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
As a regular user of xharbour.com, I used it in some apps; my main concern is about the future.
excluded.The rdd "RMDBFCDX" is owned by xharbour.com, should it be available in this repo or will be kept maintained private?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
As a regular user of xharbour.com, I used it in some apps; my main concern is about the future.
Thrilled to see all these wonderful tools being released on GitHub, allowing developers everywhere to utilize and improve them.
Patrick
I'm glad to hear such good news. I hope to find there VRW as well.
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.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
I will now start fixing ppgen to use the git generated $Id.
I'm glad to hear such good news. I hope to find there VRW as well.The start of it, yes.
😀
Patrick
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
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>The changelog still starts with
* source/pp/ppgen.c
* Modified to process new ChangeLog header after port to GIT from SVN
/*
* $Id$
*/
Do we have to wait the next commit for seeing the new Id?
--
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
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 ChangeLogSorry, I don't understand. I am not familiar with GitHub.
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.
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,
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.
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 coveringevery 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.
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
...They are not in the changelog:
+ Added sample use of HB_VER_CVSID and HB_VER_GITFAKEID
https://github.com/ronpinkas/xharbour/blob/main/ChangeLog
If I understood correctly, it is not possible, right?
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.
Hi,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
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 thesource codes of the part that belonged to xHarbour Commercial will be put on github?
Sorry for my bad english.
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
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 ***
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! Should now be fixed after:now this error appears
2023-04-20 11:08 UTC-0500 Ron Pinkas <ronpinkas/AT/gmail/com>
* source/pp/ppgen.c
* Fixed compiler warnings.
I just attempted to fix ALL outstanding compile warnings, except CODEPAGE related warnings. Should be fixed after:now this error appearsobj\b32\hbrc.c:
obj\b32\comptool.c:
Warning W8056 obj\b32\comptool.c 631: Integer arithmetic overflow in function hb_verCvsID
*** 1 errors in Compile ***
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
Hi All,extensions by means of the contrib/xhb module.
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
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.Good morning.
Greetings,
Ron
El dia dimecres, 10 de maig de 2023 a les 0:06:49 UTC+2, Ron Pinkas va escriure:Just for up this topic, waiting the release
It's a fantastic new.
Have you any date to upload the list of sources ?
Thank you.As soon as I can.
Peter
RonHi, Ron
It's fantastic, i wait impatiently...
:-)
Em quarta-feira, 10 de maio de 2023 às 04:37:35 UTC-3, Pere Cordonet escreveu:
El dia dimecres, 10 de maig de 2023 a les 0:06:49 UTC+2, Ron Pinkas va escriure:
It's a fantastic new.
Have you any date to upload the list of sources ?
Thank you.As soon as I can.
Peter
Just for up this topic, waiting the releaseRonHi, Ron
It's fantastic, i wait impatiently...
:-)
Em quarta-feira, 10 de maio de 2023 às 04:37:35 UTC-3, Pere Cordonet escreveu:
El dia dimecres, 10 de maig de 2023 a les 0:06:49 UTC+2, Ron Pinkas va escriure:
It's a fantastic new.
Have you any date to upload the list of sources ?
Thank you.As soon as I can.
Peter
Just for up this topic, waiting the releaseRonHi, Ron
It's fantastic, i wait impatiently...
:-)
Em sexta-feira, 16 de junho de 2023 às 09:24:51 UTC-3, Marco Aurélio escreveu:
Em quarta-feira, 10 de maio de 2023 às 04:37:35 UTC-3, Pere Cordonet escreveu:
El dia dimecres, 10 de maig de 2023 a les 0:06:49 UTC+2, Ron Pinkas va escriure:
It's a fantastic new.
Have you any date to upload the list of sources ?
Thank you.As soon as I can.
Peter
I didn´t succeeded to compile source with BCC58.Just for up this topic, waiting the releaseRonHi, Ron
It's fantastic, i wait impatiently...
:-)
It compiled with GCC 13.1.0 and Bison.
Em sábado, 24 de junho de 2023 às 13:08:00 UTC-3, Anderson Cardoso escreveu:
Em sexta-feira, 16 de junho de 2023 às 09:24:51 UTC-3, Marco Aurélio escreveu:
Em quarta-feira, 10 de maio de 2023 às 04:37:35 UTC-3, Pere Cordonet escreveu:
El dia dimecres, 10 de maig de 2023 a les 0:06:49 UTC+2, Ron Pinkas va escriure:
It's a fantastic new.
Have you any date to upload the list of sources ?
Thank you.As soon as I can.
Peter
GTDOS LIB FOR CONSOLE MODEI didn´t succeeded to compile source with BCC58.Just for up this topic, waiting the releaseRonHi, Ron
It's fantastic, i wait impatiently...
:-)
It compiled with GCC 13.1.0 and Bison.
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
On Tuesday, July 4, 2023 at 6:49:45 AM UTC+8, Anderson Cardoso wrote:
Em sábado, 24 de junho de 2023 às 13:08:00 UTC-3, Anderson Cardoso escreveu:
Em sexta-feira, 16 de junho de 2023 às 09:24:51 UTC-3, Marco Aurélio escreveu:
Em quarta-feira, 10 de maio de 2023 às 04:37:35 UTC-3, Pere Cordonet escreveu:
El dia dimecres, 10 de maig de 2023 a les 0:06:49 UTC+2, Ron Pinkas va escriure:
It's a fantastic new.
Have you any date to upload the list of sources ?
Thank you.As soon as I can.
Peter
GTDOS LIB FOR CONSOLE MODEI didn´t succeeded to compile source with BCC58.Just for up this topic, waiting the releaseRonHi, Ron
It's fantastic, i wait impatiently...
:-)
It compiled with GCC 13.1.0 and Bison.
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 directoryhi Anderson Cardoso,
collect2.exe: error: ld returned 1 exit status
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.Dear Ron,
Dear Ron,
Some news about commit with other libraries (SQLRDD, Visual xHarbour, etc) ?
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
Ron, I don't think it's that important to keep history in these cases.
Em terça-feira, 25 de julho de 2023 às 13:26:14 UTC-3, Ron Pinkas escreveu:
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
Em terça-feira, 25 de julho de 2023 às 14:27:25 UTC-3, Eduardo Motta escreveu:
Ron, I don't think it's that important to keep history in these cases.
Em terça-feira, 25 de julho de 2023 às 13:26:14 UTC-3, Ron Pinkas escreveu:
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, I agree with Eduardo.Ron
Let´s get it working and start a new history from now on! Don´t worry about it.
| Sysop: | Keyop |
|---|---|
| Location: | Huddersfield, West Yorkshire, UK |
| Users: | 354 |
| Nodes: | 16 (3 / 13) |
| Uptime: | 38:44:15 |
| Calls: | 7,650 |
| Calls today: | 2 |
| Files: | 12,811 |
| Messages: | 5,699,465 |