Since this may affect the heavily relied upon sql library, has the sql
library been tested?
Thanks.
Blake
On Sun, Feb 22, 2015 at 10:57 AM, Juergen Sauermann <
juergen.sauerm...@t-online.de> wrote:
> Hi,
>
> in order to prevent the incorrect usage of constructors of class *Value*,
> I have mad
Hi Dirk,
thanks, fixed in SVN 538.
/// Jürgen
On 02/23/2015 08:02 AM, Dirk Laurie
wrote:
Current:
/// debug-print \b this value
void debug(const char * info);
Suggested:
/// debug-print \b this value unde
Hi Dirk,
probably the same as in your previous example.
The FloatScalar object might be destructed before the
second printout.
Try:
Value_P a = FloatScalar(3.141592653589793,LOC);
A Value_P is a pointer, so it is as efficient as a c
2015-02-22 21:48 GMT+02:00 Dirk Laurie :
> The folllowing program pinpoints what I do not understand about
> the use of Value and Value_P.
I am beginning to think it may be a bug. Here is a minimal example
of the phenomenon that causes it.
~~~
#include
using namespace std;
#include
main() {