C# Developers' Journal (original) (raw)

Time

Event

12:44p

http://xmlia.com Dear friends!
We are glad to you to inform on opening new, absolutely free-of-charge site about online XML-validator and web-based editor.

For what to pay huge money for different win-based editors or to put the unchecked cracked copies?
Use our site, and you should not install anything on computer.
Our site does not contain advertising, is quickly loaded,consumes not enough traffic and quickly processes your data.
At your service XML visualisation not only in the form of TREE, but also in the form of GRID, that is actually avaliable only in very expensive windows XML editors.

all what you need to do-its just register for free

See you in http://xmlia.com

3:05p

This is something I've never noticed since working with .NET basically since it was in beta until today, but I find it incredibly lame and odd and I was wondering if anyone here understood the motivation for this awfully VB-like behavior:

int thisInt = 42; string thisString = "This is a string which as far as I know is a primitive in C#.NET!";

string thisShouldNotWork = thisString + thisInt;

thisShouldNotWork == "This is a string which as far as I know is a primitive in C#.NET!42"

WTF? Granted I haven't written in C++ in some time, but I was fairly certain that doing something like this in a real language would result in A) a typecasting exception or B) The string becoming absolute gibberish since the bits of memory being appended to it do not represent the data contained in a string object.

Am I on crack or is this something suspiciously VB-like in C#'s behavior (not to suggest that there aren't many other VB-like behaviors or that C# is some kind of low-level language, but still).