summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorPieter Noordhuis <pcnoordhuis@gmail.com>2010-11-03 12:02:10 +0100
committerPieter Noordhuis <pcnoordhuis@gmail.com>2010-11-03 12:02:10 +0100
commite5a8228946611fea64707a32ecc218ff5e89b497 (patch)
tree824779b3cd57430e8178f5cef015c947d3d8705d
parentcdd026ac791e0767b84f8eafc7e3bddaf5142f4d (diff)
More style
-rw-r--r--README.md24
1 files changed, 12 insertions, 12 deletions
diff --git a/README.md b/README.md
index 76e5961..51ca2a9 100644
--- a/README.md
+++ b/README.md
@@ -86,28 +86,28 @@ The standard replies that `redisCommand` are of the type `redisReply`. The
was received:
* **`REDIS_REPLY_STATUS`**:
- The command replied with a status reply. The status string can be accessed using `reply->str`.
- The length of this string can be accessed using `reply->len`.
+ * The command replied with a status reply. The status string can be accessed using `reply->str`.
+ The length of this string can be accessed using `reply->len`.
* **`REDIS_REPLY_ERROR`**:
- The command replied with an error. The error string can be accessed identical to `REDIS_REPLY_STATUS`.
+ * The command replied with an error. The error string can be accessed identical to `REDIS_REPLY_STATUS`.
* **`REDIS_REPLY_INTEGER`**:
- The command replied with an integer. The integer value can be accessed using the
- `reply->integer` field of type `long long`.
+ * The command replied with an integer. The integer value can be accessed using the
+ `reply->integer` field of type `long long`.
* **`REDIS_REPLY_NIL`**:
- The command replied with a **nil** object. There is no data to access.
+ * The command replied with a **nil** object. There is no data to access.
* **`REDIS_REPLY_STRING`**:
- A bulk (string) reply. The value of the reply can be accessed using `reply->str`.
- The length of this string can be accessed using `reply->len`.
+ * A bulk (string) reply. The value of the reply can be accessed using `reply->str`.
+ The length of this string can be accessed using `reply->len`.
* **`REDIS_REPLY_ARRAY`**:
- A multi bulk reply. The number of elements in the multi bulk reply is stored in
- `reply->elements`. Every element in the multi bulk reply is a `redisReply` object as well
- and can be accessed via `reply->elements[..index..]`.
- Redis may reply with nested arrays but this is fully supported.
+ * A multi bulk reply. The number of elements in the multi bulk reply is stored in
+ `reply->elements`. Every element in the multi bulk reply is a `redisReply` object as well
+ and can be accessed via `reply->elements[..index..]`.
+ Redis may reply with nested arrays but this is fully supported.
Replies should be freed using the `freeReplyObject()` function.
Note that this function will take care of freeing sub-replies objects