Displaying 3 results from an estimated 3 matches for "misteak".
Did you mean:
mistea
2010 May 25
2
Little t38 bug?
...p->t38.their_parms.rate = AST_T38_RATE_4800;
break;
case 2400:
p->t38.their_parms.rate = AST_T38_RATE_2400;
break;
}
found = TRUE;
else if {...
If I'm not misteaking the second "if else" condition will never be true if the other device sends "T38FaxMaxBuffer" (wich they all usually do).
Shouldn't it be
if((sscanf(a, "T38FaxMaxBuffer:%30u", &x) == 1) && ((sscanf(a, "T38MaxBitRate:%30u", &x) == 0) |...
2009 Jan 27
0
[LLVMdev] PPC calling convention -- how to provide an environment pointer?
...---
For PPC32, it seems like you may use GPR0 and GPR2 with impunity,
GPR11 if your caller is not a nested function, and GPR12 if your
callee is called directly (address never taken). The PPC64 version of
the Register Preservation table appears to be identical to the PPC32
version, so any misteaks or misunderstandings in this email should be
wrong there too. :-)
> Thanks!
You're very welcome,
stuart
2008 Dec 07
2
Checking your package's help files
It seems that many package authors do not proofread the help installed
with their packages. The Rd converter is not a parser, and it will
silently produce incorrect results on incorrect input (and some correct
input).
Here are a few hints about some common errors:
1) When you run R CMD check you get a PDF manual at
<pkg>.Rcheck/<pkg>-manual.pdf. Read through it looking for