Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
G
gcc-cobol
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
Package registry
Container Registry
Model registry
Operate
Environments
Terraform modules
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
COBOLworx
gcc-cobol
Commits
c8643122
Commit
c8643122
authored
23 years ago
by
Kaveh R. Ghazi
Committed by
Kaveh Ghazi
23 years ago
Browse files
Options
Downloads
Patches
Plain Diff
* ansidecl.h: Update comments reflecting previous change.
From-SVN: r45275
parent
ec83eb53
No related branches found
No related tags found
No related merge requests found
Changes
2
Hide whitespace changes
Inline
Side-by-side
Showing
2 changed files
include/ChangeLog
+4
-0
4 additions, 0 deletions
include/ChangeLog
include/ansidecl.h
+7
-5
7 additions, 5 deletions
include/ansidecl.h
with
11 additions
and
5 deletions
include/ChangeLog
+
4
−
0
View file @
c8643122
2001-08-29 Kaveh R. Ghazi <ghazi@caip.rutgers.edu>
* ansidecl.h: Update comments reflecting previous change.
2001-08-27 Kaveh R. Ghazi <ghazi@caip.rutgers.edu>
* ansidecl.h (VA_OPEN, VA_CLOSE): Allow multiple uses.
...
...
This diff is collapsed.
Click to expand it.
include/ansidecl.h
+
7
−
5
View file @
c8643122
...
...
@@ -93,11 +93,13 @@ Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA. */
You can declare variables either before or after the VA_OPEN,
VA_FIXEDARG sequence. You can _not_ put statements before VA_OPEN.
Also, VA_OPEN and VA_CLOSE are the beginning and end of a block.
They must appear at the same nesting level, and any variables
declared after VA_OPEN go out of scope at VA_CLOSE. Unfortunately,
with a K+R compiler, that includes the argument list.
VA_FIXEDARG sequence. Also, VA_OPEN and VA_CLOSE are the beginning
and end of a block. They must appear at the same nesting level,
and any variables declared after VA_OPEN go out of scope at
VA_CLOSE. Unfortunately, with a K+R compiler, that includes the
argument list. You can have multiple instances of VA_OPEN/VA_CLOSE
pairs in a single function in case you need to traverse the
argument list more than once.
For ease of writing code which uses GCC extensions but needs to be
portable to other compilers, we provide the GCC_VERSION macro that
...
...
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