Releases: tsolomko/BitByteData
1.4.2 Test
Testing that nothing is broken before releasing 1.4.2.
1.4.1
1.4.0
1.4.0 Test
This is a test release for the upcoming 1.4.0 update. This update will include drastic changes to the internal implementation of all readers with the goal of significant improvements to the performance. Naturally, there should be NO other visible changes to the behavior of BitByteData. To ensure that this is, in fact, the case I would like to invite to test this release everyone who has the opportunity to do so. But keep in mind, that this is still a test release and it is not recommended to use it on a day-to-day basis (if everything goes well, the 1.4.0 update will go out some time next week).
Here are the instructions to install the test release:
For Cocoapods users
Replace the BitByteData dependency line in your Podfile with the following:
pod 'BitByteData', :git => 'https://github.com/tsolomko/BitByteData.git', :tag => '1.4.0-test'
Don't forget to revert the changes to your Podfile after the 1.4.0 update is released.
For Swift Package Manager users
Replace the BitByteData dependency line in your Package.swift manifest file with the following:
.package(url: "https://github.com/tsolomko/BitByteData", from: "1.4.0-test"),
Don't forget to revert the changes after the 1.4.0 update is released.
For Carthage users
Replace the BitByteData dependency line in your Cartfile with the following:
github "tsolomko/BitByteData" "1.4.0-test"
Don't forget to revert the changes to your Cartfile after the 1.4.0 update is released.
1.3.1
1.3.0
- Updated to support Swift 4.2.
- Added
advance(by:)
function to bothLsbBitReader
andMsbBitReader
. - Added
write(unsignedNumber:bitsCount:)
function to bothLsbBitWriter
andMsbBitWriter
(thanks to @cowgp for proposing and implementing this in PR #1).
Comment: There are plans to add both advance(by:)
and write(unsignedNumber:bitsCount:)
functions to corresponding protocols in the next major update.
Known potential issues:
-
For Cocoapods users. It seems like Xcode 10 changed how it sets build environment variables. Particularly, it no longer sets variables which have empty string values. This change breaks custom build scripts added to projects by Cocoapods. If you encounter problems with building/installing BitByteData with something about "unbound variable" in your Cocoapods verbose log, this means that you, most likely, have this issue. Thankfully, 1.6.0 version of Cocoapods is going to fix this problem, but at the time of this writing it hasn't been released yet. Meanwhile, I would like to recommend upgrading to the beta version of Cocoapods 1.6.0 if you have this problem. You can learn more about this issue here.
-
For Carthage users. You may notice that the size of "BitByteData.framework.zip" archive attached to this release (that is generated and used by Carthage) is significantly smaller than the one for 1.2.0 update. Upon investigation I discovered that dSym files inside it have become a lot smaller, but I am currently unable to determine what exactly has changed about them. If you encounter any problems which may be connected with this observation, please, let me know.
1.3.0 Test
This is a test release for the upcoming 1.3.0 update which will include several API additions and some other minor changes.
1.2.0
- Updated to support Swift 4.1.
- Added
bytesLeft
andbytesRead
computed properties toByteReader
. - Added
int(fromBytes:)
,uint16(fromBytes:)
,uint32(fromBytes:)
, anduint64(fromBytes:)
functions toByteReader
(and bit readers, since they are inherited fromByteReader
). - Added
byte(fromBits:)
,uint16(fromBits:)
,uint32(fromBits:)
, anduint64(fromBits:)
functions toLsbBitReader
andMsbBitReader
, as well asBitReader
protocol. int(fromBits:)
function now has a precondition that its argument doesn't exceedInt
bit width.- Reverted "disable symbol stripping" change from 1.1.1 update, since underlying problem in Carthage was fixed.
- Small updates to documentation.
1.2.0 Test 3
- Updated to Swift 4.1/Xcode 9.3.
- Reverted change, that explicitly disabled STRIP_INSTALLED_PRODUCT Xcode project setting to workaround Carthage problems with archiving.
- Small updates to documentation.
1.2.0 Test 2
In this second test release several precondition checks introduced in the previous test release were corrected, as well as more missing functions were added.