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

netdev2: remove const modifier from vector in send method #4678

Closed
wants to merge 1 commit into from

Conversation

miri64
Copy link
Member

@miri64 miri64 commented Jan 24, 2016

The const modifier hurts in this instance more than it does good IMHO. There might be a need to change parts of the vector. E.g. sequence numbers of frame headers are better updated in the send method, since the actual device type can store the current sequence number, while netdev2_t doesn't.

@miri64 miri64 added Discussion: RFC The issue/PR is used as a discussion starting point about the item of the issue/PR Process: API change Integration Process: PR contains or issue proposes an API change. Should be handled with care. Community: Hack'n'ACK candidate This PR is a candidate for review and discussion during one of RIOT's monthly Hack'n'ACK parties labels Jan 24, 2016
@miri64 miri64 added this to the Release 2016.03 milestone Jan 24, 2016
@miri64 miri64 added the CI: ready for build If set, CI server will compile all applications for all available boards for the labeled PR label Jan 25, 2016
@haukepetersen
Copy link
Contributor

Not sure I agree, why shouldn't the 802.15.4 intermediate layer not be able to store sequence numbers?

@miri64
Copy link
Member Author

miri64 commented Jan 25, 2016

You mean introduce a new type for that? Sure, for the given case this might be a solution, but I'm still not quite sure if we put to much restrictions with the cons modifier on the API. I can think of a bunch of reasons to change the contents of vector in send. Changing to a different format as XBee does e. g.

@haukepetersen haukepetersen removed the Community: Hack'n'ACK candidate This PR is a candidate for review and discussion during one of RIOT's monthly Hack'n'ACK parties label Jan 26, 2016
@miri64
Copy link
Member Author

miri64 commented Jan 26, 2016

Closed because I will overhaul the intermediate layer this week.

@miri64 miri64 closed this Jan 26, 2016
@miri64 miri64 deleted the netdev2/rfc/send-no-const branch January 26, 2016 17:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CI: ready for build If set, CI server will compile all applications for all available boards for the labeled PR Discussion: RFC The issue/PR is used as a discussion starting point about the item of the issue/PR Process: API change Integration Process: PR contains or issue proposes an API change. Should be handled with care.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants