-
Notifications
You must be signed in to change notification settings - Fork 12
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
v2.0.7: inconsistencies in SedStyle
#67
Comments
I'm also not happy about the renaming, and if you have a better name, then that would be fine. I also dislike the redundancy of the Style object having |
Agreed. Unfortunately, I can't think of a better name at this stage.
Heartily agreed with that one too.
Yes, although I don't like the current names, I am also in favour of consistency... :) |
I think we decided to stick with the current names--can this be closed? |
I am good with the way it is right now. Can be closed from my side. |
SedLine
-related things inSedStyle
used to be namedxxxLine()
, but with the release of v2.0.7 they are now namedxxxLineStyle()
. I can see why (to avoid conflicts withSedBase
'sgetLine()
method. However, two issues:SedStyle
definesSedLine* mLine
, which shadowsSedBase::mLine
. So, I would expectSedStyle::mLine
to be renamed toSedStyle::mLineStyle
.xxxLine()
toxxxLineStyle()
makesxxxMarker()
inconsistent. So, I would expectxxxMarker()
to be renamed toxxxMarkerStyle()
andSedStyle::mMarker
toSedStyle::mMarkerStyle
.The text was updated successfully, but these errors were encountered: