Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

should all configure_XX methods contain _fused_? #62

Open
fzahle opened this issue Jan 26, 2015 · 0 comments
Open

should all configure_XX methods contain _fused_? #62

fzahle opened this issue Jan 26, 2015 · 0 comments
Labels
ideas

Comments

@fzahle
Copy link
Member

fzahle commented Jan 26, 2015

In our respective tools we'll probably have our own configure methods for wiring things together. To avoid naming clashes we could try to be consistent and name all FUSED-Wind configure methods as e.g.

configure_fused_bladesurface(assembly):

or

configure_fused_full_bos(assembly):

Will this make our codes more legible or is it unnecessary?
@fzahle fzahle added the ideas label Jan 26, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
ideas
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@fzahle