I asked this question a couple of weeks ago, and didn't get a real answer either.
The reason I sometimes prefer the CLR types rather than the C# aliases is that they explictly document their length. In the type of software I write a lot of, there is often a close connection with hardware which has specific register lengths, or bus widths, or whatever. It's useful to maintain that, and it's particularly annoying that if you're a Resharper user, you end up with code which has one set of types where you typed them yourself, and a different set wherever R# has filled in the code.
I can see why this might be hard for Resharper to fix, but I do wish the people who keep doubting that a sane person would want to keep control of the name which is used to reference a native type would run along to comp.lang.c++ and suggest that every typedef which ultimately resolves to 'int' is the unnecessary work of fools.
Hello RomaHagen,
There is no way to do so. Why do you need it?
Sincerely,
Ilya Ryzhenkov
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"
R> How to make resharper generate String instead of string, Int64
R> instead of int and so on.
R>
R> Thanks.
R>
Moreover, it is not always posiible to change from keyword to full type name
--
Eugene Pasynkov
Developer
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"
"Ilya Ryzhenkov" <orangy@jetbrains.com> wrote in message
news:76a2bd0b14e41a8ca2903b7440020@news.intellij.net...
>
>
>
>
>
Hi,
thanks for answer. I simply hate synonyms. I'd rather have one keyword for each situation. Also using true class names seems for me more reasonable.
Roman.
I asked this question a couple of weeks ago, and didn't get a real answer either.
The reason I sometimes prefer the CLR types rather than the C# aliases is that they explictly document their length. In the type of software I write a lot of, there is often a close connection with hardware which has specific register lengths, or bus widths, or
whatever. It's useful to maintain that, and it's particularly annoying that if you're a Resharper user, you end up with code which has one set of types where you typed them yourself, and a different set wherever R# has filled in the code.
I can see why this might be hard for Resharper to fix, but I do wish the people who keep doubting that a sane person would want to keep control of the name which is used to reference a native type would run along to comp.lang.c++ and suggest that every typedef which ultimately resolves to 'int' is the unnecessary work of fools.
Will