>>Hi,
>>Given:

public class A {}
>>public class B
>>{
>>    public static implicit operator B(A a) { return new B(); }
>>    public static implicit operator C(B b) { return new C(); }
>>}
>>public class C {}

Would you find a statement like this too opaque:

C c = (B)new A();

>
>Seems authentically C to me ;-)
>
>You may have read the C++ Journal some years ago. The back page was a monthly column called Obfuscated C, in which valid C/C++ code was printed and readers were invited to decipher exactly what it did.
>
>Mostly joking there. I find C# a lot more accessible than the older dialects and pleasant enough to work with. (My image of K&R C was a bunch of bearded guys in sandals who didn't necessarily want you to understand the code).

The odd thing is that, AFAICS, as I got more comfortable with C# syntax I found it easier to scan (and write) 'compact' code rather than the more verbose version (but C# is always going to be *way* more readable than C++ at its most obscure)

>And now with some downtime (hopefully not much of it) I have the opportunity to return to my studies. Haven't quite decided but trending toward a focus on ASP.NET / C#.

I've had to do a certain amount of ASP.NET work - but I've never really *enjoyed* working with it :-{
I *do* like using WPF (and Silverlight)
But I've no idea what the relative job opportunities are. I'm sure WPF guys are harder to find - just don't know how many companies are looking .....