Cpp cc file extension

Look through these links to get a better understanding of makefiles, but look mainly the second one, as it clearly says the usefulness of the. C and. I've always used. I recommend. It is of course vitally important that file extensions are acronyms, but should this rationale prove insufficiently compelling other important things are non-use of the shift key which rules out.

This doesn't rule out. I've use. C could be a problem on case insensitive filesystems, but if you have foo. C in the same directory, you deserve what you get anyway :. It doesn't matter which of those extensions you'd use. Pick whichever you like more, just be consistent with naming. On Linux though that's hardly a problem. I ended up here regarding file naming and I thought that I would share how I came up with my choice.

Here goes:. Stroustrup sees this more as a business consideration than a technical one. C rules are just aliases:. When targeting Windows, you are looking for trouble with.

C, as its file system is case-insensitive. And it may be important for you to note that Visual Studio favors the. When targeting macOS, note that Xcode prefers.

You can always change the header template to use. For what it is worth, you can also base your decision on the code bases that you like. Google uses. What about header files? As an example, my emacs config on Linux loads all. Personally, I am not using cc extension, I am trying to lower the number of extensions and not increase them, unless there's a clear value in my opinion. I agree another distinction can be made, but as I wrote, I am trying to lower the number of extensions for simplicity.

Stack Overflow for Teams — Collaborate and share knowledge with a private group. Create a free Team What is Teams? Collectives on Stack Overflow. Learn more. What is the difference between. Asked 12 years, 3 months ago. Active 30 days ago. Viewed k times. Improve this question. Conclusion It doesn't matter. Another tool that cares a little is emacs.

With a clean. Sorry about that! We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, learning, and sharing knowledge. You're trying to visit a URL that doesn't currently exist on the web. Most likely, a member posted a link a long time ago to a web page that has since been removed.

It's also possible that there was a typo when posting the URL. We redirect you to this notice instead of stripping out the link to preserve the integrity of the post. Answered by Ancient Dragon 5, in a post from 11 Years Ago.

The compiler creates a header file and an implementation file for each. The names of the output files are computed by taking the name of the. Packages If a. For example, given the package declaration: package foo.

The class is a concrete class; no pure-virtual methods are left unimplemented. Methods that are virtual in Message but not pure-virtual may or may not be overridden by Foo , depending on the optimization mode. By default, Foo implements specialized versions of all methods for maximum speed. However, if the. This significantly reduces the size of the generated code, but also reduces performance. Alternatively, if the. In particular, it does not support descriptors or reflection. However, in this mode, the generated code only needs to link against libprotobuf-lite.

The "lite" library is much smaller than the full library, and is more appropriate for resource-constrained systems such as mobile phones. You should not create your own Foo subclasses. If you subclass this class and override a virtual method, the override may be ignored, as many generated method calls are de-virtualized to improve performance. The Message interface defines methods that let you check, manipulate, read, or write the entire message, including parsing from and serializing to binary strings.

In addition to these methods, the Foo class defines the following methods: Foo : Default constructor. This contains information about the type, including what fields it has and what their types are. This can be used with reflection to inspect fields programmatically. Note that the default instance of a message can be used as a factory by calling its New method.

Nested Types A message can be declared inside another message. Fields In addition to the methods described in the previous section, the protocol buffer compiler generates a set of accessor methods for each field defined within the message in the. As well as accessor methods, the compiler generates an integer constant for each field containing its field number. The constant name is the letter k , followed by the field name converted to camel-case, followed by FieldNumber.

For field accessors returning a const reference, that reference may be invalidated when the next modifying access is made to the message.

This includes calling any non- const accessor of any field, calling any non- const method inherited from Message or modifying the message through other ways for example, by using the message as the argument of Swap. Correspondingly, the address of the returned reference is only guaranteed to be the same across different invocations of the accessor if no modifying access was made to the message in the meantime. For field accessors returning a pointer, that pointer may be invalidated when the next modifying or non-modifying access is made to the message.

This includes, regardless of constness, calling any accessor of any field, calling any method inherited from Message or accessing the message through other ways for example, by copying the message using the copy constructor. Correspondingly, the value of the returned pointer is never guaranteed to be the same across two different invocations of the accessor. If the field is not set, returns the default value.

If the field is not set, returns 0. After calling this, foo will return value. After calling this, foo will return 0. If the field was not set prior to the call, then the returned string will be empty not the default value. The message is free to delete the allocated string object at any time, so references to the object may be invalidated.

Which, of course, poses problems on systems which don't distinguish case in filenames most of them, I thinkat least, I've never encountered any but Unix which do distinguish case.

For whatever reasons, the convention seems to have become established of using. Just be consistent, and don't worry about it. The conventions for header files are even vaguer. The original convention was just to use. Apparently, I wasn't the only one who didn't like this, and a lot of people adopted different rules:. Again, just be consistent although I do think it better to restrict. James Kanze wrote: The conventions for header files are even vaguer.

Just to add a final note on this, some graphical editors can decide to highlight. This discussion thread is closed Start new discussion. Similar topics PHP. NET Framework.