gvsafronov/futriix
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Fix modules intro typos.

Browse Source
This commit is contained in:
jamespedwards42 2016-05-29 15:53:24 -07:00
parent 26630a6fb1
commit 3a1c815a6a
1 changed files with 3 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
src/modules/INTRO.md
View File

@ -344,7 +344,7 @@ section).
# Releasing call reply objects # Releasing call reply objects
Reply objects must be freed using `RedisModule_FreeCallRelpy`. For arrays, Reply objects must be freed using `RedisModule_FreeCallReply`. For arrays,
you need to free only the top level reply, not the nested replies. you need to free only the top level reply, not the nested replies.
Currently the module implementation provides a protection in order to avoid Currently the module implementation provides a protection in order to avoid
crashing if you free a nested reply object for error, however this feature crashing if you free a nested reply object for error, however this feature
@ -623,7 +623,7 @@ access) for speed. The API will return a pointer and a length, so that's
possible to access and, if needed, modify the string directly. possible to access and, if needed, modify the string directly.
size_t len, j; size_t len, j;
char *myptr = RedisModule_StringDMA(key,REDISMODULE_WRITE,&len); char *myptr = RedisModule_StringDMA(key,&len,REDISMODULE_WRITE);
for (j = 0; j < len; j++) myptr[j] = 'A'; for (j = 0; j < len; j++) myptr[j] = 'A';
In the above example we write directly on the string. Note that if you want In the above example we write directly on the string. Note that if you want
@ -783,4 +783,3 @@ Documentation missing, please check the following functions inside `module.c`:
RedisModule_IsKeysPositionRequest(ctx); RedisModule_IsKeysPositionRequest(ctx);
RedisModule_KeyAtPos(ctx,pos); RedisModule_KeyAtPos(ctx,pos);