Prolog Coding Guidelines: Status and Tool Support

September 18, 2019 Β· Declared Dead Β· πŸ› ICLP Technical Communications

πŸ‘» CAUSE OF DEATH: Ghosted
No code link whatsoever

"No code URL or promise found in abstract"

Evidence collected by the PWNC Scanner

Authors Falco Nogatz, Philipp KΓΆrner, Sebastian Krings arXiv ID 1909.08230 Category cs.PL: Programming Languages Cross-listed cs.LO, cs.SE Citations 1 Venue ICLP Technical Communications Last Checked 4 months ago
Abstract
The importance of coding guidelines is generally accepted throughout developers of every programming language. Naturally, Prolog makes no exception. However, establishing coding guidelines is fraught with obstacles: Finding common ground on kind and selection of rules is matter of debate; once found, adhering to or enforcing rules is complicated as well, not least because of Prolog's flexible syntax without keywords. In this paper, we evaluate the status of coding guidelines in the Prolog community and discuss to what extent they can be automatically verified. We implemented a linter for Prolog and applied it to several packages to get a hold on the current state of the community.
Community shame:
Not yet rated
Community Contributions

Found the code? Know the venue? Think something is wrong? Let us know!

πŸ“œ Similar Papers

In the same crypt β€” Programming Languages

Died the same way β€” πŸ‘» Ghosted