This is the Perl 5 implementation of the SML code library. SML is a minimalistic plain text descriptive markup language which is human readable, enables continuous integration of documentation, expresses and validates semantic relationships, is easy to edit, is easy to generate automatically, and publishes professional documentation from plain text manuscripts.
GNU General Public License v3.0
2
stars
2
forks
source link
Distinguish Between Divisions With and Without an ID #57
Division IDs are either user-specified or system generated.
Certain functions should only apply to divisions that have a user-specified ID. For instance, the new SML::Library 'store_sha_digest_file' method should only store SHA hashes for divisions that have an ID. You can't INCLUDE a division unless it has an ID.
On the other hand, there are some functions that should apply to ALL divisions even if they don't have a user-specified ID. The library division count that summarizes the size and complexity of a library should account for ALL divisions, not just those with a user-specified ID.
Possible solution: use the SML::Library private attribute 'id_hash' to track ALL divisions (leave unchanged). Create a new SML::Library private attribute 'specified_id_hash' to track just divisions with user-specified IDs.
Solving this problem is related to generating the change page (issue #21) because I'm implementing the function that stores the SHA digests for each user-identified division.
Division IDs are either user-specified or system generated.
Certain functions should only apply to divisions that have a user-specified ID. For instance, the new SML::Library 'store_sha_digest_file' method should only store SHA hashes for divisions that have an ID. You can't INCLUDE a division unless it has an ID.
On the other hand, there are some functions that should apply to ALL divisions even if they don't have a user-specified ID. The library division count that summarizes the size and complexity of a library should account for ALL divisions, not just those with a user-specified ID.
Possible solution: use the SML::Library private attribute 'id_hash' to track ALL divisions (leave unchanged). Create a new SML::Library private attribute 'specified_id_hash' to track just divisions with user-specified IDs.
Solving this problem is related to generating the change page (issue #21) because I'm implementing the function that stores the SHA digests for each user-identified division.