Hi,
Is the limitation mentioned under below link for accessing serial ports is
still valid.
http://www.mono-project.com/archived/howtosystemioports/
Thanks
Techi
___
Mono-devel-list mailing list
Mono-devel-list@lists.ximian.com
I have found link which is useful on below topics.
http://www.mono-project.com/docs/debug+profile/debug/
Please let me know if any other info available.
Thanks
Techi
-- Forwarded message --
From: techi eth techi...@gmail.com
Date: Mon, Dec 1, 2014 at 4:24 PM
Subject: Mono
Mono today also only supports the format specifiers used in decimalFmt:
https://github.com/mono/mono/blob/f8a517624de3fdfc070d2f0660fce1b62d41bc4c/mcs/class/System.Numerics/System.Numerics/BigInteger.cs#L1458-L1471
So using this #if for Mono is the correct way to go.
(reposted, seems like the
Hello Alex,
I am not sure I am understanding this.
This looks like we are choosing to not bring features that we are missing?
Why would we want to do that?
Miguel
On Wed, Dec 3, 2014 at 10:33 AM, Alexander Köplinger
alex.koeplin...@outlook.com wrote:
Mono today also only supports the
Hey,
we need to ensure we only continue for the format specifiers used in
decimalFmt. Any other format specifier (i.e. culture-specific ones) would
result in a call into unmanaged code later on
To make this 100% clear: .NET implements locale aware number formatting in the
VM, e.g. for format specifiers like 'e' (exponential) or 'f' (fixed-point) it
calls into the VM for formatting.
We don't have this in Mono atm., so the only way is to restrict it to the
invariant format specifiers
Hello. Have you guys heard of the proxygen (
https://github.com/facebook/proxygen/ ) - an HTTP stack library recently
released by Facebook? It supports HTTP, SPDY, websockets and will support
HTTP/2.0 later.
I was playing around with it and created some initial bindings that allow
to write code
Got it.
Miguel
On Wed, Dec 3, 2014 at 11:13 AM, Alexander Köplinger
alex.koeplin...@outlook.com wrote:
To make this 100% clear: .NET implements locale aware number formatting in
the VM, e.g. for format specifiers like 'e' (exponential) or 'f'
(fixed-point) it calls into the VM for
I would say in the interop calls, you'll need to drop COM and implement
custom marshalling to avoid messy copying/conversion of structs and strings
(CLR uses UTF-16 strings internally and I didn't dig into proxygen or your
COM wrapper to see what it uses, but probably it is utf-8 or some
I figured out that the most costly thing is the creation of 2 RCW (Runtime
Callable Writer) per request. As long as I don't spam COM object instances
it should be fine. Althrough it wouldn't be really COM-way for
request/response objects.
2014-12-03 23:29 GMT+03:00 Rafael Teixeira
I've removed that RCW creating (i. e. I'm receiving IntPtr from native
code) and now its 109K rps.
___
Mono-devel-list mailing list
Mono-devel-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list
On Dec 2, 2014, at 9:09 AM, Burhan Eyuboglu burhaneyubo...@gmail.com wrote:
When I add libcyusb.so, I got this error: libcyusb.so is not a valid ELF
executable
Where do you get this error from? What's the overall context?
I checked the library, libcyusb.so is not ELF, it is a linker, however
12 matches
Mail list logo
