Oops yes ;-)
BTW Kazuki cooked patches to reduce those memory usage with little
cost:
http://kserver.panicode.com/memo/2007/12/30/0
(327KB - 57KB)
http://kserver.panicode.com/memo/2007/12/31/0
(57KB - 20KB)
Atsushi Eno
Juraj Skripsky wrote:
Hello,
I think the following two arrays account
();
}
return path;
}
}
To me it looks that it just tries to skip security assertion.
Atsushi Eno
Original Message
Subject: [Mono-patches] r92329 - trunk/mcs/class/System.Web/System.Web.Util
Date: Sun, 6 Jan 2008 03:14:55 -0500
Just to not let people investigate into and waste time on the same
issue, this issue is fixed at r92196 without notice here.
Atsushi Eno
Juraj Skripsky wrote:
Hi Igor,
I've noticed something strange in your latest commit:
+ private void WriteExpandoAttributes
in mono (!TARGET_DOTNET).
I agree that you'd need TARGET_DOTNET while am glad to hear that it
does not happen much.
Atsushi Eno
Konstantin Triger wrote:
Hey Eno,
I did not completely understand your comment, but let me explain the
background, so you will understand what Igor meant by this patch
Hello,
I'll take a look, but it had better be filed as a bug on bugzilla so
that the issue can be tracked down and is safer in case I just forget:
http://www.mono-project.com/Bugs
Atsushi Eno
Mads Bondo Dydensborg wrote:
Hi there
I have a difference between output in current Mono SVN
Hi,
Ok, I've applied your patch, with a new NUnit test case (it is
possible to write a test for assuring WSDL contents by
ServiceDescriptionReflector). Thanks.
Atsushi Eno
Arina Itkes wrote:
Hi,
A wsdl file generated by a web service on IIS that has a method
with SOAPAction
like as operator which sometimes makes the sources
more readable and kind enough for code completion depending on
the editor/IDE.
Atsushi Eno
Juraj Skripsky wrote:
Hi Rodrigo,
SelectSingleNode (cp) returns an XmlElement if an element cp is
found or null otherwise. So the explicit cast should
Hey,
Well, my comments are more specific to the case that Rodrigo pointed
out. I in general agree with your preference on explicit cast over
as in theory.
Atsushi Eno
Juraj Skripsky wrote:
Hi Atsushi,
I agree that the preference of the explicit cast is a matter of personal
taste in almost
results, but if you fix them, they will fail on mono.
Atsushi Eno
Roei Erez wrote:
Hi,
I have noticed that the following CharCategory related tests fails when
running on MS:
CharCategoryTest.IsDigit
CharCategoryTest.IsLower
CharCategoryTest.IsNumber
Hello,
Agreed. If there's no objection I'd welcome such a change (or will do if
no one does but not sure when).
Atsushi Eno
Hi, Atsushi.
So right now Mono 2.0 behaves like .Net 1.1.
What about making Mono compatible with .Net 2.0? This will make Mono 1.1
behave like .Net 2.0 but since
Hi,
It's mostly done, except for XStreamingElement (I just haven't
looked at this new stuff in depth yet).
See mcs/class/System.Xml.Linq. It is built within net_3_5 profile.
Atsushi Eno
Andrew Koryavchenko wrote:
Hello
Is anyone know, what happens with System.Xml.Linq implementation
http://mono-project.com/Bugs
Andrew Koryavchenko wrote:
Hello
Here is exceptions (on .NET runtime all running OK):
Failures:
1) Rsdn.SmartApp.Configuration.ConfigServiceTest.NormalRun :
System.ArgumentOutOfRangeException : Less than 0 or more than list count.
Parameter name: index
-1
Hello,
You cannot add reference to System.Data.dll when building
System.Xml. Add your DataSet related test under System.Data.
The fix itself looks ok, except for coding style. I don't think
it was your first contribution though ...?
http://www.mono-project.com/Coding_Guidelines
Atsushi Eno
Hello,
I'm not sure if it really happened or not. It does not happen with
trunk version of sys.xml.linq anyways.
Atsushi Eno
Andrew Koryavchenko wrote:
Hello
Mono System.Xml.Linq implementation ain't work with Microsoft XmlReader.
For example, running this code on .NET with mono xlinq
)
{
if (IsMapExported (map)) return;
Atsushi Eno
Arina Itkes wrote:
Ok. I moved the test to System.Data.
Please explain your claim about coding style. I didn't understand.
Arina.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL
We already have some 3.5 stuff (such as DateTimeOffset). We also have
System.Core.dll (where HashSet lives), so nothing stops you from
contributing implementation for that class :-)
Atsushi Eno
code wrote:
Could part of Mono library goes beyond .NET 2.0? For example, HashSet is
.NET Framework
There isn't.
Atsushi Eno
Scott Fluto wrote:
so 1.9 will be c#3.0 and the .net 3.0/3.5(wpf,wcf...) will be coming
from the olive project and they are on their own timeline then? is there
a roadmap for the olive branch??
scott
-Original Message-
From: Jonathan Pobst [mailto
If Vladimir does not fix his regression, I'll revert r91075 tomorrow.
Atsushi Eno
Robert Jordan wrote:
joel reed wrote:
When I upgrade mono from 1.2.6 to SVN HEAD, I get the following error
making a webservice call:
Unhandled Exception: System.InvalidOperationException
MS.Build.Tasks under
2.1 profile will solve it.)
Atsushi Eno
Index: Microsoft.Build.Tasks/AssemblyResolver.cs
===
--- Microsoft.Build.Tasks/AssemblyResolver.cs (ãªãã¸ã§ã³ 96527)
+++ Microsoft.Build.Tasks/AssemblyResolver.cs (ä½æ¥ã
Thanks JB for the build fix :)
In general when some one changes code in System.ServiceModel, he or
she should also pay attention to System.ServiceModel.Web build.
There had been such build breakages not a few times lately.
Atsushi Eno
Jb Evain wrote:
Hey,
On 3/19/08, Sharique uddin Ahmed
configuration stuff.
Please remove any configuration hook from existing working stuff
such as ChannelFactory. If you do not, I'll revert several things
instead next week, which could mess your work. Thanks in advance.
Atsushi Eno
___
Mono-devel-list mailing
ChangeLog entry such as:
Log:
fix implementation, refactoring
but it is not true. For example for r98854 which you put *new file*
which is neither implementation fix nor refactoring at all.
Atsushi Eno
Igor Zelmanovich wrote:
Hello Atsushi,
There was some not implemented API
Turned out that you actually never logged changes to ChangeLog
(it is not about SVN commit log but about files named ChangeLog.)
We (including you) should always log the changes in those files.
Atsushi Eno
Atsushi Eno wrote:
No matter how it works in your machine, the tests are indeed broken
what you means by Implemented here - they are WS-Security
stuff that involves several
missing WS-* functionality.
That's all so far. Thanks for the nice status page :-)
Atsushi Eno
Miguel de Icaza wrote:
Hello folks,
With Mono 2.0 approaching, it is time to start looking at new
areas
(such as BuildChannelFactory) are implemented.
It could be assumed from the following lines of those lines.
While you interpreted those lines (without implicit context among
the milestone section lines) as if the entire BindingElements
were implemented. That's why such a mismatch happens.
Atsushi Eno
Eyal
It contains Console.WriteLine(). Is it intended? (I haven't tried
it; guessing it may be for code generation.)
Atsushi Eno
Original Message
Subject: [Mono-patches] r99345 - in trunk/mcs/class/System.XML:
System.Xml.Serialization Test/System.Xml.Serialization Test/XmlFiles/xsd
No. When .NET compatibility components in olive get mature, they will be
moved into mcs,
like we have done for System.Core and System.Xml.Linq.
Olive is aggregated experimental stuff.
Atsushi Eno
Sharique uddin Ahmed Farooqui wrote:
Hi,
I think we should distribute olive module with mono
Hello,
As usual, it has NUnit test infrastructure in:
topdir/class/Directory.By.Assembly/Test/Directory.By.Namespaces/Test.By.Class.cs
Basically it should not be a separate test suite unless there is some
appropriate reason.
Atsushi Eno
Roei Erez wrote:
Hi,
We are currently writing
I have no idea why your test stuff does not fit NUnit test suite by
nature, but then
feel free to put your tests into somewhere like
$(topdir)/class/System.ServiceModel/Test/standalone.
(Once it turned out to fit with existing nunit test stuff, we could
integrate it later.)
Atsushi Eno
Roei
implementation, we might want to have diffent
property implementation in Message.
Atsushi Eno
Michael Barker wrote:
Hi,
Attached is a patch for System.Messaging that includes the barest
beginnings of a provider layer. However using the patch below I have
implemented the sending of binary
Yes it is likely (your bug). See:
http://lists.ximian.com/pipermail/mono-list/2007-December/037098.html
Atsushi Eno
Paul Veuve wrote:
Hello,
1. Acces to child nodes with foreach run in an infinite loop
2. Acces to child nodes or nodes in a nodes list by indexer [] acces only
half of nodes
some comments on the patch details, but I'd put my general survey
first :)
Atsushi Eno
Michael Barker wrote:
Hi,
As I mentioned a couple of days ago I have a 0.0.1 version of a bridge
between Mono and QPid. I have placed the code and a patch that adds an
SPI to Mono on google code. http
on the patch details, but I'd put my general
survey first :)
Atsushi Eno
Unfortunately my timing here is not the best. I am about to head off
travelling for about 4 months, so I won't be able to make any major
changes until September. I'll fix the license and add
1) I don't, without concrete patch. But any fixes are welcome.
2) That's non-issue, nor are we hobby copycats that are glad to
waste time on mimicking .net behavior.
Atsushi Eno
Sasha Kogan wrote:
To reproduce the bug:
in MonoTests.System.Xml.Linq.XNodeReaderTest.CreateReader1
://monoport.com/9806
Atsushi Eno
___
Mono-devel-list mailing list
Mono-devel-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list
The original question is how to do it using framework 1.1.
Process.Start() with user information is only-2.0 feature, so
it is out of scope anyways.
I guess it can be done with sudo.
Atsushi Eno
Jacob Gladish wrote:
Agreed assuming it was implemented. I tried a small test and it didn't
Cool, thanks for the fix :) Can you please also attach the new file
resolveUriSchema.xsd ?
Atsushi Eno
James Fitzsimons wrote:
Hi all,
While porting Spring.NET to run on Mono on linux I have discovered a
small bug in the GetResolvedUri method of the XmlSchema class.
I have a custom
Oops, nm, I was blind at 4am ;-) Let me verify and check in svn in
case it worked fine.
Atsushi Eno
Atsushi Eno wrote:
Cool, thanks for the fix :) Can you please also attach the new file
resolveUriSchema.xsd ?
Atsushi Eno
James Fitzsimons wrote:
Hi all,
While porting Spring.NET to run
in
TARGET_JVM and rewritten to fail only on .NET. (Who cares after all?)
Atsushi Eno
___
Mono-devel-list mailing list
Mono-devel-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list
.
Atsushi Eno
Noam Lampert wrote:
Hi Atsushi,
We care about .NET. Please do not rewrite the tests to fail on .NET.
Passing on .NET gives strong confidence that our implementation is
correct, and not only non-regressive.
As you can see, the order of the members in Grasshopper and .NET
does not make sense; the conditional compilation is
done at compile time, not run time. We don't have such switch
anyways. See mcs/class/README for the expected switches.)
Atsushi Eno
Noam Lampert wrote:
I agree that the tests need modification.
There is no intention of compelling Mono to fail
At the time of mono 1.9 there was a couple of bugs in XLinq (well,
and we may still have some bugs). I have no idea what kind of error
there was, but it is already gone in svn.
Atsushi Eno
Maciej Paszta wrote:
Any hints on this strange behaviour (in one xontext the same xml is
successfully
bugs with an earlier revision number).
Atsushi Eno
Leszek Ciesielski wrote:
Hi,
I've been using trac and redmine bug tracking systems with several
other projects I follow, and those two have a feature I miss greatly
in mono bugzilla: links to revisions related to a certain comment/bug
as is, not in string form. This makes
comparison more strict.
* Test/System.Data/DataColumnTest.cs
Added test for non-DBNull case and changing DataType case.
If it looks good, I'll check in it later.
Atsushi Eno
Index: Test/System.Data/DataColumnTest.cs
Sure, you are right. I'll make that change. Thanks.
Atsushi Eno
Gert Driesen wrote:
Atsushi,
I wouldn't use the ExpectedException attribute on the Defaults3 tests,
as it allows for false positives (if any of the other calls results in
an ArgumentException).
Instead just use this (more
Thanks, applied.
Atsushi Eno
Veerapuram Varadhan wrote:
Hi Atsushi,
Patch looks really good to go.
Thanks,
V. Varadhan
On Fri, 2008-06-13 at 01:06 +0900, Atsushi Eno wrote:
Hello,
I have a fix for one of failing sys.data test in 2.0 profile. Here
is description (could be used
any localizable strings.
Atsushi Eno
___
Mono-devel-list mailing list
Mono-devel-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list
Uh, yep I meant such tests.
I'm attaching an example cases in DataTableTest.cs
Atsushi Eno
Gert Driesen wrote:
Hey Atsushi,
I sometimes write tests that check for part of an exception message.
For example:
When the message is Invalid value XXX for argument Z, I'd check for
XXX and Z
.
Atsushi Eno
Andrés G. Aragoneses wrote:
Atsushi Eno wrote:
Hey guys,
I have seen a lot of bad NUnit tests that unnecessarily compare
exception messages. They are wrong not only because they fail
in non-English Windows environment but also because those tests
will fail when Microsoft improves
to not premise DBNull than picking every
possible supported types.
Of course, changing relevant to support INullable is better than
now I think.
Atsushi Eno
Konstantin Triger wrote:
Hello all,
It was strange to me that MS perform a special check for SqlXXX types,
so I started looking what is common
.
Atsushi Eno
Index: System.Data/XmlSchemaWriter.cs
===
--- System.Data/XmlSchemaWriter.cs (revision 105755)
+++ System.Data/XmlSchemaWriter.cs (working copy)
@@ -63,9 +63,10 @@
internal static void WriteXmlSchema
Hey Kosta,
Thanks, that's a good point. I don't think reflection is a soluton
there for performance wise, so I made another fix to replace
Activator.CreateInstance().
Atsushi Eno
Konstantin Triger wrote:
Hey Eno,
Yep, I agree it's a corner case, that can be postponed. Yet I think it's
in DataTableTest.ReadWriteXmlSchema(). It
still has another issue to fix (though now it looks like the same as
another test exposes).
If it looks good, I'll commit it later.
Atsushi Eno
Index: Test/System.Data/DataSetInferXmlSchemaTest.cs
===
--- Test
fix for it.
If the fix looks good, I'll commit it later.
Atsushi Eno
Index: Test/System.Data/TestMerge1.xml
===
--- Test/System.Data/TestMerge1.xml (revision 0)
+++ Test/System.Data/TestMerge1.xml (revision 0)
@@ -0,0 +1,64
constructors that do not have corresponding parameter).
If I set it always true, then one test case in DataSetTest2 fails.
Atsushi Eno
___
Mono-devel-list mailing list
Mono-devel-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list
, or at least block significant performance
improvements.
I see almost no benefits and will revert unless you claim very
important improvements.
Atsushi Eno
Original Message
Subject: [Mono-patches] r106626 - in
trunk/mcs/class/System.Configuration: . System.Configuration
Test
somewhat special eyes on your changes because you usually
seem to make larger changes than usual hackers do. And this time
unfortunately we were actually discussing System.Configuration
refactoring. That's why your change is specially mentioned.
Atsushi Eno
Gert Driesen wrote:
Hey Jb,
Sorry
I think that's kind of mistake we often make; CONFIGURATION_DEP
annoyance. Let's not worry much about it ;-)
Atsushi Eno
Jb Evain wrote:
Hey,
On 6/26/08, Gert Driesen [EMAIL PROTECTED] wrote:
Please be reasonable. What more can you ask?
Is that worth noting that the particular commit
responded to your comments inline.
Gert
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Atsushi Eno
Sent: donderdag 26 juni 2008 17:41
To: Gert Driesen
Cc: 'mono-devel-list'
Subject: Re: [Mono-dev] [Fwd: [Mono-patches] r106626 - in
trunk/mcs/class
with sources.
Atsushi Eno
Andreas Nahr wrote:
The attached patch reduces code duplication in Char by more than 130 lines
and improves the performance of some methods a little bit.
Somebody please have a short look...
Happy Hacking
Andreas
mono-dev next time. I will silently
eliminate extraneous changes. I really don't care about those
pointless compatibility and will be glad to eliminate.
Atsushi Eno
Gert Driesen wrote:
Atsushi,
I'm not deliberately ignoring your or anyone else's advice. Perhaps my idea
of trivial changes
Um, you're right, sadly.
Then; check the name of the argument.
Atsushi Eno
Atsushi,
I did not ask you privately.
Gert
-Original Message-
From: Atsushi Eno [mailto:[EMAIL PROTECTED]
Sent: vrijdag 27 juni 2008 23:34
To: Gert Driesen
Subject: Re: [Mono-patches] r106777
insignificant here.
Atsushi Eno
___
Mono-devel-list mailing list
Mono-devel-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list
As usual, I didn't start insulting posts from my side. Though I'm
pretty much positive to return the same (and more) words to the starter.
Atsushi Eno
Daniel Morgan wrote:
Comments from eno like the one below is one of the main reasons I no longer
felt motivated to contribute to mono
http://lists.ximian.com/pipermail/mono-devel-list/2008-June/028336.html
Atsushi,
If you can find ANY, I mean, ANY insult I addressed to you then please show
me.
Gert
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Atsushi Eno
Sent: zaterdag 28
I stop posting to this really fruitless thread (I've already intended to
do and
actually did that until I was asked to post more).
Atsushi Eno
http://lists.ximian.com/pipermail/mono-devel-list/2008-June/028336.html
Atsushi,
If you can find ANY, I mean, ANY insult I addressed to you
makes such ones.)
Atsushi Eno
Atsushi,
Yes, the argument name in the ArgumentNullException does not match the name
of the method argument.
This is probably because the argument check itself is not performed in the
Find method, but bubbled up.
This is a detail not worth discussing, but also
, some by statistically).
I can almost fully disclose our email exchanges from my side (I was
thinking to forward it here instead, if it were written by myself).
Those messages are friendly given.
Atsushi Eno
Gert Driesen wrote:
Atsushi,
Is that an insult? I've scanned that post several times
they have fair mind and glad to fix their bugs unlike
you guess.
Atsushi Eno
___
Mono-devel-list mailing list
Mono-devel-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list
Thanks, the patch is applied.
Atsushi Eno
Jonathan Gagnon wrote:
Hi,
I just filed a bug (408381) for a problem that I found with the CP1252
encoding. I attached a one-line patch that fixes the problem as well as
a new unit test. Could someone have a look at it? Since
, as long as it could be
almost
harmlessly done. At least we always give our feedback on any desired
changes,
as we used to do :)
Atsushi Eno
This message is an official statement from the position and does not
represent
the position of myself.
Pascal Craponne wrote:
Hi Pablo,
yes, that's
for each thread.
Atsushi Eno
Joshua Tauberer wrote:
From time to time I encounter index out of range errors in
Mono.Xml.Xsl.XslSortEvaluator during my multi-threaded use of a single
XSLT transform object, which I think was due to modifying the state of a
XslSortEvaluator object during
multiple
XslTransform for each thread. Since newobj happens a lot, it shouldn't
be a big problem (for you at least).
Atsushi Eno
Joshua Tauberer wrote:
Atsushi Eno wrote:
Thanks for the patch, but I don't think it makes things better.
It adds extra newobj cost at every transformation time
msxsl:script cannot be thread safe on transform operations as script
writers could write any thread-unsafe operations. If MSDN says it
is thread safe for transformation, then that is wrong. If it were
correct, it requires whatever no one can achieve.
Atsushi Eno
Joshua Tauberer wrote:
Okay, so
thread safe.
So it falls back to my second reply: I don't think we welcome x is
thread safe y is not sort of complication. (And I don't forget
the performance issue in your change yet.)
Atsushi Eno
___
Mono-devel-list mailing list
Mono-devel-list
is released, you'll be able to build
olive (if you are not very unlucky).
BTW (as you are cross posting to moonlight-list) olive has nothing
to do with moonlight anymore.
Atsushi Eno
[EMAIL PROTECTED] wrote:
Hi guys:
Curently is not posible for our development team to change the
development
cannot wait for its release for,
say, half a year.
Having said that, since there isn't a lot of changes in olive and
mono in sync lately, such mismatches between olive trunk and mono
release wouldn't likely to happen once the next 2.0 beta release
gets out.
Atsushi Eno
[EMAIL PROTECTED] wrote:
Ok
) Activator.CreateInstance (
col.DataType, new object [0]);
if (!reader.IsEmptyElement) {
reader.ReadStartElement ();
reader.MoveToContent ();
x.ReadXml (reader);
reader.ReadEndElement ();
}
else
reader.Skip ();
row [col] = x; // not sure if it is filled in case of empty element...
Atsushi
To make sure, the release notes contain changes only from 1.9 (unlike
the page title implies), right?
Atsushi Eno
Marc Christensen wrote:
Hey Everyone,
We've just released Mono 2.0 Preview 1 today! Please help us out by
giving it a try with your applications.
As always, you can get
the title implies as if it were for
the final release notes.
IMO current release notes (including the document title) should be
distinguished from the final one.
Atsushi Eno
Miguel de Icaza wrote:
Hello,
To make sure, the release notes contain changes only from 1.9 (unlike
the page title implies
://msdn.microsoft.com/en-us/library/aa365261(VS.85).aspx
Anyone volunteer to implement it? :) That'd be great.
Atsushi Eno
___
Mono-devel-list mailing list
Mono-devel-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list
don't think Linq to Entities depend on Linq to SQL (does it?).
Linq to SQL is narrow-minded SQL Server only technology. As Pablo
wrote, it is being implemented though (in DBLinq Mono mode, which is
somewhat wider-minded to open to some other vendors).
Atsushi Eno
. It is almost API
complete, but cannot be released without System.ServiceModel.dll
which has a lot of unimplemented annoyance such as WS-*.
Astoria in .NET 3.5 would likely run into the same problem too.
Atsushi Eno
___
Mono-devel-list mailing list
Mono
For reference, we have somewhat similar things: System.Management.dll,
System.EnterpriseServices.dll and System.Messaging.dll.
Atsushi Eno
The problem here is that the dependency WindowsBase.dll has never
been worked on (actually I'm even unsure what kind of
work this dll needs) and hence
Sharique uddin Ahmed Farooqui wrote:
On Wed, Aug 13, 2008 at 7:12 AM, Atsushi Eno [EMAIL PROTECTED] wrote:
Hello,
Sharique uddin Ahmed Farooqui wrote:
Hi,
To day MS has released sp1 of .net 3.5. which has Dynamic data,
Ado.net Entity set, some improvements in Linq to Sql are the new
Hey Marek,
Thanks. OK, that is not much improvement IMO ;-)
Atsushi Eno
Marek Safar wrote:
Hello Eno
As you didn't answer this question, I assume there is not any
improvement on Linq to SQL in fact.
(I'm not confirming you are wrong ;) If there is any improvement,
I would like to tell
Congrats guys :) Do you have any release notes on what's new in
this release?
Atsushi Eno
Rusty Howell wrote:
Hey folks,
We just released the next version of Moonlight!
You can download the Firfefox plugin from http://go-mono.com/moonlight
or get the sources from
http://ftp.novell.com
, and I have
never heard of any problem as of now.
Atsushi Eno
Hi,
What do I need to do to get XIM working with winforms? I've built
2.0preview1 (from the tarballs) and that seems fine. When I run a
winform app from a terminal, I get a line Can't find XIM (or something
similar) which
is likely breaking your mono/mwf
environment.
We cannot introduce any workaround for you, as we cannot avoid call to
XOpenIM() while everything looks fine.
Atsushi Eno
___
Mono-devel-list mailing list
Mono-devel-list@lists.ximian.com
http://lists.ximian.com
. The last maintainers were not me but Mainsoft guys.
Atsushi Eno
___
Mono-devel-list mailing list
Mono-devel-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list
Hola,
Hey,
On 8/19/08, Atsushi Eno [EMAIL PROTECTED] wrote:
You meant System.ServiceModel*.
Of course, thanks :)
Most generally, we have two choices:
Another option I'm thinking about, is to have SL2 *only* versions of
such assemblies in mcs. That is, the code still lives
assemblies actually exists) ?
Since they are not supported assemblies, we could rather live without
them, or something like pkg:dotnet-preview would be better (just to
replace olive, minus UIA stuff).
At least -pkg:wcf and -pkg:cardspace sounds identical.
Atsushi Eno
.
That rather sounds like you have some valid setup for en_US.UTF8
but not for en_GB.UTF8.
Atsushi Eno
___
Mono-devel-list mailing list
Mono-devel-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list
in the near future. (B) won't happen. It is Windows-only ACL things.
Atsushi Eno
___
Mono-devel-list mailing list
Mono-devel-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list
actually hack the source file should
have the right to decision.
Atsushi Eno
___
Mono-devel-list mailing list
Mono-devel-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list
AFAIK it does not already compile.
Atsushi Eno
Rodrigo Kumpera wrote:
The interpreter is no longer supported and there is no guarantee that it
will even compile.
Whatever you might be thinking I can't see why not using mono JIT would
be desirable.
On Wed, Sep 24, 2008 at 7:52 PM, Nuno
Seo Sanghyeon wrote:
2008/9/27 Atsushi Eno [EMAIL PROTECTED]:
I disagree; the only people who actually hack the source file should
have the right to decision.
Isn't source code for API users as much as API developers who hack on it?
It does not contradict my opinion.
Atsushi Eno
Cory Foy wrote:
Atsushi Eno wrote:
I disagree; the only people who actually hack the source file should
have the right to decision.
When I read comments like that, it makes me think that there is an air
of elitism to it, and that if you aren't touching source, you don't have
a say.
You
I don't remember the details but I indeed tried to implement it one
year ago, and gave up for not a minor difference between those ACLs.
http://lists.ximian.com/pipermail/mono-devel-list/2007-September/025096.html
If you take your words and go to implement it, it'd be awesome.
Atsushi Eno
)
BTW do you know if AMQP/Rabbit is going to support message peek
and receive-by-id functionality (in some milestones), as you
mentioned in the early discussion ?
http://www.mail-archive.com/mono-devel-list@lists.ximian.com/msg16731.html
Atsushi Eno
Michael Barker wrote:
Hi,
Patch attached
501 - 600 of 890 matches
Mail list logo
