Quote from: Pascal on January 08, 2020, 08:41:46 amQuote from: wp on January 07, 2020, 10:20:34 pmQuote from: af0815 on January 07, 2020, 07:25:50 pmWith the decision of MvC here (https://bugs.freepascal.org/view.php?id=36525) ist looks impossible to use the fpexpression in the fpreport for calculating of aggregations and grouping on an non english configured system. On a german system the decimal seperator is a comma not a dot. If data is sent to fpexpression it must be converted to a non system standard value to be aggregated. The same problem i have found in the tests of fpreport, because the Formatsettings sometimes not handled Looking in the fcl-report/src directory I found a unit fprexprpars which is more or less a copy of the standard fpexprpars unit (note the additional "r" behind the "fp"); this was probably needed to provide dedicated adjustments of the parser for the report engine which should not be used in the standard parser. Maybe MvC changes his mind when the patch of the bug report is modified to apply to fprexprpars, not to fpexprpars?Can't find it! Did you mix it up with fprepexprpars, which is used for fpc versions below 030101?It is in the official sources of fpc trunk: https://svn.freepascal.org/cgi-bin/viewvc.cgi/trunk/packages/fcl-report/src/fprepexprpars.pp?view=log. If it is not needed any more it should be removed.
Quote from: wp on January 07, 2020, 10:20:34 pmQuote from: af0815 on January 07, 2020, 07:25:50 pmWith the decision of MvC here (https://bugs.freepascal.org/view.php?id=36525) ist looks impossible to use the fpexpression in the fpreport for calculating of aggregations and grouping on an non english configured system. On a german system the decimal seperator is a comma not a dot. If data is sent to fpexpression it must be converted to a non system standard value to be aggregated. The same problem i have found in the tests of fpreport, because the Formatsettings sometimes not handled Looking in the fcl-report/src directory I found a unit fprexprpars which is more or less a copy of the standard fpexprpars unit (note the additional "r" behind the "fp"); this was probably needed to provide dedicated adjustments of the parser for the report engine which should not be used in the standard parser. Maybe MvC changes his mind when the patch of the bug report is modified to apply to fprexprpars, not to fpexprpars?Can't find it! Did you mix it up with fprepexprpars, which is used for fpc versions below 030101?
Quote from: af0815 on January 07, 2020, 07:25:50 pmWith the decision of MvC here (https://bugs.freepascal.org/view.php?id=36525) ist looks impossible to use the fpexpression in the fpreport for calculating of aggregations and grouping on an non english configured system. On a german system the decimal seperator is a comma not a dot. If data is sent to fpexpression it must be converted to a non system standard value to be aggregated. The same problem i have found in the tests of fpreport, because the Formatsettings sometimes not handled Looking in the fcl-report/src directory I found a unit fprexprpars which is more or less a copy of the standard fpexprpars unit (note the additional "r" behind the "fp"); this was probably needed to provide dedicated adjustments of the parser for the report engine which should not be used in the standard parser. Maybe MvC changes his mind when the patch of the bug report is modified to apply to fprexprpars, not to fpexprpars?
With the decision of MvC here (https://bugs.freepascal.org/view.php?id=36525) ist looks impossible to use the fpexpression in the fpreport for calculating of aggregations and grouping on an non english configured system. On a german system the decimal seperator is a comma not a dot. If data is sent to fpexpression it must be converted to a non system standard value to be aggregated. The same problem i have found in the tests of fpreport, because the Formatsettings sometimes not handled