init_ipc

Gamma: Version 4.0
Prev |  | Next

# `init_ipc`

`init_ipc` -- sets up necessary data structures for IPC.

## Syntax

    init_ipc (my_name, my_queue_name?, domain?)

## Arguments

`my_name`

  A name for this task, as a string. It is only used internally.

`my_queue_name`

  Optional queue name for this task, as a string. This is necessary for asynchronous communication, and it must be unique on the system.

`domain`

  Optional domain name for this task.

## Returns

t on success, otherwise nil.

## Description

Sets up all of the data structures needed prior to attempting any interprocess communication from this task. Messages can be neither sent nor received before this call is made. All Cascade DataHub functions use IPC. If the value of `my_queue_name` is nil, no queue name is assigned and no asynchronous IPC is possible.

## Example

        Gamma> init_ipc("myname","myqueue");
        t
        Gamma>

See the Starting Programs section of the Common Functions chapter (Tutorial One), or the Starting Programs section of the Common Functions for Any Program chapter (Tutorial Two) in the Cogent Tools Demo and Tutorials book for examples of this function used in context.

## See Also

`isend`, `next_event`, `next_event_nb`, `read_point`, `read_existing_point`, `register_point`, `send`, `send_async`, `send_string`, `send_string_async`, `write_point`, `write_existing_point`

Prev | Home | Next
`init_async_ipc` | Up | `isend`

Copyright 1995-2002 by Cogent Real-Time Systems, Inc.