You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Those four elements in @range are not different from the object dimensions, and could be computed on the fly from the object, saving lots of updating in methods that change the dimensions of an FLComp object, say '['
The range() method would return them in the same format, but certain attributes, life fmin, fmax and plusgroup would stay there.
Other packages accessing those numbers directly e.g. object@range['min'], would have to change to
Those four elements in @range are not different from the object dimensions, and could be computed on the fly from the object, saving lots of updating in methods that change the dimensions of an FLComp object, say '['
The range() method would return them in the same format, but certain attributes, life fmin, fmax and plusgroup would stay there.
Other packages accessing those numbers directly e.g. object@range['min'], would have to change to
range(object)['min']
or better still
range(object, 'min')
A simple
/pkg/R $ grep '@range' *.R
would show the places.
@ejardim @drfinlayscott @laurieKell
The text was updated successfully, but these errors were encountered: