stuff
This commit is contained in:
parent
86037398ca
commit
b28248ca03
3 changed files with 49 additions and 1 deletions
BIN
build/report.pdf
BIN
build/report.pdf
Binary file not shown.
|
@ -440,3 +440,51 @@
|
|||
year = {2015},
|
||||
publisher = {Elsevier}
|
||||
}
|
||||
@article{DSLSANDHOW,
|
||||
author = {Mernik, Marjan and Heering, Jan and Sloane, Anthony M.},
|
||||
title = {When and how to develop domain-specific languages},
|
||||
year = {2005},
|
||||
issue_date = {December 2005},
|
||||
publisher = {Association for Computing Machinery},
|
||||
address = {New York, NY, USA},
|
||||
volume = {37},
|
||||
number = {4},
|
||||
issn = {0360-0300},
|
||||
url = {https://doi.org/10.1145/1118890.1118892},
|
||||
doi = {10.1145/1118890.1118892},
|
||||
abstract = {Domain-specific languages (DSLs) are languages tailored to a specific application domain. They offer substantial gains in expressiveness and ease of use compared with general-purpose programming languages in their domain of application. DSL development is hard, requiring both domain knowledge and language development expertise. Few people have both. Not surprisingly, the decision to develop a DSL is often postponed indefinitely, if considered at all, and most DSLs never get beyond the application library stage.Although many articles have been written on the development of particular DSLs, there is very limited literature on DSL development methodologies and many questions remain regarding when and how to develop a DSL. To aid the DSL developer, we identify patterns in the decision, analysis, design, and implementation phases of DSL development. Our patterns improve and extend earlier work on DSL design patterns. We also discuss domain analysis tools and language development systems that may help to speed up DSL development. Finally, we present a number of open problems.},
|
||||
journal = {ACM Comput. Surv.},
|
||||
month = {dec},
|
||||
pages = {316–344},
|
||||
numpages = {29},
|
||||
keywords = {Domain-specific language, application language, domain analysis, language development system}
|
||||
}
|
||||
|
||||
@misc{CodeQL,
|
||||
title = {{CodeQL}},
|
||||
year = {2024},
|
||||
month = may,
|
||||
urldate = {2024-05-29},
|
||||
note = {[Online; accessed 29. May 2024]},
|
||||
url = {https://codeql.github.com}
|
||||
}
|
||||
|
||||
@misc{Coccinelle,
|
||||
title = {{Coccinelle The Linux Kernel documentation}},
|
||||
year = {2024},
|
||||
month = may,
|
||||
urldate = {2024-05-29},
|
||||
note = {[Online; accessed 29. May 2024]},
|
||||
url = {https://docs.kernel.org/dev-tools/coccinelle.html}
|
||||
}
|
||||
@inproceedings{CodeQLStuff,
|
||||
author = {Moor, Oege de and Verbaere, Mathieu and Hajiyev, Elnar and Avgustinov, Pavel and Ekman, Torbjorn and Ongkingco, Neil and Sereni, Damien and Tibble, Julian},
|
||||
booktitle = {Seventh IEEE International Working Conference on Source Code Analysis and Manipulation (SCAM 2007)},
|
||||
title = {Keynote Address: .QL for Source Code Analysis},
|
||||
year = {2007},
|
||||
volume = {},
|
||||
number = {},
|
||||
pages = {3-16},
|
||||
keywords = {},
|
||||
doi = {10.1109/SCAM.2007.31}
|
||||
}
|
||||
|
|
|
@ -39,7 +39,7 @@
|
|||
\clearpage
|
||||
\DeclareRobustCommand{\VAN}[3]{#3}
|
||||
\addcontentsline{toc}{chapter}{Bibliography}
|
||||
\bibliographystyle{plain}
|
||||
\bibliographystyle{generators/myplainnat}
|
||||
\bibliography{generators/refs}
|
||||
\appendix
|
||||
\titleformat{\chapter}[display]
|
||||
|
|
Loading…
Reference in a new issue