Comments (3)
One concern:
If the output filenames are not available at cmake configuration time, it would make things much harder.
So we should most likely make sure that the output filenames are deterministically inferable from the input file names (without running a parser, I would like to avoid that during config time).
from flatdata.
I prefer to have a single output file. The rationale is that the code is generated and therefore - not really meant for human editing. Splitting code in multiple files is usually done to enable people to work on different independent parts, i.e. it implies better maintainability. The latter is not important for generated code.
In case of python, they made an unfortunate decision to bind modules to the filesystem.
@imagovrn: If we are not going to work on this, what do you think about closing this issue?
from flatdata.
We do not support including other files at the moment, so closing until this is needed
from flatdata.
Related Issues (20)
- Add support for reading from TAR archive HOT 1
- Add clean/delete function to ArchiveBuilder(s) HOT 3
- Expose maximum possible value for primitive types in generated code HOT 2
- Release flatdata-cpp
- Archive::describe does not describe sub-archives
- Create a `How to contribute` section HOT 1
- Publish on PyPI HOT 2
- Publish on ReadTheDocs.org HOT 9
- Specify sorting order in schema
- Add annotations for offset based references
- Replace memmap crate
- Flatdata schema parser does not check explicit_reference HOT 1
- Struct::to_string broken for enumeration fields
- Dot diagrams do not properly name enumerations
- flatdata does not report errors in optional sub-archives
- Opening archives with broken optional sub-archive is not failing
- Comparison to FlatBuffers HOT 4
- Expected archive schema string does not match generated resource schema. HOT 2
- Add size() method to flatdata::ResourceStorage and/or flatdata::Archive
- Release flatdata-rs HOT 3
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 flatdata.