0 down vote favorite
A pipe in mac/mono is just like any file. You set up the pipe, then use
streams to talk to the pipe. One app writes to the pipe using streams, the
other app reads from the pipe using streams. Again, as we discussed, you
need to code up 2 test objectivec apps talking
I'm checking that code, at
https://github.com/mono/mono/blob/master/mono/metadata/security-core-clr.c.
If to ensure that the specified method can be used with reflection since
Transparent code cannot call Critical methods is fine with me, why does
CoreCLR also prevents transparent code to call
Hello,
some time ago I submitted a pull request which adds openat() and some
other methods to Mono.Posix:
https://github.com/mono/mono/pull/221
A related pull request for mono-tools (which is needed for the mono pull
request):
https://github.com/mono/mono-tools/pull/22
Is there anything else I
I believe you're asking the wrong question: why should CoreCLR allow
transparent code to call internal methods? It doesn't matter if
they're transparent or not, there's a reason a method is internal and
you can make the object confused if internal methods are called
directly.
Rolf
On Sun, Mar
On 24.03.2013 19:08, nelson wrote:
I'm checking that code, at
https://github.com/mono/mono/blob/master/mono/metadata/security-core-clr.c.
If to ensure that the specified method can be used with reflection since
Transparent code cannot call Critical methods is fine with me, why does
CoreCLR also
On Mar 26, 2013, at 9:13 AM, Steffen Kieß s-ki...@web.de wrote:
some time ago I submitted a pull request which adds openat() and some other
methods to Mono.Posix: https://github.com/mono/mono/pull/221
A related pull request for mono-tools (which is needed for the mono pull
request):
Am Dienstag, den 26.03.2013, 15:12 -0400 schrieb Jonathan Pryor:
On Mar 26, 2013, at 9:13 AM, Steffen Kieß s-ki...@web.de wrote:
some time ago I submitted a pull request which adds openat() and some other
methods to Mono.Posix: https://github.com/mono/mono/pull/221
A related pull
