Displaying 3 results from an estimated 3 matches for "errmessag".
Did you mean:
errmessage
2002 Jan 18
1
TeX error generated by R CMD CHECK
...ard LaTeX document class
....
(/usr/local/teTeX/texmf/tex/latex/graphics/dvipsnam.def))
(/usr/local/teTeX/texmf/tex/latex/hyperref/hyperref.sty
(/usr/local/teTeX/texmf/tex/latex/graphics/keyval.sty)
(/homef/jonm/R-1.4.0/share/texmf/hyperref.cfg
! key-val: linktocpage undefined.
\KV at err #1->\errmessage {key-val: #1}
l.12 }
? h <--TYPED BY ME
This error message was generated by an \errmessage
command, so I can't give any explicit help.
Pretend that you're Hercule Poirot: Examine all clues,
and deduce the truth by order and method.
?
)...
2009 Feb 04
2
[nut-commits] svn commit r1765 - in trunk: . drivers man
...crodowell.c/h into drivers/. add man/microdowell.8. Adjusted
> drivers/Makefile.am and man/makefile.am. Adjusted the code for 2.4.0 in the
> microdowell.c.
Besides the things already mentioned by others and the obvious
formatting issue, just a couple of nits to pick:
> 93 static char *ErrMessages[] = {
[...]
> 187 }
Consider returning the error message through something like
> 124 case ERR_NO_ERROR:
> 125 return "OK";
instead of doing this indirectly through an index in an array of error
strings. This makes sure these don't get out of sync.
> 547...
2007 Jul 05
2
[LLVMdev] PATCH (rest of code changes) "bytecode" --> "bitcode"
Here is the bulk of the sanitizing.
My residual doubts center around the question
whether we still do/want to support (un)compressed *byte*code
in 2.0/2.1.
I need a definitive word on this to proceed.
My understanding is that bytecode is already gone, but there are
still some functions/enums that really deal with *byte*code
(instead of *bit*code).
I did not touch those areas, so the attached