Displaying 7 results from an estimated 7 matches for "unfavourably".
2007 Jan 10
1
Priority + 101 exit
Many built-in applications jump to current priority + 101 upon unfavourable
output. Does this apply to macros and AGI's also? Precisely, when an AGI
returns non-zero, will Asterisk automatically take the call to +101? And
when a macro hits an invalid extension, will Asterisk automatically take the
call to +101? (So far the "i" extension could not be reached from within a
2024 Mar 15
2
RSS Feed of NEWS needs a hand
Hi!
Thanks for this service! It is very helpful to know what is being developed.
I distribute the content to other venues and I noticed some times that the
updates are duplicated.
For example, the sentence "?is.R()? is deprecated as no other S dialect is
known to be in use (and this could only identify historical dialects, not
future ones)." is duplicated in different days:
Day 1:
2017 Aug 15
3
[XRay] Alternatives to relocations in .text section
...ly, (in X86) we just write out a raw ".quad <label>" reference after lowering the function, where <label> is defined in the "xray_fn_idx" section. Unfortunately this causes the linker (gold?) to emit a relocation in the .text section (TEXTREL in ELF) which interferes unfavourably with GNU IFUNC relocations.
Questions
=========
Is there an alternative to this approach available to us from the LLVM back-end? I see that there's ways to define associative COMDAT sections, but that's COFF-specific and only works with COMDAT. We instrument XRay functions that aren't...
2024 Mar 15
1
RSS Feed of NEWS needs a hand
Years ago Duncan set up a nightly job to feed RSS based off changes to NEWS,
borrowing some setup parts from CRANberries as for example the RSS 'compiler'.
That job is currently showing the new \I{...} curly protection in an
unfavourable light. Copying from the RSS reader I had pointed at this since
the start [1], for today I see (indented by four spaces)
CHANGES IN R-devel
2008 Oct 16
1
One-sample test for p
Hi, i am doing a statistics course and am having trouble with an exercise
where i need to determine whether my success rate at something is higher
than 80%.
I was successful in 29 out of 60 trials, so these were the commands i
entered into R:
>n=60
>p.hat=29/n
>p.0=0.8
>se.0=sqrt(p.0*(1-p.0)/n)
>z=(p.hat-p.0)/se.0
>print(z)
Which returned:
[1] -6.132224
>1-pnorm(z)
Which
2007 May 09
3
One for the wish list - var.default etc
I was working on a permutation-like variant of the bootstrap for smaller samples, and wanted to be able to get summary stats of my estimator conveniently. mean() is OK as its a generic, so a mean.oddboot function gets used automatically. But var, sd and others are not originally written as generic; they have to be explicitly masked by a package or new declaration.
It would have been nice if
2023 Jul 07
1
printCoefmat() and zap.ind
>>>>> Shu Fai Cheung
>>>>> on Thu, 6 Jul 2023 17:14:27 +0800 writes:
> Hi All,
> I would like to ask two questions about printCoefmat().
Good... this function, originally named print.coefmat(),
is 25 years old (in R) now:
--------------------------------------------------------------------
r1902 | maechler | 1998-08-14 19:19:05 +0200 (Fri,