Per Arneng wrote:
> The reason is: c# language is very good but the .NET API is't allways that > good. and whats with the capital letter in method names. Console.WriteLine. > Its not very nice i really like the java coding conventions and if it was > possible to combine the strength of the c# language with the java API it > would be a winning combination. Let's try to avoid flamefests...deep breath... :) I'm not quite sure if java API is very good choice for C#. On one hand it is nicely designed in most places and people are familiar with it, on the other hand it is heavily dependent on accessor methods. In C# you would use properties. But then it would be nice to have some stuff returned as value types (Dimension/Rectangle etc)... and at some point you will end up 'correcting' java API. Wouldn't it be nice if at some points it would accept List instead of hardcoded Vector ? Etc.etc. So, if you just port java API, letter-for-letter, you will loose a lot of C# features (be it 'strength' or 'weakness' :). But if you will start to change, you will end up with something in between. Maybe it would be just better to start separate project with aim of creating java-like core lib for C#. Reuse/hack out some code from classpath, but do not try to translate it directly. What do you think ? Artur _______________________________________________ Classpath mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/classpath
