search for: _type_

...-c( as.numeric(i), as.numeric(j), as.numeric(myMedian) ); k <- k+1; } } ---------------------- Begin SAS code ------------------------------------ proc summary data=SASUser.PaydexNormfull nway; class PaydexNormingCategory SIC ; weight Counts; var Paydex; output out=outstat (drop=_type_ _freq_) median= / autoname; run; ---------------------- End SAS code ------------------------------------ Thanks for your guidance! Vivek Satsangi GE Capital Americas GE imagination at work [[alternative HTML version deleted]]

...X3; RUN; I am able to easily obtain the linear discriminant functions for the strata which allow computation of the three discriminant scores for a given observation. This information is contained in WORK.FOOTSTAT and may be extracted by subsetting: DATA LDFUNC; SET FOOSTAT(WHERE = (_TYPE_ = LINEAR)); RUN; To actually implement the linear discriminant functions takes a bit more formatting, but there it is. My question: Where is this information stored in R? I completely understand that predict( ) or predict.lda( ) are the preferable ways to obtain a classification prediction f...

...fined behavior. > > And if that is a problem, you use unsigned integers instead of signed > integers. > > So it seems that we should be able to do something very similar here. For this case the important pice of information to convey one or the other meaning in source code is the _type_ of involved entities, not annotations on the operations. signed type -> undefined overflow, unsigned type -> modulo arithmetic; easy, and it nicely carries automatically through operation chains (and pointers) without any annotations. I feel much of the complexity in the memory order spe...

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, since Icecast <=1.3.12 has been affected by a cross-site scripting vulnerability in the status display (s. <http://securitytracker.com/alerts/2004/Aug/1011046.html> and <http://www.debian.org/security/2004/dsa-541>) it appears to be unclear so far if Icecast 2.x is vulnerable too. Can anyone of you maybe confirm it is affected/not

...3 NO Can't rename mailbox to another storage type. I was a little surprised that it didn't work at first, since they're both using the same (default) mail_location, but I see why it doesn't work after looking at the code. Is there any chance cross-namespace (and even cross-storage _type_) wouldn't eventually be supported? (I guess that the big problem is making cross-type renames appear atomic to clients.) Is there a better way to do what I'm trying to do? -- Ben Winslow <rain at bluecherry.net>

Hello, I am using the polar.plot function from plotrix. Is there a way to change the width of the grid lines? grid.lwd doesn't work.... Thanks Martin -- View this message in context: http://r.789695.n4.nabble.com/Grid-Width-in-polar-plot-tp4647547.html Sent from the R help mailing list archive at Nabble.com.

>Paul E Wrote [snip] >Windows 2000 (although it's the same for all of them) doesn't read in >any mime-type to correctly identify a file, it just uses the extension. [snip] What if, at least for Windows, someone wrote a simple application which when associated with .ogg files and an .ogg file was opened simply read enough of the ogg stream to identify the type of content and then

On Thu, Feb 25, 2016 at 04:46:50PM -0800, Hans Boehm wrote: > If carries_dependency affects semantics, then it should not be an attribute. I am not picky about the form of the marking. > The original design, or at least my understanding of it, was that it not > have semantics; it was only a suggestion to the compiler that it should > preserve dependencies instead of inserting a fence

I have some questions regarding how globals are represented in DS graph. Specifically, I wrote the following simple program: List *g; void alloc_func(){ g = ( List* ) malloc( sizeof( List ) ); } void free_func(){ free( g ); } int main(){ alloc_func(); free_func(); } I noticed that the DSnode for g in alloc_func is different from that of free_func and NEITHER of them had GlobalNode