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.

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

Package-private fields #327

Open
Anaphory opened this issue Apr 24, 2015 · 1 comment
Open

Package-private fields #327

Anaphory opened this issue Apr 24, 2015 · 1 comment

Comments

@Anaphory
Copy link
Contributor

What is the reason that there are quite a few package-private (i.e. not marked as “private”, “protected” or “public”) fields in Beast2 classes?

I am now looking into writing a data type with appropriate substitution model, but all of DataType.Base.stateCount, .mapCodeToStateSet, … are package-private. Is there a good reason that they are, and I should leave them like that? Or is this just because “protected” is more to type than “ ”, and is has not come up yet, so can I change them to beprotected (with a pull request here etc.) without it leading to any problems?

@rbouckaert
Copy link
Member

Please feel free to create pull requests, or simply list fields you want to have access to. I made all DataType.Bare field protected.

tgvaughan added a commit that referenced this issue May 8, 2015
Make package-private properties of substitutionmodels protected instead, as per #327
rbouckaert added a commit that referenced this issue Aug 16, 2015
rbouckaert added a commit that referenced this issue Jan 28, 2019
rbouckaert added a commit that referenced this issue Jun 4, 2019
rbouckaert added a commit that referenced this issue Aug 7, 2019
jordandouglas added a commit that referenced this issue Nov 18, 2019
NicoNeureiter added a commit to NicoNeureiter/beast2 that referenced this issue Apr 23, 2020
rbouckaert added a commit that referenced this issue Apr 23, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants