search for: wheere

Displaying 5 results from an estimated 5 matches for "wheere".

Did you mean: where
2019 May 03
3
ArrayRef vs SmallVectorImpl
It is suggested in the documentation that if you would have declared a function parameter as SmallVector<Foo,N>&, it is better to instead declare it as SmallVectorImpl<Foo>&. This makes sense, but it seems to me that it is better still to declare it as ArrayRef<Foo>; a quick test suggests it compiles to the same (highly efficient) code, and adds a bit more flexibility in
2005 Jun 03
0
RE: GARCH (1 , 1), Hill estimator of alpha, Pareto estimator]
...; m1<- garch(dax) > Error: couldn't find function "garch" > m1<- garch(dax[1:1865]) > Error: couldn't find function "garch" > m1<- garch(dax[1:1865]) I am sorry, but I forgot to change the addres to r-help in the reply. Well, I am not sure, wheere do you want to get those data from, but if you are able to do that: > dax<- diff(log(DAX_CAC$DAX[1:1865])) Then it means, that you have managed to do that. The thing is, that garch function is in the tseries package and I haven't seen any call to it, so first try: library(tseries)...
2008 Dec 31
1
plot.stepfun xlim
i've noticed a strange problem when plotting a stepfun. according to the documentation, the xlim parameter should bound the range of the function being plotted, and is returned as the extreme two values (i.e. first and last) in the vector t from the plot.stepfun call. instead, it plots beyond the desired range (although the limits are preserved for the viewing space). to reproduce: foo
2004 Oct 03
2
Problem with XP after upgrade from 2.2 -> 3.0
Hello All, About 2 weeks ago I upgraded from debian woody to sarge. This included an upgrade from Samba2.2 -> Samba3.0. However since the upgrade I have problems using my Samba server from my XP (home) Laptop. The symptoms are basically "explorer" freezeing on most network browseing type actions. Or if I open a file (eg a movie). I'm pretty confident that I don't have a
2008 Feb 04
3
[PATH] ioemu: use SIGHUP instead of SIGKILL
The stub domain device model needs to trap the termination signal so as to actually destroy the stub domain. SIGKILL can''t be trapped, SIGTERM is caught by SDL and so may be unnoticed. SIGHUP can be trapped and is not caught by SDL (and by default causes a process termination without core). Signed-off-by: Samuel Thibault <samuel.thibault@eu.citrix.com> diff -r 2407a61c0d30