What is the difference between string and string

What is the difference between String and string in C? Ask Question. Asked 13 years, 3 months ago. Active 24 days ago. Viewed 1. And what are the differences? Improve this question. Mapper, but the fact remains that string is a lexical construct of the C grammar whereas System. String is just a type. Regardless of any explicit difference mentioned in any spec, there is still this implicit difference that could be accomodated with some ambiguity. The language itself must support string in a way that the implementation is not quite so obligated to consider for a particular class in the BCL.

KirkWoll: According to the language specification, the language itself must consider string to be exactly the same as the BCL type System. String , nothing else.

That is not ambiguous at all. Of course, you can implement your own compiler, using the C grammar, and use all of the tokens found like that for something arbitrary, unrelated to what is defined in the C language specification. However, the resulting language would only be a C lookalike, it could not be considered C.

You can use string without a using directive for System. You can't do that with String. For someone coming from Algol and Fortran, this discussion shows there is something wrong with string. It is needed to abbreviate System. String , but, as an alias, it seems quite like, but not exactly the same thing. After several years of C , though, I'd say, it is safe to simply use string and string. Format and not to worry about System. Sangeeta What are you saying? The System. String class is still there, and the string keyword is still an alias for it.

Just like System. Int32 and int. They are literally the same thing. Show 3 more comments. Active Oldest Votes. Improve this answer. If you decide to use StyleCop and follow that, that will say to use the types specific to the language.

So for C you'll have string instead of String , int instead of Int32 , float instead of Single - stylecop. I always use the aliases because I've assumed one day it might come in handy because they are acting as an abstraction, so therefore can have their implementations changed without me having to know.

Visual Studio says that String. Format should be changed to string. Format, so I guess Microsoft is going that way. I have also always used String for the static methods. I gues then Just be conistent. Use string or String or use a cerntain one in a specific case, but always in that case.

Show 2 more comments. Just for the sake of completeness, here's a brain dump of related information The complete list is: object: System. Object string: System. String bool: System. Boolean byte: System. Byte sbyte: System. SByte short: System. Int16 ushort: System. UInt16 int: System. Int32 uint: System. UInt32 long: System. Int64 ulong: System. UInt64 float: System. Single double: System. Double decimal: System. Decimal char: System. Char Apart from string and object , the aliases are all to value types.

Add a comment. I can say the same about int , System. Int32 etc.. I personally prefer using "Int32", since it immediately shows the range of the value.

Imagine if they upgraded the type of "int" on later higher-bit systems. I'd prefer predictable consistency there, thank you very much. MyDaftQuestions I concur. If anything it would make sense to consistently use the. Nyerguds There are two reasons to simply not worry about it.

One is that int is defined in the C language spec as a 32 bit integer regardless of the hardware. C , despite a shared heritage in the mists of time, is not actually C. Changing int to a 64 bit integer would be a breaking change in the specification and the language. It would also require redefining long , as long is currently the 64 bit integer. The other reason not to worry is irrelevant since the types will never change, but.

Craig I dig into lots of old proprietary game formats where I do have to think about that all the time, though. This is because JavaScript changes a primitive to its object when a method is called through it.

This happens for a very small amount of time just to execute the method and returns back to its primitive self. Then why question may arrive why we will need String object! Need of String Object: When we use the keyword new, TS creates a new object every time unlike when you use a primitive type, if you have the same value for the variables then they point to the same memory. Refer to the below example. Example 1: The below example will shows how a1 and b1 are shown to be equal since they are literals having the same value, whereas a2 and b2 are shown to be different because we used the keyword new which creates two different objects.

Refer to the following example. In this example, we will see how string and String differ when using eval method. We can also evaluate the object by changing it to a primitive string using toString method.

We can use String objects to hold an additional value in the properties. Even though this not commonly used, it is still a feature of JS. The String object are scarcely used. The string primitives only hold the value. The String object have the ability to hold the property. The string are immutable thus are thread safe.

In this article, we will see the differences between string and System. String in C. Are you confused about System. String and string in C? What is the difference between String and string in C?

And how to choose between string and System. October 7, at am. Bagus says:. January 27, at am. November 10, at am. June 11, at pm. June 18, at pm. September 11, at am. Rakesh Reddy says:. January 28, at am. Mosh Hamedani says:.