Open flaxed opened 5 years ago
I don't see how it's related to DDL. Anyone can do anything they want with it, including embedding it somewhere else, it's their responsibility to extract and parse it.
It's just a nice feature to have. Obviously not the most important to add. If we can add value for a scenario that is more productive for the user, that ends up being better for the project.
I think we have different expectations for the scope of the DDL.
This isn't a major feature, but might be useful.
It would allow whoever is using our tools to provide a file that doesn't contain exclusively
.ddl
or even.xdl
content to parse the relevant.ddl
content.Let's assume we have a HLSL shader with
.ddl
content:This would allow for the project pipeline to parse the shader inputs definition, generate all the useful files, including a
CBuffer
definition that gets injected directly into the file, and.h
files with a struct that maps directly to theCBuffer
.Also improves development workflow since the dev only needs to work in a single file.