Small typo fixes in quickstart docs
This commit is contained in:
@@ -74,7 +74,7 @@ Build a message
|
|||||||
Initialize a New Cap'n Proto Object
|
Initialize a New Cap'n Proto Object
|
||||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||||
|
|
||||||
Now that you have a message buffer, you need to allocate an actual object that is from your schema. In this case, we will allocate an `AddressBook`::
|
Now that you've imported your schema, you need to allocate an actual struct from that schema. In this case, we will allocate an `AddressBook`::
|
||||||
|
|
||||||
addresses = addressbook_capnp.AddressBook.new_message()
|
addresses = addressbook_capnp.AddressBook.new_message()
|
||||||
|
|
||||||
@@ -98,7 +98,7 @@ For now, let's grab the first element out of this list and assign it to a variab
|
|||||||
|
|
||||||
alice = people[0]
|
alice = people[0]
|
||||||
|
|
||||||
.. note:: It is a very bad idea to call `init` more than once. Every call to `init` allocates new memory inside your Cap'n Proto message, and if you call it more than once, the previous memory is leaked.
|
.. note:: It is a very bad idea to call `init` more than once on a single field. Every call to `init` allocates new memory inside your Cap'n Proto message, and if you call it more than once, the previous memory is leaked.
|
||||||
|
|
||||||
Primitive Types
|
Primitive Types
|
||||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||||
@@ -117,6 +117,8 @@ You can assign straight to the variable with the corresponding Python type. For
|
|||||||
alice.name = 'Alice'
|
alice.name = 'Alice'
|
||||||
alice.email = 'alice@example.com'
|
alice.email = 'alice@example.com'
|
||||||
|
|
||||||
|
.. note:: Text fields will behave differently depending on your version of Python. In Python 2.x, Text fields will expect and return a `bytes` string, while in Python 3.x, they will expect and return a `unicode` string. Data fields will always a return `bytes` string.
|
||||||
|
|
||||||
Enums
|
Enums
|
||||||
~~~~~~~~~~~~~~
|
~~~~~~~~~~~~~~
|
||||||
|
|
||||||
@@ -346,7 +348,7 @@ There are 2 ways to call RPC methods. First the more verbose `request` syntax::
|
|||||||
request.expression.literal = 123
|
request.expression.literal = 123
|
||||||
eval_promise = request.send()
|
eval_promise = request.send()
|
||||||
|
|
||||||
This creates a request for the method named 'evaluate', sets `expression.literal` in that calls parameters to 123, and then sends the request and returns a promise (all non-blocking).
|
This creates a request for the method named 'evaluate', sets `expression.literal` in that call's parameters to 123, and then sends the request and returns a promise (all non-blocking).
|
||||||
|
|
||||||
The shorter syntax for calling methods is::
|
The shorter syntax for calling methods is::
|
||||||
|
|
||||||
|
|||||||
Reference in New Issue
Block a user