Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
P
postgres-lambda-diff
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Container Registry
Model registry
Operate
Environments
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Jakob Huber
postgres-lambda-diff
Commits
4ec92b05
Commit
4ec92b05
authored
14 years ago
by
Robert Haas
Browse files
Options
Downloads
Patches
Plain Diff
Correct spelling: longjump() -> longjmp().
parent
79a9decd
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
doc/src/sgml/extend.sgml
+1
-1
1 addition, 1 deletion
doc/src/sgml/extend.sgml
with
1 addition
and
1 deletion
doc/src/sgml/extend.sgml
+
1
−
1
View file @
4ec92b05
...
@@ -322,7 +322,7 @@
...
@@ -322,7 +322,7 @@
If calling backend functions from C++ code, be sure that the
If calling backend functions from C++ code, be sure that the
C++ call stack contains only plain old data structures
C++ call stack contains only plain old data structures
(<acronym>POD</>). This is necessary because backend errors
(<acronym>POD</>). This is necessary because backend errors
generate a distant <function>longj
u
mp()</> that does not properly
generate a distant <function>longjmp()</> that does not properly
unroll a C++ call stack with non-POD objects.
unroll a C++ call stack with non-POD objects.
</para>
</para>
</listitem>
</listitem>
...
...
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