beast2 icon indicating copy to clipboard operation
beast2 copied to clipboard

Package-private fields

Open Anaphory opened this issue 9 years ago • 1 comments

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?

Anaphory avatar Apr 24 '15 22:04 Anaphory

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

rbouckaert avatar May 03 '15 23:05 rbouckaert