Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
S
sequencer-2-2
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Iterations
Wiki
Jira
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Locked files
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Package Registry
Container Registry
Model registry
Operate
Environments
Terraform modules
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Code review analytics
Issue analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
This is an archived project. Repository and other project resources are read-only.
Show more breadcrumbs
epics-modules
sequencer-2-2
Commits
b18d8a37
Commit
b18d8a37
authored
11 years ago
by
benjamin.franksen
Browse files
Options
Downloads
Patches
Plain Diff
docs: minor change in the reference
parent
c61666aa
No related branches found
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
documentation/Reference.txt
+2
-2
2 additions, 2 deletions
documentation/Reference.txt
with
2 additions
and
2 deletions
documentation/Reference.txt
+
2
−
2
View file @
b18d8a37
...
@@ -587,10 +587,10 @@ empty or not; and any state set that mentions a variable in a
...
@@ -587,10 +587,10 @@ empty or not; and any state set that mentions a variable in a
:token:`when` clause automatically gets woken up whenever the variable
:token:`when` clause automatically gets woken up whenever the variable
changes due to a monitor event. On the other hand, relying on the event
changes due to a monitor event. On the other hand, relying on the event
flag being set as an indication that the queue is non-empty has always
flag being set as an indication that the queue is non-empty has always
been unreliable since another pvGetQ might have intervened and emptied
been unreliable since another
:c:func:`
pvGetQ
`
might have intervened and emptied
the queue between the two calls.
the queue between the two calls.
Note that pvGetQ clears an event flag associated with the variable if
Note that
:c:func:`
pvGetQ
`
clears an event flag associated with the variable if
the queue becomes empty after removing the head element.
the queue becomes empty after removing the head element.
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment