Issue992

Title Make landmark code more readable.
Priority wish Status in-progress
Superseder Nosy List clemens, jendrik, malte, remo, salome, silvan, thomas
Assigned To Keywords
Optional summary
Part of meta issue987.

Created on 2021-01-26.21:02:40 by thomas, last changed by clemens.

Summary
Part of meta issue987.
Messages
msg11764 (view) Author: clemens Date: 2025-02-03.15:12:09
Renaming this issue because we want to extend its purpose. Besides making it consistent with coding conventions, we would also like to have shorter functions, more suitable variable names, and bring comments up to date. All of this should not affect the overall functionality in any of the landmark heuristics.

Since these changes are mostly independent between different parts of the code, we discussed offline that we want to approach this in three stages:
(1) landmark graph and landmarks
(2) landmark heuristics and status manager
(3) landmark factories

If he gets to it, Remo is going to start with (1) as part of the sprint that started today.
msg9823 (view) Author: silvan Date: 2021-01-27.07:58:51
Link to meta issue.
msg9822 (view) Author: silvan Date: 2021-01-27.07:58:22
I think the idea is also to rename variables and methods for better readability, as well as to re-order methods of classes.
msg9816 (view) Author: thomas Date: 2021-01-26.21:02:40
Much of the landmark code violates the coding conventions. In this issue, we'd like to make the landmark code consistent with the coding conventions without changing any functionality.
History
Date User Action Args
2025-02-03 15:12:09clemenssetstatus: chatting -> in-progress
nosy: + remo
messages: + msg11764
title: Make landmark code consistent with coding conventions -> Make landmark code more readable.
2021-01-27 07:58:51silvansetmessages: + msg9823
summary: Part of meta issue987.
2021-01-27 07:58:22silvansetmessages: + msg9822
2021-01-26 21:02:40thomascreate