On 07/21/05 Allan Hsu wrote:
> I think I may have misread the part of the wiki that talks about
> embedding mono (http://mono-project.com/Embedding_Mono):
Note that this page is specifically about embedding: icalls are
available to embedders, but that's it, they aren't a generally
available solu
Hi,
Internal calls are only a bit faster than p/invoke. The difference
only becomes
greater when complex types are passed to native code like arrays/structures in
which case the runtime will have marshall them. You are of course free to
add new inter
On Jul 21, 2005, at 10:04 AM, Paolo Molaro wrote:
As explained a few days ago in another mail: internal calls have
nothing to do with speed. They only belong inside the general
purpouse mono if they are generally useful or in your specialized
embedding app. So they are not appropriate as a subst
On 07/18/05 Allan Hsu wrote:
> After last week's AES benchmarking, we've decided to write a
> managed->native wrapper around the openssl libcrypto library for the
> sake of performance. From my experience with embedded mono, it seems
> straightforward enough to write a RijndaelNative clas
Hello,
> embedding mono. Is it possible to register internal calls at runtime
> when running mono like a normal, sane person? Will this be any faster
> than using p/Invoke?
You can not use internal calls and have them work in non-embedded
scenarios.
P/Invoke will also be a lot simpler to deb
After last week's AES benchmarking, we've decided to write a
managed->native wrapper around the openssl libcrypto library for the
sake of performance. From my experience with embedded mono, it seems
straightforward enough to write a RijndaelNative class that contains
method declarations