Skip to content

Modified write_hex_file() to support big endian mode #31

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

Closed
wants to merge 7 commits into from

Conversation

nufsty2
Copy link

@nufsty2 nufsty2 commented Jun 5, 2019

I used a simple reverse algorithm to reverse the data bytes before writing them to the bin dictionary. Use it by specifying new argument "endian_mode" as "big" when calling write_hex_file().

@nufsty2
Copy link
Author

nufsty2 commented Jun 5, 2019

All of the "duplicate" commits were just me removing annoying whitespace changes that my text editor added

@bialix
Copy link
Member

bialix commented Sep 27, 2019

Sorry for not working on your pull request. I'm looking for a new maintainer for Python IntelHex project. I hope someone will help.

@bialix
Copy link
Member

bialix commented Jul 9, 2020

OK, I see - you're modifying data inplace, so after write_hex_file the IntelHex object is totally modified. I don't like such side-effects, and I think it's counter-intuitive to expect them from method that should be just "export" data. So I think your addition is better to make as a separate method. Sorry, I reject your patch.

@bialix bialix closed this Jul 9, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants