• hmmm, I could implement something similiar. But IMHO, the word weird woule be a good description for that.
    On the other hand, a totally new ble_uuid_t, I agree, could have a lot of side effects.

    Could it be an option for a first step to add a uuid128 field to ble_uuid_t(bluetooth.h) for non NRF52 boards ?
    Uuid and type would stay the way they are used today. For NRF52 everything would stay the way it is now.
    Some more ifdef lines (in bleUUIDEqual,bleVarToUUID) would use this field for 128bit uuids. For 16/32 bit uuids, this could be filled with standard mask (00000000-0000-1000-8000-00805F9B34FB or 16/32 uuids into)

About

Avatar for JumJum @JumJum started