Re: [Mono-dev] Call for release notes comments.
XSP/Mod_mono changes : Mod_mono now supports HTTPS Client Certificate with apache : see http://bugzilla.ximian.com/show_bug.cgi?id=78740 Thanks Le mardi 15 aot 2006 14:39 -0400, Miguel de Icaza a crit : Hello folks, As usual, am calling for people to email me about new features that are worth mentioning in the release notes for 1.1.17. The current -very early draft- is at: http://www.go-mono.com/archive/1.1.17 Miguel. ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list ___Ce message et les éventuels documents joints peuvent contenir des informations confidentielles.Au cas où il ne vous serait pas destiné, nous vous remercions de bien vouloir le supprimer et en aviser immédiatement l'expéditeur. Toute utilisation de ce message non conforme à sa destination, toute diffusion ou publication, totale ou partielle et quel qu'en soit le moyen est formellement interdite.Les communications sur internet n'étant pas sécurisées, l'intégrité de ce message n'est pas assurée et la société émettrice ne peut être tenue pour responsable de son contenu. ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
[Mono-dev] Mono / Java interop, Eclipse Plugin
Hi all, We are building an Eclipse plugin, and we need to access our .NET/Mono libraries from Java. Is there a good way to do this? ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] [PATCH] Use UTF-8 encoding for source files in mcs tree and for ChangeLogs
Kornél Pál wrote:
Hi,
Note that I posted the patch for mcs tree uncompressed but it was too
large and hasn't been approved to the list yet so I resend it zipped.
Currently source files (*.cs; *.vb) use different encodings:
- ASCII
- Latin 1
- UTF-8 (without BOM)
- UTF-8 (with BOM)
The same is true for ChangeLogs but there were mixed encodings as well.
Our mcs compile doen't recongnize UTF-8 without BOM so those files are
incorrectly compiled if they were in Latin 1.
All of our source files should use the same encoding to be consistent that
makes code more maintainable as well. UTF-8 without BOM seems to be a good
solution as it provides support for every possible Unicode character so
this
is a long-term solution for the problem.
I used the attached Latin1ToUtf8.cs to convert the encoding of source files
but I revised each modified character to make sure that the file was
converted from the right encoding to UTF-8.
Additional modifications:
mcs/build/config-default.make: Use UTF-8 as the default encoding for
compilers
mcs/class/Managed.Windows.Forms/Makefile: Removed CODEPAGE as UTF-8 is the
default
mcs/class/Microsoft.VisualBasic/Makefile: Removed CODEPAGE as UTF-8 is the
default
Replaced unnecessary (same visual character) non-ASCII characters with
ASCII
characters in:
mcs/class/Mono.GetOptions/GetOptTest/GetOptTester.cs
mcs/class/System.Drawing/Test/DrawingTest/Exocortex.DSP/src/ComplexF.cs
mcs/class/System.Drawing/Test/DrawingTest/Exocortex.DSP/src/Complex.cs
mcs/class/Microsoft.VisualBasic/Test/standalone/6797.vb
Note that removig BOM and the above replacements resulted in 129 more ASCII
files that were non-ASCII because of BOM or non-ASCII characters.
I think that there are no side effects of these patches but comments are
welcome.
Please review and approve the patches.
Thanks a bunch for the patch! I attached the result of my audit
as only meaningful code changes i.e. I believe I read the
entire changes ;-)
If no objection in reasonable days, let's check the patch in.
Atsushi Eno
Index: mcs/build/config-default.make
===
--- mcs/build/config-default.make (revision 63811)
+++ mcs/build/config-default.make (working copy)
@@ -6,8 +6,8 @@
# DO NOT EDIT THIS FILE! Create config.make and override settings
# there.
-# Use ISO-8859-1 (Latin 1) as the default encoding for compilers
-CODEPAGE = 28591
+# Use UTF-8 as the default encoding for compilers
+CODEPAGE = 65001
RUNTIME_FLAGS =
TEST_HARNESS = $(topdir)/class/lib/$(PROFILE)/nunit-console.exe
Index: mcs/class/Mono.Data.SqliteClient/Test/SqliteCommandUnitTests.cs
===
--- mcs/class/Mono.Data.SqliteClient/Test/SqliteCommandUnitTests.cs
(revision 63811)
+++ mcs/class/Mono.Data.SqliteClient/Test/SqliteCommandUnitTests.cs
(working copy)
@@ -19,7 +19,7 @@
readonly static string _uri = SqliteTest.db;
readonly static string _connectionString = URI=file:// + _uri
+ , version=3;
static SqliteConnection _conn = new SqliteConnection
(_connectionString);
- readonly static string stringvalue = my keyboard is better
than yours : äöüß;
+ readonly static string stringvalue = my keyboard is better
than yours : äöüÃ;
public SqliteCommandUnitTests()
{
@@ -128,7 +128,7 @@
public void ScalarReturn()
{
// This should return the 1 line that got inserted in
CreateTable() Test
- SqliteCommand cmd = new SqliteCommand(SELECT COUNT(*)
FROM t1 WHERE t LIKE '%äöüß',_conn);
+ SqliteCommand cmd = new SqliteCommand(SELECT COUNT(*)
FROM t1 WHERE t LIKE '%äöüÃ',_conn);
using(_conn)
{
_conn.Open();
Index: mcs/class/Mono.GetOptions/GetOptTest/GetOptTester.cs
===
--- mcs/class/Mono.GetOptions/GetOptTest/GetOptTester.cs(revision 63811)
+++ mcs/class/Mono.GetOptions/GetOptTest/GetOptTester.cs(working copy)
@@ -38,7 +38,7 @@
return WhatToDoNext.GoAhead;
}
- public override WhatToDoNext DoHelp() // uses parent´s
OptionAttribute as is
+ public override WhatToDoNext DoHelp() // uses parent's
OptionAttribute as is
{
base.DoHelp();
return WhatToDoNext.GoAhead;
Index: mcs/class/ByteFX.Data/mysqlclient/parameter.cs
===
--- mcs/class/ByteFX.Data/mysqlclient/parameter.cs (revision 63811)
+++ mcs/class/ByteFX.Data/mysqlclient/parameter.cs (working copy)
@@ -358,7 +358,7 @@
}
[Mono-dev] Visual Basic upgrade.
Hello, In the next couple of days, I will remove mbas, the Visual Basic runtime and the various other incomplete forks of mbas that we have on the mcs tree from the tree as they are outdated, no longer under development, unmaintained and buggy. We will replace this with two new components: * Mainsosft's new fresh VB runtime. This fresh VB runtime was written by Rafael Mizrahi and Boris Kirzner completely in VB.NET. The code also contains two extensive test suites: a C# based test suite for low-level components and it consumes plenty of VB tests from the current runtime, compilers and the new vbc from Rolf Bjarne. * Rolf's VB.NET compiler written in VB.NET. Rolf Bjarne has been working on a VB.NET 9 compiler written in VB.NET itself, which is a very good test for the qualities of his compiler. This compiler is very close to bootstrapping and it is also able to build these new class libraries (it can compile itself, and is missing one tiny feature: embedding resources, to be self-hosting) Rolf effort is partially funded by Google Summer of Code program. Miguel. ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] Visual Basic upgrade.
Hello, I also forgot to mention, the new VB Runtime written in VB already has many 2.0 features implemented as well. Hello, In the next couple of days, I will remove mbas, the Visual Basic runtime and the various other incomplete forks of mbas that we have on the mcs tree from the tree as they are outdated, no longer under development, unmaintained and buggy. We will replace this with two new components: * Mainsosft's new fresh VB runtime. This fresh VB runtime was written by Rafael Mizrahi and Boris Kirzner completely in VB.NET. The code also contains two extensive test suites: a C# based test suite for low-level components and it consumes plenty of VB tests from the current runtime, compilers and the new vbc from Rolf Bjarne. * Rolf's VB.NET compiler written in VB.NET. Rolf Bjarne has been working on a VB.NET 9 compiler written in VB.NET itself, which is a very good test for the qualities of his compiler. This compiler is very close to bootstrapping and it is also able to build these new class libraries (it can compile itself, and is missing one tiny feature: embedding resources, to be self-hosting) Rolf effort is partially funded by Google Summer of Code program. Miguel. -- Miguel de Icaza [EMAIL PROTECTED] Novell, Inc. ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] [PATCH] Use UTF-8 encoding for source files in mcs tree and for ChangeLogs
Hello,
We are in the process of cooking up 1.1.17, I would like to
postpone this patch until 1.1.17 is released, so we have more time for
testing.
1.1.17 will be done next week.
Kornél Pál wrote:
Hi,
Note that I posted the patch for mcs tree uncompressed but it was too
large and hasn't been approved to the list yet so I resend it zipped.
Currently source files (*.cs; *.vb) use different encodings:
- ASCII
- Latin 1
- UTF-8 (without BOM)
- UTF-8 (with BOM)
The same is true for ChangeLogs but there were mixed encodings as well.
Our mcs compile doen't recongnize UTF-8 without BOM so those files are
incorrectly compiled if they were in Latin 1.
All of our source files should use the same encoding to be consistent that
makes code more maintainable as well. UTF-8 without BOM seems to be a good
solution as it provides support for every possible Unicode character so
this
is a long-term solution for the problem.
I used the attached Latin1ToUtf8.cs to convert the encoding of source files
but I revised each modified character to make sure that the file was
converted from the right encoding to UTF-8.
Additional modifications:
mcs/build/config-default.make: Use UTF-8 as the default encoding for
compilers
mcs/class/Managed.Windows.Forms/Makefile: Removed CODEPAGE as UTF-8 is the
default
mcs/class/Microsoft.VisualBasic/Makefile: Removed CODEPAGE as UTF-8 is the
default
Replaced unnecessary (same visual character) non-ASCII characters with
ASCII
characters in:
mcs/class/Mono.GetOptions/GetOptTest/GetOptTester.cs
mcs/class/System.Drawing/Test/DrawingTest/Exocortex.DSP/src/ComplexF.cs
mcs/class/System.Drawing/Test/DrawingTest/Exocortex.DSP/src/Complex.cs
mcs/class/Microsoft.VisualBasic/Test/standalone/6797.vb
Note that removig BOM and the above replacements resulted in 129 more ASCII
files that were non-ASCII because of BOM or non-ASCII characters.
I think that there are no side effects of these patches but comments are
welcome.
Please review and approve the patches.
Thanks a bunch for the patch! I attached the result of my audit
as only meaningful code changes i.e. I believe I read the
entire changes ;-)
If no objection in reasonable days, let's check the patch in.
Atsushi Eno
plain text document attachment (mcs-utf8-reduced.diff)
Index: mcs/build/config-default.make
===
--- mcs/build/config-default.make (revision 63811)
+++ mcs/build/config-default.make (working copy)
@@ -6,8 +6,8 @@
# DO NOT EDIT THIS FILE! Create config.make and override settings
# there.
-# Use ISO-8859-1 (Latin 1) as the default encoding for compilers
-CODEPAGE = 28591
+# Use UTF-8 as the default encoding for compilers
+CODEPAGE = 65001
RUNTIME_FLAGS =
TEST_HARNESS = $(topdir)/class/lib/$(PROFILE)/nunit-console.exe
Index: mcs/class/Mono.Data.SqliteClient/Test/SqliteCommandUnitTests.cs
===
--- mcs/class/Mono.Data.SqliteClient/Test/SqliteCommandUnitTests.cs
(revision 63811)
+++ mcs/class/Mono.Data.SqliteClient/Test/SqliteCommandUnitTests.cs
(working copy)
@@ -19,7 +19,7 @@
readonly static string _uri = SqliteTest.db;
readonly static string _connectionString = URI=file:// + _uri
+ , version=3;
static SqliteConnection _conn = new SqliteConnection
(_connectionString);
- readonly static string stringvalue = my keyboard is better
than yours : ;
+ readonly static string stringvalue = my keyboard is better
than yours : äöüß;
public SqliteCommandUnitTests()
{
@@ -128,7 +128,7 @@
public void ScalarReturn()
{
// This should return the 1 line that got inserted in
CreateTable() Test
- SqliteCommand cmd = new SqliteCommand(SELECT COUNT(*)
FROM t1 WHERE t LIKE '%',_conn);
+ SqliteCommand cmd = new SqliteCommand(SELECT COUNT(*)
FROM t1 WHERE t LIKE '%äöüß',_conn);
using(_conn)
{
_conn.Open();
Index: mcs/class/Mono.GetOptions/GetOptTest/GetOptTester.cs
===
--- mcs/class/Mono.GetOptions/GetOptTest/GetOptTester.cs (revision 63811)
+++ mcs/class/Mono.GetOptions/GetOptTest/GetOptTester.cs (working copy)
@@ -38,7 +38,7 @@
return WhatToDoNext.GoAhead;
}
- public override WhatToDoNext DoHelp() // uses parents
OptionAttribute as is
+ public override WhatToDoNext DoHelp() // uses parent's
OptionAttribute as is
{
base.DoHelp();
return WhatToDoNext.GoAhead;
Index:
Re: [Mono-dev] Visual Basic upgrade.
Hello, I also forgot to mention, the new VB Runtime written in VB already has many 2.0 features implemented as well. A few folks have asked me if I really meant VB 9. Apparently I got the naming wrong, I mean the VB that ships with VS 2005. Hello, In the next couple of days, I will remove mbas, the Visual Basic runtime and the various other incomplete forks of mbas that we have on the mcs tree from the tree as they are outdated, no longer under development, unmaintained and buggy. We will replace this with two new components: * Mainsosft's new fresh VB runtime. This fresh VB runtime was written by Rafael Mizrahi and Boris Kirzner completely in VB.NET. The code also contains two extensive test suites: a C# based test suite for low-level components and it consumes plenty of VB tests from the current runtime, compilers and the new vbc from Rolf Bjarne. * Rolf's VB.NET compiler written in VB.NET. Rolf Bjarne has been working on a VB.NET 9 compiler written in VB.NET itself, which is a very good test for the qualities of his compiler. This compiler is very close to bootstrapping and it is also able to build these new class libraries (it can compile itself, and is missing one tiny feature: embedding resources, to be self-hosting) Rolf effort is partially funded by Google Summer of Code program. Miguel. -- Miguel de Icaza [EMAIL PROTECTED] Novell, Inc. ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] [PATCH] Use UTF-8 encoding for source files in mcs tree and for ChangeLogs
Hi, We are in the process of cooking up 1.1.17, I would like to postpone this patch until 1.1.17 is released, so we have more time for testing. 1.1.17 will be done next week. It's OK. Other than this are you OK with UTF-8? Kornél ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] [PATCH] Use UTF-8 encoding for source files in mcs tree and for ChangeLogs
Hello, It's OK. Other than this are you OK with UTF-8? Am fine with it, I think its a good move. ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] [MonoDevelop] OdbcDataAdapter.Fill method
Tony, Are you sure this message was meant for the MonoDevelop IDE List? Maybe you meant the Mono Development List instead? I forwarded your message to mono-devel-list. --- Tony Gu [EMAIL PROTECTED] wrote: Suresh, I got the problem on OdbcDataAdapter.Fill when the table column data type is VarChar (Informix DB), just hands nevery return. Is this problem related to bug #75574? Do you mind show me where did you fix that bug (for bit type)? Thanks! Tony - Do you Yahoo!? Get on board. You're invited to try the new Yahoo! Mail Beta. ___ Monodevelop-list mailing list [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/monodevelop-list __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
[Mono-dev] UTF-8 in ChangeLogs
Hi, All ChangeLogs in mcs and mono are now encoded using UTF-8 that let us use non-ASCII characters (hopefully) without problems. When editing ChangeLogs please use UTF-8. You can use ASCII as well because UTF-8 is ASCII compatible as long as you don't destroy already existing non-ASCII characters. Please don't use byte order marks (BOM) because some editors don't recognize it and it will be left in the middle of the file. To ensure that you don't mess up previous ChangeLog entries the best way is to do an svn diff and verify that older entries are not changed. Note that I'm not going to commit the patch that converts source files to UTF-8 before 1.1.17 is released. I committed this patch because it does not affect any code files. Kornél ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] [mono-vb] Visual Basic upgrade.
Hello, It's great to hear this is working out! Are there binary snapshots available of vbnc? Is there a website or somewhere the progress is tracked? The code is on SVN, module `vbnc', currently you need an MS compiler to bootstrap it, but in the next few days I will start working on putting the packages together. ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
