Hi Sean,
Well, yes and no. It is true .NET was designed to share classes and
objects between .NET languages since they compile directly to the same
MSIL language which makes it possible. What you end up having to do in
such a case is put one languages classes in one dll file, another
languages in another dll, and then write the application up in whatever
language you wish in order to share everyones work. While it makes
sharing between .NET languages possible it still isn't advisable from a
programming standpoint.
When programmers work together on a project the first key to
successfully designing anything is standardisation. Standards on how to
format the code, how to comment the code so everyone on the team
understands what person x did, standardised language, etc. For example,
look at the two different styles of a C# function.
// Sample function 1.
private void MyFunction()
{
// Enter code here.
}
// Sample function 2.
private void
myFunction() {
// Enter code here.
}
Both styles are valid styles of coding a [program, but the manner is
such that without an agreed upon standard two very different coders
would drive each other nuts trying to share code. Especially, with
capitalised words. For example, I like to capitalise the m in My and the
F in Function. Some one else might like humpback notation having the m
in my lower case, but the F in Function capatilised. That is two
different standards that would make a project of any complexity unreadable.
Similar things happen with a project that is split among languages.
While it can be done it can be difficult at a later date to maintain.
Especially, if the parties involved aren't able to understand clearly
the other languages he/she isn't working on.
For example, let's say I write all my code in C++ and C#,and my partner
does VB. Ok, we managed to get this killer game made, and I ride off
into the sunset never to be heard from again. My partner wants to make
upgrades to the game, but he/she doesn't know the languages I wrote my
portion of the game in. He/she either needs to rewrite or learn those
languages to be able to edit and upgrade the portion of the game. It
would have been more practical in the beginning to just have agreed upon
one language so we both could access the source for every part of the
project.
Sean Mealin wrote:
> Or you could use .net, that would cover vb, c# and others. The beautiful
> part is a c# developer can call classes and the such done in vb, and vice
> versa.
>
---
Gamers mailing list __ Gamers@audyssey.org
If you want to leave the list, send E-mail to [EMAIL PROTECTED]
You can make changes or update your subscription via the web, at
http://audyssey.org/mailman/listinfo/gamers_audyssey.org.
All messages are archived and can be searched and read at
http://www.mail-archive.com/[EMAIL PROTECTED]
If you have any questions or concerns regarding the management of the list,
please send E-mail to [EMAIL PROTECTED]
