---

yaml
---
r: 98280
b: refs/heads/master
c: 67d83ac
h: refs/heads/master
v: v3

Author: Matthias247

[refs]

@@ -1,5 +1,5 @@
 ---
-refs/heads/master: 188167c4b3ab42f1d0dc793365819afe28719df5
+refs/heads/master: 67d83ac40af2c2e20c44e4c16b53e500880a7439
 refs/heads/snap-stage1: e33de59e47c5076a89eadeb38f4934f58a3618a6
 refs/heads/snap-stage3: b6400f998497c3958f40997a71756ead344a776d
 refs/heads/try: c274a6888410ce3e357e014568b43310ed787d36

trunk/doc/guide-ffi.md

@@ -329,6 +329,12 @@ channel where the writing end (`Chan`) is used exclusively from the C callback
 to queue events. The reading end (`Port`) is used in the Rust task which owns
 the wrapper object.
 
+Depending on the type of data in the event you might want to convert callback
+data from C into a more suitable Rust structure before sending it into the
+channel. E.g. it makes sense to convert C strings (`char*`) into Rust strings.
+You could also use Rust enumerations to differentiate between multiple types
+of events and their data.
+
 Putting this together a wrapper for a library that uses a background thread
 that sends events could look like: