Comments (6)
Allowing them would require us to either 1) make a global change, e.g. add a '_' prefix everywhere, or 2) 'escape' only those reserved words, but that would be inconsistent behavior.
Are you fine with just disallowing them, as I did for #4?
from rock.
If you are already checking for all the C99 names in ooc, it wouldn't take much to just escape them instead of preventing their use. It's a step towards making ooc not C-specific
from rock.
Yes, but we are checking them at the parsing stage. What about calls to these functions? We'd have to check again at writing time for both FunctionDecl and FunctionCalls. And the name from C will be different from the one used in ooc, without the use of extern nor unmangled. I think it may be less clear than just disallowing them.
I'd love to have the others' opinion about this.
from rock.
I don't think ooc should disallow names because of a limitation of C. I'd also like to hear other opinions
from rock.
Closing for now, as nobody else has expressed interest in the problem. It seems non-critical for now. A nice addon maybe but maybe not worth the complexity..
from rock.
Fair enough.
from rock.
Related Issues (20)
- pkg-config/CustomPkg flags aren't passed to additionals HOT 2
- Rock cannot find sdk when run from make HOT 2
- Weird behaviour with setters calling associated getter HOT 7
- The way rock constructs class information can lead to data races in seemingly unrelated code HOT 3
- Unexpectedly "good" behaviour from ooc arrays HOT 4
- So, is OOC development still onging? HOT 5
- Rock aborts with interfaces HOT 1
- Problems making after cloning repo HOT 4
- Problem installing: GC_jmp_buf multiple definition HOT 2
- The top 5 bugs? HOT 3
- Template type instances generated in separate modules do not generate include statements in C code HOT 1
- Wrong cast to non scalar type, and some other problems. HOT 3
- Rock parses function arguments with default values incorrectly HOT 1
- 'this' as default parameter value in a function refers to the wrong object HOT 2
- Static variables are not maintained correctly HOT 4
- Add newcomer label to issues HOT 1
- Allow implementing interfaces after type declaration HOT 1
- rock generates invalid C code when trying to access an interface's generic type HOT 2
- Funcs should behave as Closures with extra type information. HOT 7
- rock sometimes segfaults when classes try to implement interfaces
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 rock.