IPP Software Navigation Tools IPP Links Communication Pan-STARRS Links

Changeset 4084


Ignore:
Timestamp:
Jun 1, 2005, 2:42:48 PM (21 years ago)
Author:
jhoblitt
Message:

change blurb about Threads to clarify requirements

Location:
trunk/doc/pslib
Files:
2 edited

Legend:

Unmodified
Added
Removed
  • trunk/doc/pslib/ChangeLogSDRS.tex

    r4080 r4084  
    1 %%% $Id: ChangeLogSDRS.tex,v 1.119 2005-06-01 22:10:01 jhoblitt Exp $
     1%%% $Id: ChangeLogSDRS.tex,v 1.120 2005-06-02 00:42:48 jhoblitt Exp $
    22
    33\subsection{Changes from version 00 to version 01}
     
    654654  \item rename \code{psFitsAlloc()} $\rightarrow$ \code{psFitsOpen()}
    655655  \item add \code{psFitsClose()}
     656  \item change blurb about ``Threads'' to clarify requirements
    656657  \item remove \code{lock} from \code{psList}
    657658  \item change \code{psVector} to store it's number of elements as an \code{unsigned long int}
  • trunk/doc/pslib/psLibSDRS.tex

    r4080 r4084  
    1 %%% $Id: psLibSDRS.tex,v 1.255 2005-06-01 22:10:01 jhoblitt Exp $
     1%%% $Id: psLibSDRS.tex,v 1.256 2005-06-02 00:42:48 jhoblitt Exp $
    22\documentclass[panstarrs,spec]{panstarrs}
    33
     
    150150\subsection{Threads}
    151151
    152 Pan-STARRS does not have a strong requirement for multithreading
    153 capability.  The memory management functions, defined below, must be
    154 written to be thread-safe. 
     152Pan-STARRS does not have a strong requirement for multithreading capability.
     153The memory management functions, defined below, must be written to be
     154thread-safe.  The use of \code{static} variables should be keep to an absolute
     155minimum and then only when protected by a ``mutex''.  Cross-thread
     156synchronization for PSLib's fundamental datatypes (\code{psArray},
     157\code{psVector}, etc.) is left as an exercise for the end-user.
    155158
    156159\subsection{Conventions}
Note: See TracChangeset for help on using the changeset viewer.