NRF_BLE_SCAN_NAME_MAX_LEN is not documented correctly?

[RVM]

I am using the Scanning module in NRF5 SDK v17.1.x to set up a BLE scanner that matches  a specific name e.g. 'NordicSemi'.
The above string contains 10 characters  ( But the underlying C string length is presumably set to '11' ? )

Most BLE related specifications refer to a 'length' as the core number of entries in the data.

BUT, I observe that the scanner fails to match if I use this value: 

#define NRF_BLE_SCAN_NAME_MAX_LEN     10

The scanner does detect the remote if I use THIS value:

#define NRF_BLE_SCAN_NAME_MAX_LEN     11

Cheers
RVM

[Elfving]

Hi RVM, 

I'm not 100% sure, but I would assume that this is the null character occupying an additional space. Setting it to 11 does work for you, so this is not really an issue but you are just wondering why?

Regards,

Elfving

[RVM]

What I wanted to bring to your attention is that the NULL character is also significant.
But that is not usually the case for common lexicographic comparisons and is counter intuitive.
Anyways, this was just a FYI and I do not expect any updates from Nordic