Hi Rodrigo,
this is true but with this sample code:
using System;
using System.Threading;
namespace testThread
{
class Program
{
static void Main(string[] args)
{
Program p = new Program();
Thread t = new Thread(p.ThreadEntryPoint,
Hello,
I currently try to modify Mono (based on 2.6.1) to write C#
applications that meet soft real-time constraints. I want to do
a pre-JIT compilation of nearly all methods and a pre-execution
of most trampoline code.
Look at following snippet that starts a new thread:
ThreadStart ts
Hi !
That's a problem of your code:You first create a ThreadStart
delegate and execute it via Invoke [!] and the you start
the thread, which run the same code!! Do you see? Why do you
do call the invoke method on the thread start delegate, please?
Hope, this helps?
br++mabra
Hi !
Sorry for my TOO FAST MAIL ;-)
I have never seen Trampoline and so, not completely
understood the problem .
If the shown code is generated, I would not know why
and it looks wrong to me.
br++mabra
-Original Message-
From: mono-devel-list-boun...@lists.ximian.com
Using the latest code from git, I encountered another regression from 2.6
(similar to the problem I reported here:
https://bugzilla.novell.com/show_bug.cgi?id=653710). I discovered this in
mono-2-8 from git, but confirmed that it exists on the master too.
The following code fails to compile
Alan,
We do something similar to this in our Mac application. We wrote a custom
attribute which decorates the C# classes that we need to access from
Objective-C. Then we wrote a program which reflects over our compiled .NET
assemblies looking for our attribute then generates Objective-C wrappers
This problem still exists.
Does anyone have an idea?
-- Forwarded message --
From: Chakotey STME chakoteys...@gmail.com
Date: 2010/11/30
Subject: Problem with WCF and IEnumerable as return type
To: mono-devel-list@lists.ximian.com
Hello,
I have a problem with WCF.
If I have
On 06.12.10 06:29 pm, ma...@manfbraun.de wrote:
That's a problem of your code:You first create a ThreadStart
delegate and execute it via Invoke [!] and the you start
the thread, which run the same code!! Do you see? Why do you
do call the invoke method on the thread start delegate,
