Comments (5)
modern IDEs mean the file name is pretty much irrelevant. Various OS requirements make all lowercase (or uppercase) files more portable and less likely to cause problems. The default file names in QtCreator are all lowercase.
My vote is for all lowercase.
from libcellml-archived.
I think this is just a choice you make and once you do, put it in your coding style document. There are pros and cons for either convention.
My vote is for all lowercase
from libcellml-archived.
I am also in favour of all lowercase when it comes to file names. It does indeed make things easier for portability.
Otherwise, while we are at it, we might want to 'reopen' issue #16. Yesterday, I came across some code in this repository and I must confess that I didn't like the coding style. Now, I agree that it's all very subjective, but it might nonetheless be worth agreeing on something that looks good to most, is 'efficient', etc.
from libcellml-archived.
It seems we should go with lowercase for now and revisit this if it becomes an issue in future.
from libcellml-archived.
Just to add, if we're going for all lowercase, I'd suggest separating words by underscores, as is done (e.g.) for Python module names. It avoids the issue with being unable to parse the words that Randall mentioned.
As Randall notes we've never had portability issues with file names in Chaste, but then we're careful not to have names that are identical apart from case.
from libcellml-archived.
Related Issues (20)
- Windows buildslave(s) HOT 3
- Setup buildbot e-mail notification HOT 3
- Buildbot - GitHub repo changes should trigger build HOT 1
- Agree on some coding style HOT 6
- Use case "Create [very simple] model, serialise to XML (no maths)". HOT 5
- Develop branch required for git flow HOT 1
- Make "Google Test" framework available HOT 1
- Use of `#pragma once` rather than include guards? HOT 9
- Use case 1.i: Create and serialise empty model to XML HOT 4
- Use CodeSynthesis XSD to generate XML bindings HOT 9
- Initial code stub HOT 1
- develop branch: is the name of the gtest folder really suitable?
- develop branch: do we need all of the gtest code? HOT 2
- Development process documentation
- Development process documentation specifically about contribution HOT 5
- Build status on branches view HOT 2
- Name of the library built with cl.exe should be libcellml
- Cmake config to treat compile warnings as errors HOT 11
- Use case 1.ii: Create and serialise empty validly named model to XML
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from libcellml-archived.