Michael,
How dare you go off topic!!!
Just kidding.
As for whether or not you will be able to mix languages in a project,
no, you will not. I don't see this as being doable anytime in the near
future. However, this doesn't mean that you can't mix languages in the same
assembly. You can always compile projects into netmodules and then link
them into a single assembly.
As for comments on Cw, I think that it definitely has its uses, but I
think those uses are specialized. For a general purpose programming
language, I think that it could actually hamper some operations. However,
if your space requires this kind of functionality, then by all means, go for
it. It reminds me of my FoxPro days, where data was more of an ambient
entity than encapsulated in constructs.
One of the beauties of .NET is that you can have all of these different
languages, each with their strengths and weaknesses, and you can make them
all work with each other rather easily, since they all compile down to IL.
Hope this helps.
--
- Nicholas Paldino [.NET/C# MVP]
-
mv*@spam.guard.caspershouse.com
"Michael S" <a@b.c> wrote in message
news:uW**************@tk2msftngp13.phx.gbl...
I've been reading about and trying out Cw from microsoft research.
http://research.microsoft.com/Comega..._startpage.htm
My first cent is that the language is weird but have potential. I have
more cents on the subject but are eager to hear what others have to say.
In future versions of Visual Studio, we will be able to mix languages in a
project. Hence classes that sport a lot of SQL and/or XML could perhaps
benefit from this new weird language.
What I want your opinion on is:
- Is it codable?
- Is it readable?
- Will it help in system development?
- Will you use it?
Happy Discussion
- Michael S
ps.
I hope my favourite gurus Jon, Bruce and Joanna have some input.
pps.
Yesterday I flamed a post for being off-topic. But I choose to ignore that
just now. =)