As many [Bellhop] users will likely run something like Rs = 0 and use a rangebox of [0, Rmax]
I consider this to be a major usabilty bug as the user has no way of knowing what causes the segfault.
Solution:
Add a check to readIn(), print a warning and exit, or
Silently resize the rangebox so that it includes the source? (maybe do this as a special case for rs = rbox1 = 0.0?)
What ?
Rs == rbox1 causes segfault
As many [Bellhop] users will likely run something like Rs = 0 and use a rangebox of [0, Rmax] I consider this to be a major usabilty bug as the user has no way of knowing what causes the segfault.
Solution: