search for: maxint

...rargs.h... no checking for size_t... yes checking for working const... (cached) yes checking whether byte ordering is bigendian... (cached) no checking for u_int computing machine epsilon(s) gcc -o macheps ./src/meschach/dmacheps.c gcc -o macheps ./src/meschach/fmacheps.c computing M_MAX_INT gcc -o maxint maxint.c ./src/meschach/maxint.c: In function 'main': ./src/meschach/maxint.c:37: warning: incompatible implicit declaration of built-in function 'printf' checking char \\0 vs. float zeros checking for bcopy... yes checking for bzero... yes checking for function prototypes checking...

optim ignores misspelled control parameters, so that trying to set (e.g.) "maxint=1000" in the control argument silently does nothing. The patch below (watch out for line breaks! also posted at http://www.zoo.ufl.edu/bolker/optim_patch.R , and http://www.zoo.ufl.edu/bolker/optim_new.R) adds three lines to optim.R that issue a warning if any names of elements of "cont...

I'm running dovecot 1.2.16 from the ports collection on FreeBSD 8.1-STABLE, amd64. I've long been getting the following kind of messages in my logs, on random occasions when I access or move mail into mboxes: Aug 16 00:43:58 myhost dovecot: IMAP(mike): mbox /home/mike/mail/feedback: seq=88 uid=91 uid_broken=0 originally needed 0 bytes, now needs 18446744073709551615 bytes Whatever

R Version 1.4.0 Patched (2002-01-23) Solaris 5.8 I just noticed that max(NULL) gives a strange result: > max(NULL) [1] -2147483647 Warning message: no finite arguments to min/max; returning extreme. in: max(..., na.rm = na.rm) I discovered this when I did something like max(object$element) for an incorrect element name. The warning message was helpful, but I was still surprised to

...rargs.h... no checking for size_t... yes checking for working const... (cached) yes checking whether byte ordering is bigendian... (cached) no checking for u_int computing machine epsilon(s) gcc -o macheps ./src/meschach/dmacheps.c gcc -o macheps ./src/meschach/fmacheps.c computing M_MAX_INT gcc -o maxint maxint.c ./src/meschach/maxint.c: In function 'main': ./src/meschach/maxint.c:37: warning: incompatible implicit declaration of built-in function 'printf' checking char \\0 vs. float zeros checking for bcopy... yes checking for bzero... yes checking for function prototypes checking...

...the numbers returned are exactly as for the 'simpler ways', so nls is definitely in the wrong, but the self-start is almost identical to the one for the logarithmic fit, which works perfectly .... I can't see my mistake at all. Can anyone help?? Thanks, Toby Marthews traceson=FALSE;maxint=10000;minstepfactor=2^(-30);tolerance=1e-7 xtxt="DBH in mm";ytxt="Height in m" dbh=c(0.9,1.0,1.1,1.2,4.8,4.9,5.0,5.1,8.9,9.0,9.1,9.2,11.8,11.9,12.0,12.1,14.9,15.1,15.2,15.5) height=c(5.770089,5.154794,4.888847,6.356770,14.849109,14.973146,15.423816,14.865038,21.335985,20.477624,...

...x supports filtering by date. For example, all dates between START and END. Would it be possible to extend this behaviour to include the time? We have documents which expire. In order to filter out 'old' articles, we would like to check if the document date is between START=NOW and END=MAXINT. Best regards, Eric

All... I'm new to the HP-UX environment... I'm trying to build 1.9.18p3, using the HP compiler...I get the following errors: Compiling util.c cpp: "values.h", line 27: warning 2001: Redefinition of macro MAXINT. cpp: "includes.h", line 290: error 4036: Can't open include file 'sys/statfs.h'. cpp: "includes.h", line 292: error 4036: Can't open include file 'sys/filio.h'. cpp: "includes.h", line 293: error 4036: Can't open include file 'sys/socki...

...the error: ------- *** caught segfault *** address 0x1c404ec8, cause 'memory not mapped' Traceback: 1: .Call("rrfunc", as.double(dx), as.integer(nrows), as.integer(ncols), as.double(deltadt), as.character(binmaps), as.integer(ldd), as.double(downst),as.integer(outl), as.double(maxinte), as.double(nmn)) 2: rrfuncR(dx, nrows, ncols, delta.t,binmaps.pathed,ldd,downst, out.index,interc,n.man) 3: eval.with.vis(expr, envir, enclos) 4: eval.with.vis(ei, envir) 5: source("rrprogv1_2.R") 6: eval.with.vis(expr, envir, enclos) 7: eval.with.vis(ei, envir) 8: source("m...

...** Offending process: xend (pid=1045) ** *************************************************************** *************************************************************** Continuing... /usr/lib/python/xen/util/xsconstants.py:110: FutureWarning: hex/oct constants > sys.maxint will return positive values in Python 2.4 and up INVALID_SSIDREF = 0xFFFFFFFF etc/xen/scripts/xen-network-common.sh sh: =~: unknown operand sh: =~: unknown operand *ifdown: interface eth0 not configured* ip: SIOCSIFNAME: Device or resource busy suspend: event channel 9 BLKTAPCTRL[1091]: blktapctr...

...ional value for the "bigOutput" argument. ????? Comments? ????? Thanks, ????? Spencer Graves On 2020-01-19 10:28, Avraham Adler wrote: > Technically, lambda can always be numeric. It is the observations > which must be integral. > > Would hitting everything larger than maxint or maxlonglong with floor > or round fundamentally change the distribution? Well, yes, but enough > that it would matter over process risk? > > Avi > > On Sun, Jan 19, 2020 at 11:20 AM Benjamin Tyner <btyner at gmail.com > <mailto:btyner at gmail.com>> wrote: &gt...

So imagine rpois is changed, such that the storage mode of its return value is sometimes integer and sometimes numeric. Then imagine the case where lambda is itself a realization of a random variable. Do we really want the storage mode to inherit that randomness? On 1/19/20 10:47 AM, Avraham Adler wrote: > Maybe there should be code for 64 bit R to use long long or the like? > > On

...ents? > ????? Thanks, > ????? Spencer Graves > > > > On 2020-01-19 10:28, Avraham Adler wrote: >> Technically, lambda can always be numeric. It is the observations >> which must be integral. >> >> Would hitting everything larger than maxint or maxlonglong with >> floor or round fundamentally change the distribution? Well, yes, >> but enough that it would matter over process risk? >> >> Avi >> >> On Sun, Jan 19, 2020 at 11:20 AM Benjamin Tyner <btyner at gmail.com >> <...

Attached patch fixes a problem in marshaling large integers. It seems to only occur on systems with very large memory. However, on those systems, it''s a show-stopper. I see this as a temporary solution until we can sanitize the XML-RPC functions and get rid of all the S-Expression stuff. I''ll run xm-test tomorrow against it. Right now I''ve only done basic

Technically, lambda can always be numeric. It is the observations which must be integral. Would hitting everything larger than maxint or maxlonglong with floor or round fundamentally change the distribution? Well, yes, but enough that it would matter over process risk? Avi On Sun, Jan 19, 2020 at 11:20 AM Benjamin Tyner <btyner at gmail.com> wrote: > So imagine rpois is changed, such that the storage mode of its retur...

...s = 0; - tval_tv_usecs = usecs/1000; + tval.tv_sec = 0; + tval.tv_usec = usecs/1000; select(0,NULL,NULL,NULL,&tval); return 0; #endif /* HAVE_USLEEP */ In HPUX 10.20's compilation there are lots of warnings: cpp: "values.h", line 27: warning 2001: Redefinition of macro MAXINT but these are just warnings. Nothing to be worried about (I know someone will worry!) ------ Panu Outinen Tel. +358 3 313 411 Vertex Systems Oy Fax +358 3 313 41450 Vaajakatu 9 http://www.vertex.fi 33720 Tampere, FINLAND...

...sys/socket.h) AC_CHECK_HEADERS(sys/mount.h sys/vfs.h sys/fs/s5param.h sys/filsys.h termios.h termio.h) AC_CHECK_HEADERS(sys/termio.h sys/statfs.h sys/dustat.h sys/statvfs.h stdarg.h sys/sockio.h) +AC_CHECK_HEADERS(crypt.h) # # HPUX has a bug in that including shadow.h causes a re-definition of MAXINT. # This causes configure to fail to detect it. Check for shadow separately on HPUX. diff -ruN samba-2.0.6/source/include/includes.h samba-2.0.6.ia64/source/include/includes.h --- samba-2.0.6/source/include/includes.h Wed Nov 10 18:36:00 1999 +++ samba-2.0.6.ia64/source/include/includes.h Fri Apr 2...

...cer Graves >> >> >> >> On 2020-01-19 10:28, Avraham Adler wrote: >>> Technically, lambda can always be numeric. It is the >>> observations which must be integral. >>> >>> Would hitting everything larger than maxint or maxlonglong >>> with floor or round fundamentally change the distribution? >>> Well, yes, but enough that it would matter over process risk? >>> >>> Avi >>> >>> On Sun, Jan 19, 2020 at 11:20 AM Benjamin Tyner &...

I have observed the following differences in the use of min/max functions between R and Splus (4.5) R (0.64.1): min(c(NA,NA,NA),na.rm=T) returns the following Warning in min(..., na.rm = na.rm) : no finite arguments to min/max; returning extreme. [1] 2147483647 S-Plus 4.5( Win32 edition) min(c(NA,NA,NA),na.rm=T) returns [1] NA The S-PLUS behaviour seems to be the right one Thanks,

...argument. > > > Comments? > Thanks, > Spencer Graves > > > > On 2020-01-19 10:28, Avraham Adler wrote: > > Technically, lambda can always be numeric. It is the observations which > must be integral. > > Would hitting everything larger than maxint or maxlonglong with floor or > round fundamentally change the distribution? Well, yes, but enough that it > would matter over process risk? > > Avi > > On Sun, Jan 19, 2020 at 11:20 AM Benjamin Tyner <btyner at gmail.com> wrote: > >> So imagine rpois is changed, suc...