Displaying 4 results from an estimated 4 matches for "misform".
Did you mean:
misforn
2019 Nov 28
2
Some commits not getting sent to the mailing lists.
For example:
https://github.com/llvm/llvm-project/commit/549ff601f053303356abe7d8fca8fbcf5e3502e7
and
https://github.com/llvm/llvm-project/commit/4eacc32672e60113b835c4356d1c398dc1e30279
Don't seem to have made it to cfe-commits.
This makes it harder to search for stuff, reply to commits, and most
importantly it allows these patches to land "under the radar",
potentially without
2007 Aug 09
1
[LLVMdev] Tail call optimization thoughts
Implementing tail call opt could look like the following:
0.)a fast calling convention (maybe use the current
CallingConv::Fast, or create a CallingConv::TailCall)
1.) lowering of formal arguments
like for example x86_LowerCCCArguments in stdcall mode
we need to make sure that later mentioned CALL_CLOBBERED_REG is
not used (remove it from available
registers in callingconvention for
2006 May 28
13
JSON not auto-evaluated
Hi,
please consider this stripped down example:
new Ajax.Request(''foo.php'', {
onSuccess: function(t, json) {
alert(json.myParam);
}
});
According to http://www.sergiopereira.com/articles/prototype.js.html, the
second param is supposed to be the evaluated json object IF the X-JSON header
is send in the response. I send the header in my script. However, the json
var
2011 Nov 02
0
Calling str() on mlogit object gives warnings
...the first element will be used
2: In if (le > 0) P0("[1:", paste(le), "]") else "(0)" :
the condition has length > 1 and only the first element will be used
I am surprised that I'm getting warnings. Am I doing something wrong
here, or is the mlogit object misformed in some way, or is there a
problem with str()?
I don't think the str() is specific to mlogit, since if I do
utils:::str.default(ml.train)
I get the same warnings.
Thanks.
Jen
sessionInfo()
R version 2.14.0 (2011-10-31)
Platform: x86_64-unknown-linux-gnu (64-bit)
locale:
[1] LC_CTYPE=e...