@COMMENT This file was generated by bib2html.pl <https://sourceforge.net/projects/bib2html/> version 0.94
@COMMENT written by Patrick Riley <http://sourceforge.net/users/patstg/>
@COMMENT This file came from Gal A. Kaminka's publication pages at
@COMMENT http://www.cs.biu.ac.il/~galk/publications/
@inproceedings{msr23,
 author = {Tom Mashiach and Bruno Sotto-Mayor and Gal A. Kaminka and Meir Kalech},
 title = {{CLEAN++}: Code Smells Extraction for {C++}},
 booktitle = {Proceedings of the International Conference on Mining Software Repositories (MSR)},
 year = {2023},
 pages = {441--445},
  wwwnote = {},
  abstract = {
 The extraction of features is an essential step in the process of mining software repositories.
An important feature that has been actively studied in the field of mining software repositories is bad code smells.
Bad code smells are patterns in the source code that indicate an underlying issue in the design and implementation of the software.
Several tools have been proposed to extract code smells.
However, currently, there are no tools that extract a significant number of code smells from software written in C++. 
Therefore, we propose \TOOL\ (Code smeLls ExtrActioN for C++). 
It is an extension of a robust static code analysis tool that implements 35 code smells.
To evaluate \TOOL, we ran it over \PROJECTS\ open-source projects and wrote test cases to validate each code smell. 
Also, we converted the test cases to Java and used two Java tools to validate the effectiveness of our tool.
In the end, we confirmed that the \TOOL\ is successful at detecting code smells.
  }
}