Skip to content

Conversation

physicsfan
Copy link
Collaborator

Here are my first stabs at modules for librang. There are three top-level modules, "el", "oneparticle" and "onscalar". Each has second-level modules, sharing the same name but with an "n" appended to it, that contain subroutines that are called from subroutines within the top-level modules. I still haven't settled on a good naming convention yet. There are also some third-level modules that contain subroutines called from the second-level. I haven't tried compiling these yet, I would like you to have a look first and give me your comments. One of the conventions that I like to use with modules is to be explicit as to which parts are public. Thus I always set my modules to be "private by default" and then explicitly choose what is public. I feel this is in line with an Object-Oriented philosophy.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant