Alan McGovern wrote:
(sorry, just realised last message didn't go to mailing list)
Hi,
Have you tried FileStream.Flush()? ;)
Flush() intentionally doesn't call fsync nor FlushFileBuffers.
Robert
Alan.
On 1/9/07, Patrick Earl [EMAIL PROTECTED] wrote:
Greetings all. I've recently
Hi all,
Are there plans to implement the 'thiscall' calling convention (first parameter
on ECX, the rest on stack) in Mono (for interop, P/Invoke, etc with native
windows libraries) ?___
Mono-devel-list mailing list
Mono-devel-list@lists.ximian.com
A project of mine uses #ctor(String,Exception) on ObjectDisposedException, so I
looked at adding that, and any other similar constructors missing as per the
class status report.
I also spotted inconsistent setting of HResult, and fixed those too. For
instance, ArgumentNullException sets
Hello,
Please review attached patch that fixed SettingsPropertyValue.IsDirty
property, it aslo corrects default value deserialization when it's null.
Vladimir
SettingsPropertyValue.cs.patch
Description: SettingsPropertyValue.cs.patch
SettingsPropertyValueTest.cs.patch
Description:
Woops, if the patch is possibly useable I should attach it! This time.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf
Of Andy Hume
Sent: 10 January 2007 20:00
To: mono-devel-list@lists.ximian.com
Subject: [Mono-dev] Patch to add missing v2
If I wanted to add this functionality to the mono class library so no
p/invokes are required, does anyone have any suggestions where it
should be added? I've seen most new functionality added to Mono.*
classes, but I don't see anything like Mono.IO. Are there any
guidelines on where something
Have you tried FileStream.Flush()? ;)
Flush() intentionally doesn't call fsync nor FlushFileBuffers.
Well, the original reason cited for a cross platform fsync() call was to
perform a flush to disk operation on a filestream. I believe that's
*exactly* what FileStream.Flush() is for. So
Hello Andy,
Woops, if the patch is possibly useable I should attach it! This time.
Your patch works, I have applied it.
___
Mono-devel-list mailing list
Mono-devel-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list
Hi,
I have attached a patch to 'mono/mini/mini-x86.c' that allows Mono JIT to
handle ThisCall convention on windows.correctly.
This allows for interop/pinvoke with visual c++ compiled classes/methods. (For
GCC cygwin/mingw 'Cdecl' should be used)
The changes are in effect only on the x86
Hi,
This patch implements Marshal.ReAllocCoTaskMem. I know shifting the
icalls isn't needed, but it looks cleaner keeping them in order since
Marshal has so many (plus VS does column selection so it's just a
copy/paste).
Thanks,
Jonathan
ReAllocCoTaskMem.diff
Description: Binary data
Hello,
I have problem with compile Mono, to run on my Strong Arm board.
This board is made of Intel SA1110 cpu and have 64Mb of RAM and 32Mb of FLASH.
On it is already ported Linux kernel 2.4.18. I would like to build mono for this
platform, but I don't have enough knowleage to do this job.
I
Hello,
A company developing consumer products is looking for a JIT
developer interested in implementing the AOT support for Mono on the
StrongARM CPU and having someone knowledgeable about Mono on staff.
Let me know if you are interested.
Miguel
12 matches
Mail list logo