postgresql,postgresql-9.3,infinity,range-types

The confusion stems from two different meanings of "infinity" here. timestamp types accept special values for infinity and -infinity. Range types have a general concept for ranges without lower / upper bound. The functions to test for it are called lower_inf() and upper_inf(), but they are really testing for "no...

c#,visual-studio-2012,infinity

You could use Nullable<int> (int? for short) and just use null to mean "infinity". Technically, this would likely be fine, but it's not an ideal semantic representation of what you're trying to do. Also note that if you use mathematical operations (addition, multiplication, etc) the semantics for null values...

java,android,formatting,infinity

Never mind, found it myself: DecimalFormatSymbols.getInstance().getInfinity() Note that it may not work with some custom fonts....

ifelse constructs each of its possible values, and it bugs out on as.POSIXct("infinity"). Instead, try converttime <- function(x,o="1970-01-01",posinf="infinity",neginf="-infinity"){ xc <- x xc[x%in%c(posinf,neginf)] <- NA d <- as.POSIXct(xc, origin=o) d[x==posinf] <- as.POSIXct(Inf, origin=o) d[x==neginf] <- as.POSIXct(-Inf, origin=o) d } d <- converttime(df$dates) d[3] > d[4] # TRUE ...

haskell,floating-point,infinity,floor

The first question is perhaps not so important, so I'll try to answer the second question first. Once you have a number, if you know that it came from floor x, you can't know whether x was the valid representation of 2^1024 or if it was infinity. You can probably...

java,exception,exception-handling,infinity

Not sure if this is what you are looking for, but you can test for infinity/overflow with an if statement as well: if( mfloat == Float.POSITIVE_INFINITY ){ // handle infinite case, throw exception, etc. } So in your situation, you would do something like this: public static double Power(double base,...

Use one less index value in array_name. Integer myInf = Integer.MAX_VALUE; array_name[length_of_array - 1]=myInf; ...

android,android-fragments,textfield,calculator,infinity

Use this: Integer.parseInt(etBodyWeight.getText().toString()); instead of: Integer.parseInt(etBodyWeight.toString()); Also see the answer here for getting value from EditText. Also change to etWaist.getText().toString()....

The "pythonic" way is to go with what's readable and maintainable. That said, x == float("inf") and x == float("-inf") are slightly more readable to me, and I'd prefer them. math.isinf(x) and x > 0 is faster, but only on the order of about 40 nanoseconds per call. So unless...

Split the summation range in two. For example, to sum 1/(k+1/2)^2 for k ranging from -inf to inf: >> syms k >> S = symsum(1/(k+1/2)^2,1,inf) + symsum(1/(-k+1/2)^2,0,inf) S = pi^2 ...

One way of expressing an average is: totalValue += nextValue * nextWeight; totalWeight += nextWeight; average = totalValue / totalWeight; This is prone to overflow in totalValue, as you have seen. Instead you can also do: totalWeight += nextWeight; average += ((nextValue * nextWeight) - average) / totalWeight; In your...

All the expressions 1-7 in your question evaluate to true when compiled by a compiler that implements IEEE 754 rules. None of them depend on the rounding mode. For many, this is simply because < and == are exact operations. In addition, -inf - inf is always -inf (that is,...

Change for ( i = 1; i < userNumber; i++ ) { to for ( i = userNumber - 1; i > 1; --i ) { Note that your code changes userNumber in the loop body, so that the loop will only terminate if userNumber overflows....

They don't convert to NA, that's just how they're printed. R> d <- as.Date(-Inf, origin="1970-01-01") R> is.na(d) # [1] FALSE R> is.infinite(d) # [1] TRUE If you want them to print differently, you can override the print.Date method and add special cases for +/- infinity....

No, it creates two lists: one with a single item, and one with 100 items that all point to the first list. It then makes the single item in the first list point to the second list. So it does not make an infinitely deep list; it just creates a...

I'm assuming you're asking about why there's an Infinity global property, not why there's a concept of having infinities in the first place, which is another matter. It allows easy comparison with the Infinity value itself, where you get it from some arithmetic: function inv(x) { return x * 100000000000;...

Yes, Infinity and -Infinity are special values of the Number type. From the ES5 spec: There are two other special values, called positive Infinity and negative Infinity. For brevity, these values are also referred to for expository purposes by the symbols +∞ and −∞, respectively. (Note that these two infinite...

ruby,postgresql,csv,double,infinity

First of all, Postgres can probably handle loading CSVs without Ruby's help. As for your question... CSV does not define data types, so whenever you read CSV data into something that expects data types (like Excel or Ruby) the program has to guess. When Excel sees 20150519E000010 it is guessing...

You need to use (as David points out in comments): range.default(f, finite=TRUE) # [1] 1 3 or range(f, finite=1) # [1] 1 3 The function is erroneously requiring finite to be numeric, but then properly uses it in removing infinite values. Notice: f2 <- data.frame(x=1:2, y=3:4) range(f2, finite=TRUE) # Error...

There's a macro for this INFINITY, float x = INFINITY; You can find this in usr/include/math.h # define HUGE_VALF __builtin_huge_valf() ... #define INFINITY HUGE_VALF edit Some more interesting read here http://www.gnu.org/software/libc/manual/html_node/Infinity-and-NaN.html...

Haskell's Double (the default you get when using /) follows the IEEE 754 standard for floating point numbers, which defines how Infinity behaves. This is why 1/0 is Infinity. By this standard (and, to be fair, by logic), Infinity + 1 == Infinity, and the Enum instance for Double just...