/macosx-10.9.5/CF-855.17/ |
H A D | CFString.c | 5303 /* Only come in here if spec->type is CFFormatLongType or CFFormatDoubleType. Pass in 0 for width or precision if not specified. Returns false if couldn't do the format (with the assumption the caller falls back to unlocalized). 5305 static Boolean __CFStringFormatLocalizedNumber(CFMutableStringRef output, CFLocaleRef locale, const CFPrintValue *values, const CFFormatSpec *spec, SInt32 width, SInt32 precision, Boolean hasPrecision) { argument 5358 SInt32 prec = hasPrecision ? precision : ((spec->type == CFFormatLongType) ? 0 : 6); // default precision of printf is 6 5371 targetValue = values[spec->mainArgNum].value.longDoubleValue; // losing precision 5404 if (hasPrecision && spec->type == CFFormatLongType) { // if we have precision and %d or %u, we pad 0 5452 if (hasPrecision && spec->type == CFFormatLongType) { // if we have precision and %d or %u, we pad 0 according to precision first 5461 prec++; // for %e, precision+1 is the number of sig fig 5477 double doubleValue = values[spec->mainArgNum].value.longDoubleValue; // losing precision 5966 SInt32 width = 0, precision = 0; local [all...] |
/macosx-10.9.5/CPANInternal-140/DBIx-Class-Schema-Loader-0.05003/lib/DBIx/Class/Schema/Loader/DBI/ |
H A D | Pg.pm | 129 # set the correct precision for datetime and varbit types. 141 /^(?:bigint|int8|bigserial|serial8|bit|boolean|bool|box|bytea|cidr|circle|date|double precision|float8|inet|integer|int|int4|line|lseg|macaddr|money|path|point|polygon|real|float4|smallint|int2|serial|serial4|text)\z/i) { 144 # for datetime types, check if it has a precision or not 146 my ($precision) = $self->schema->storage->dbh 154 if ((not $precision) || $precision !~ /^\d/) { 164 if ($precision == $max_precision) { 168 $result->{$col}{size} = $precision; 172 elsif ((not $precision) || $precision !~ / [all...] |
H A D | Sybase.pm | 271 # XXX we need to handle "binary precision" for FLOAT(X) 274 if ($data_type =~ /^(?:text|unitext|image|bigint|int|integer|smallint|tinyint|real|double|double precision|float|date|time|datetime|smalldatetime|money|smallmoney|timestamp|bit)\z/i) {
|
/macosx-10.9.5/CPANInternal-140/DBIx-Class-Schema-Loader-0.07033/lib/DBIx/Class/Schema/Loader/DBI/ |
H A D | InterBase.pm | 205 my ($precision, $scale, $type_num, $sub_type_num, $char_set_id, $char_length, $type_name, $sub_type_name) = $sth->fetchrow_array; 213 if ($precision && $type_name =~ /^(?:LONG|INT64)\z/ && $sub_type_name eq 'BLR') { 216 elsif ($precision && $type_name =~ /^(?:LONG|SHORT|INT64)\z/ && $sub_type_name eq 'TEXT') { 219 elsif ((not $precision) && $type_name eq 'INT64' && $sub_type_name eq 'BINARY') { 241 if ($data_type =~ /^(?:decimal|numeric)\z/ && defined $precision && defined $scale) { 242 if ($precision == 9 && $scale == 0) { 246 $info->{size} = [$precision, $scale];
|
H A D | Oracle.pm | 252 elsif (my ($precision) = $info->{data_type} =~ /^timestamp\((\d+)\)(?: with (?:local )?time zone)?\z/i) { 255 if ($precision == 6) { 259 $info->{size} = $precision; 267 elsif (($precision) = $info->{data_type} =~ /^interval year\((\d+)\) to month\z/i) { 270 if ($precision == 2) { 274 $info->{size} = $precision; 288 my $precision = $info->{size}[0]; 290 if ($precision == 2) { 294 $info->{size} = $precision; 310 $info->{data_type} = 'double precision'; [all...] |
H A D | Pg.pm | 192 # set the correct precision for datetime and varbit types. 205 /^(?:bigint|int8|bigserial|serial8|bool(?:ean)?|box|bytea|cidr|circle|date|double precision|float8|inet|integer|int|int4|line|lseg|macaddr|money|path|point|polygon|real|float4|smallint|int2|serial|serial4|text)\z/i) { 208 # for datetime types, check if it has a precision or not 217 my ($precision) = $self->schema->storage->dbh 225 if ((not $precision) || $precision !~ /^\d/) { 235 if ($precision == $max_precision) { 239 $info->{size} = $precision; 243 elsif ((not $precision) || $precision !~ / [all...] |
H A D | Sybase.pm | 439 = ($info->{$col}{len} <= 4 ? 'real' : 'double precision'); 446 if ($data_type =~ /^(?:text|unitext|image|bigint|integer|smallint|tinyint|real|double|double precision|float|date|time|datetime|smalldatetime|money|smallmoney|timestamp|bit)\z/i) {
|
H A D | mysql.pm | 225 $info->{data_type} = 'double precision'; 232 my ($precision, $scale, $column_type, $default) = eval { $self->dbh->selectrow_array(<<'EOF', {}, $table->name, lc($col)) }; 242 $info->{size} = $precision if defined $precision; 244 elsif ($data_type =~ /^(?:float|double precision|decimal)\z/i) { 245 if (defined $precision && defined $scale) { 246 if ($precision == 10 && $scale == 0) { 250 $info->{size} = [$precision,$scale];
|
/macosx-10.9.5/CPANInternal-140/DBIx-Class-Schema-Loader/lib/DBIx/Class/Schema/Loader/DBI/ |
H A D | Pg.pm | 129 # set the correct precision for datetime and varbit types. 141 /^(?:bigint|int8|bigserial|serial8|bit|boolean|bool|box|bytea|cidr|circle|date|double precision|float8|inet|integer|int|int4|line|lseg|macaddr|money|path|point|polygon|real|float4|smallint|int2|serial|serial4|text)\z/i) { 144 # for datetime types, check if it has a precision or not 146 my ($precision) = $self->schema->storage->dbh 154 if ((not $precision) || $precision !~ /^\d/) { 164 if ($precision == $max_precision) { 168 $result->{$col}{size} = $precision; 172 elsif ((not $precision) || $precision !~ / [all...] |
H A D | Sybase.pm | 271 # XXX we need to handle "binary precision" for FLOAT(X) 274 if ($data_type =~ /^(?:text|unitext|image|bigint|int|integer|smallint|tinyint|real|double|double precision|float|date|time|datetime|smalldatetime|money|smallmoney|timestamp|bit)\z/i) {
|
/macosx-10.9.5/CPANInternal-140/DBIx-Class/lib/DBIx/Class/Storage/ |
H A D | DBI.pm | 2186 numeric | int(?:eger)? | (?:tiny|small|medium|big)int | dec(?:imal)? | real | float | double (?: \s+ precision)? | (?:big)?serial
|
/macosx-10.9.5/CPANInternal-140/DBIx-Class/lib/DBIx/Class/Storage/DBI/ODBC/ |
H A D | ACCESS.pm | 91 =item Invalid precision value
|
/macosx-10.9.5/CPANInternal-140/DBIx-Class/lib/DBIx/Class/Storage/DBI/Oracle/ |
H A D | Generic.pm | 200 Maximum allowable precision is used, unless the environment variables have 209 To get more than second precision with L<DBIx::Class::InflateColumn::DateTime>
|
/macosx-10.9.5/CPANInternal-140/DBIx-Class/lib/DBIx/Class/Storage/DBI/ |
H A D | SQLAnywhere.pm | 104 second precision. The full precision is used.
|
/macosx-10.9.5/CPANInternal-140/DBIx-Class/lib/DBIx/Class/Storage/DBI/Sybase/ |
H A D | ASE.pm | 301 real => 'double precision', 305 float => 'double precision', 858 C<SMALLDATETIME> columns only have minute precision.
|
/macosx-10.9.5/CPANInternal-140/DateTime/lib/ |
H A D | DateTime.pm | 1207 my $precision = shift; 1210 return $ret unless $precision; # default = 9 digits 1216 return substr( $ret, 0, $precision );
|
/macosx-10.9.5/CPANInternal-140/JSON-2.53/lib/ |
H A D | JSON.pm | 1751 precision. Otherwise it will preserve the number as a string value (in 1757 precision (in which case you might lose perfect roundtripping ability, but 1760 Note that precision is not accuracy - binary floating point values cannot 1762 floating point, C<JSON> only guarantees precision up to but not including 1894 Note that numerical precision has the same meaning as under Perl (so
|
/macosx-10.9.5/CPANInternal-140/JSON-2.53/lib/JSON/ |
H A D | backportPP.pm | 2557 precision. Otherwise it will preserve the number as a string value (in 2563 precision (in which case you might lose perfect roundtripping ability, but 2566 Note that precision is not accuracy - binary floating point values cannot 2568 floating point, C<JSON> only guarantees precision up to but not including 2687 Note that numerical precision has the same meaning as under Perl (so
|
/macosx-10.9.5/CPANInternal-140/JSON-XS-2.33/ |
H A D | XS.pm | 990 precision. Otherwise it will preserve the number as a string value (in 996 precision (in which case you might lose perfect roundtripping ability, but 999 Note that precision is not accuracy - binary floating point values cannot 1001 floating point, JSON::XS only guarantees precision up to but not including 1100 Note that numerical precision has the same meaning as under Perl (so
|
/macosx-10.9.5/CPANInternal-140/JSON-XS/ |
H A D | XS.pm | 985 precision. Otherwise it will preserve the number as a string value (in 991 precision (in which case you might lose perfect roundtripping ability, but
|
/macosx-10.9.5/CPANInternal-140/JSON/lib/ |
H A D | JSON.pm | 1589 precision. Otherwise it will preserve the number as a string value (in 1595 precision (in which case you might lose perfect roundtripping ability, but
|
/macosx-10.9.5/CPANInternal-140/Net-DNS/lib/Net/DNS/RR/ |
H A D | LOC.pm | 101 (\s+ ([\d.]+) m?)? # horiz precision 102 (\s+ ([\d.]+) m?)? # vert precision 304 Returns the horizontal precision of the data, in centimeters. 310 Returns the vertical precision of the data, in centimeters.
|
/macosx-10.9.5/CPANInternal-140/Perl4-CoreLibs-0.003/lib/Perl4/ |
H A D | CoreLibs.pm | 45 Arbitrary precision decimal floating point arithmetic. 50 Arbitrary precision integer arithmetic. 55 Arbitrary precision rational arithmetic.
|
/macosx-10.9.5/Heimdal-323.92.1/lib/hcrypto/libtommath/ |
H A D | bn.tex | 248 source code is also accessible for computer science students attempting to learn ``BigNum'' or multiple precision 334 The basic ``multiple precision integer'' type is known as the ``mp\_int'' within LibTomMath. This data type is used to 1233 considerably less work. For example, a 10000-digit multiplication would take roughly 724,000 single precision 1234 multiplications with Toom-Cook or 100,000,000 single precision multiplications with the standard Comba (a factor
|
H A D | tommath.tex | 129 great deal of work in which multiple precision mathematics was needed. Understanding the possibilities for speeding up 130 multiple precision calculations is often very important since we deal with outdated machine architecture where modular 170 raise or lower the precision of the numbers we are dealing with. For example, in decimal we almost immediate can 171 reason that $7$ times $6$ is $42$. However, $42$ has two digits of precision as opposed to one digit we started with. 172 Further multiplications of say $3$ result in a larger precision result $126$. In these few examples we have multiple 173 precisions for the numbers we are working with. Despite the various levels of precision a single subset\footnote{With the occasional optimization.} 176 By way of comparison a fixed or single precision operation would lose precision on various operations. For example, in 177 the decimal system with fixed precision $6 \cdot 7 = 2$. 179 Essentially at the heart of computer based multiple precision arithmeti [all...] |