Pull Request #1631: rename msg_* to blip_*

Development archive
1

Hi guys,

my PR #1631 changes all msg_* function and structure names to blip_*.

This is a prerequisite to a new messaging API that will be a lot more flexible.

As I'd like to keep the old functions for compatibility and functional reasons, I'm just renaming them for now.

The new API will allow messages bigger than "type"+"content", but will also be content agnostic (no type field).

The old (now blip_*) api will stay the same. I'm thinking to also use them for the riot equivalent of "signals", which will be short messages with defined content, like "exit the thread if you receive this".

Do you have any suggestions for a different name than "blip"?

Kaspar

2

Hi Kaspar,

what happened to note_*?

Cheers, Martine

3

Hi Martine,

4

Hi,

5

Maybe 'ipc_*'?

Le 10/09/2014 20:11, Kaspar Schleiser a �crit :

6

Hi,

7

Hi,

8

Hi,

This is a prerequisite to a new messaging API that will be a lot more flexible.

What does "a lot more flexible" entail?

The new API will allow messages bigger than "type"+"content", but will also be content agnostic (no type field). ... Do you have any suggestions for a different name than "blip"?

How about you name the new API "packet" instead?

Cheers, Ludwig

9

Hi,

10

Hi!

> Do you have any suggestions for a different name than "blip"?

How about you name the new API "packet" instead?

Nope, that's to confusing with network functionality.

I still like "mem_*" for the new API.

Cheers, Oleg

11

Hi

12

I think that would be the easiest solution, because we would not have to advertise this big API change.

13

Hi,

14

Hi,

15

I thought you wanted to make this beast telemetric as well?

In any case - yes it is.

Cheers, Ludwig

16

Hi,

17

Hi,

18

Hi,

19

Hi,

20

I understand, thanks for clearing it up.

Cheers, Ludwig