wishlist

[Enoch]

1. Catch IOError and report it by some IntelHexError subclass, at least for the common "No such file or directory" case where the user simply supplies a wrong file name.

2. Devise a mechanism within IntelHex to check for project specific constraints such as "flash memory overflow", "code/data alignment error", "forbidden memory allocated', etc. Simple solution, allow the programmer to supply a function argument which tests the validity of each allocated address.

Thanks, Enoch.

[Alexander Belchenko (bialix)]

I think that 1 is incorrect and 2 is worth to implement, but not in base IntelHex class, but in some smart subclass.
BTW, launchpad has special section for such proposal (as 2) called blueprints: https://blueprints.launchpad.net/intelhex/

I keep that bug report open until Enoch or me will file new blueprint with implementation details for constrained IntelHex class.

[Alexander Belchenko (bialix)]

Re: "2. Devise a mechanism within IntelHex to check for project specific constraints..."

Recent version of IntelHex class implementation allows to user to easily implement such checking via slicing and len(ih). I'll describe this more detailed in docs, I think having HOWTO doc for this will be nice.

[Alexander Belchenko (bialix)]

Keep it open until good doc will be written for newly implemented features.

[Alexander Belchenko (bialix)]

beta version of docs available in trunk