OracleNumber weirdness

OracleNumber weirdness

Postby David Jud » Fri 19 Oct 2007 11:26

I was just testing the CoreLab.Oracle 4.20.22 trial. The following members are in OracleNumber:

public static double a(OracleNumber A_0);
public static long b(OracleNumber A_0);
public static int c(OracleNumber A_0);

I do not think these obfuscated members were meant to be public. :wink:

public static double ToDouble(ref OracleNumber val);
public static int ToInt32(OracleNumber val);
public static long ToInt64(ref OracleNumber val);

These are really nice - in CoreLab 3.55 I had always to use Decimal.ToDouble(number.Value). I hope that I can parse our geometries a bit faster with these.
But: I do not think they should be ref...

Best Regards, David
David Jud
 
Posts: 1
Joined: Fri 19 Oct 2007 11:11

Re: OracleNumber weirdness

Postby Alexey » Tue 23 Oct 2007 10:45

David Jud wrote:But: I do not think they should be ref...

We are gonna fix this.
Look forward to the next builds.
Alexey
 
Posts: 2756
Joined: Mon 13 Mar 2006 07:43

Postby Alexey » Tue 30 Oct 2007 16:46

Please try new version of OraDirect .NET 4.25.
Alexey
 
Posts: 2756
Joined: Mon 13 Mar 2006 07:43


Return to dotConnect for Oracle