Looks ok.
Zoltan
2010/4/22 Kornél Pál kornel...@gmail.com
Hi,
native int, unsigned native int, unmanaged pointers, and function pointers
are all unmanaged; thus are not affected by a moving GC.
Please review the patch.
Thanks.
Kornél
Index: mono/mono/mini/method-to-ir.c
Hi Mauricio,
buhochile...@gmail.com wrote:
Well, you are in did really positive this morning, you just forget to
mention that the future of monotouch is at least uncertain at this
moment (may be is worse than that)...
Better to be honest with people than keep selling licence for something
Hi Cory
Hi Mauricio,
buhochile...@gmail.com wrote:
Well, you are in did really positive this morning, you just forget to
mention that the future of monotouch is at least uncertain at this
moment (may be is worse than that)...
Better to be honest with people than keep selling licence for
On 22.04.2010 16:34, buhochile...@gmail.com wrote:
Sure, let hope that all this end up successfully for MT, adobe, unity,
etc (I really hate ObjC)..but my point is that until we know a
definitely answer from Apple, the future of MT is at least uncertain,
and is good to take some responsibility
Hi Mauricio
[Mods: This is my last reply, then I'm letting this drop. Promise.]
buhochile...@gmail.com wrote:
In all seriousness, I think that it's not as bad as people are making it
Not as bad, are you serious?, you must read the NDA again, is very,
very clear and specific, there is no
Can someone please have a look at this?
On (2010-04-20 23:26), Robert Nagy wrote:
Hi
The attached diff makes SerialPort.GetPortNames() work on
all Unix systems other than Linux too, because ttyS* and
ttyUSB* is linux specific and on *BSD the serial ports are
tty[0-9]+.
(I've tested this
Hello,
The attached diff makes SerialPort.GetPortNames() work on
all Unix systems other than Linux too, because ttyS* and
ttyUSB* is linux specific and on *BSD the serial ports are
tty[0-9]+.
(I've tested this code on Linux and it should also support
ttySG0 (SGI running Linux (ia64)).
I am
Hi guys,
We may be able to get some hints from the sysfs filesystem, if running
on Linux. In /sys/class/tty, we have the available TTY ports -
whether or not they're physical serial ports is another issue - but
maybe it doesn't matter. If on Linux, and the /sys/class/tty
directory is available,
Hey
Basically on linux ttyS* and ttyUSB* is used for serial device names, but this
is not the case for *BSD, Solaris and probably OS X.
On these systems tty[0-9]+ or ttyU[0-9]+ is used so the current code ony works
on
linux.
What my diff does is that it gets the list of all tty devices from
Thanks for the explanation.
SVN now has a slightly different and more obvious approach
On Thu, Apr 22, 2010 at 2:52 PM, Robert Nagy rob...@openbsd.org wrote:
Hey
Basically on linux ttyS* and ttyUSB* is used for serial device names, but
this
is not the case for *BSD, Solaris and probably OS
Hi Robert,
Robert Nagy wrote:
Hey
Basically on linux ttyS* and ttyUSB* is used for serial device names, but this
is not the case for *BSD, Solaris and probably OS X.
If this helps:
macbook-pro:dev foyc$ ls tty*
tty ttyse
tty.BlackBerry9530-BlackBer-1 ttysf
Hello,
The web is all abuzz about LLVM. Would it make the parts of the Mono
runtime that are written in C any more performant? If it does, and if this
is a relatively safe operation, I would consider building Mono this way on
machines that are less experimental.
Anybody have any idea?
12 matches
Mail list logo
