Can someone explain the scope/linkage differences between the following 4
global declarations and when one should be used (theoretically) over the
rest?
sample.h
---------
#ifndef SAMPLE_H
#define SAMPLE_H
int a;
const int b;
static int c;
extern int d;
#endif
---------
And if I gave 'd' an initial value, what the consequences would be (if any)? 7 2574
Method Man wrote: Can someone explain the scope/linkage differences between the following 4 global declarations and when one should be used (theoretically) over the rest?
sample.h --------- #ifndef SAMPLE_H #define SAMPLE_H
int a;
Reserve sizeof(int) bytes for a in the uninitialized variables section,
that at program startup will be set to zero. This definition will be
used *unless* some other definition appears like:
int a = 78;
If the second definition appears anywhere in the program, it will be
used instead of this one.
const int b;
Same as previously but now b can't be assigned to. static int c;
Same as the first definition but the name "c" will not be visible
in other modules of the program. extern int d;
This integer variable is defined somewhere else as an external, and
is used in this module. And if I gave 'd' an initial value, what the consequences would be (if any)?
int a = 78;
Reserve sizeof(int) byte in the data section and fill it with the bit
pattern 78. This is definitive, no other definition can follow.
const int b = 78;
Same as above but the value of b can't be changed.
Some compilers will optimize:
static const int b = 78;
so that all references of this "variabl" will be replaced with 78.
static int c=78;
Same as the first one except that the name is not visible elsewhere.
extern int d = 78;
This is equivalent to the first definition, int d = 78;
Method Man wrote: Can someone explain the scope/linkage differences between the following 4 global declarations and when one should be used (theoretically) over the rest?
sample.h --------- #ifndef SAMPLE_H #define SAMPLE_H
int a; const int b; static int c; extern int d;
#endif ---------
d is the only one of those declarations that belongs in a header file.
d should also be declared in one of the C files in the C program,
like sample.c.
Having static c in the header file,
defeats the whole point of the static keyword.
Every C file which #includes sample.h,
will have it's own a, b and c, that the other C files don't know about.
And if I gave 'd' an initial value, what the consequences would be (if any)?
If you did that, then you wouldn't be able to declare d
in a C file which #included sample.h.
--
pete
Groovy hepcat Method Man was jivin' on Sun, 10 Oct 2004 02:02:09 -0400
in comp.lang.c.
Global variable declaration in headers's a cool scene! Dig it! Can someone explain the scope/linkage differences between the following 4 global declarations and when one should be used (theoretically) over the rest?
sample.h --------- #ifndef SAMPLE_H #define SAMPLE_H
int a;
File scope and external linkage.
const int b;
File scope and external linkage.
static int c;
File scope and internal linkage.
extern int d;
File scope and external linkage.
#endif ---------
And if I gave 'd' an initial value, what the consequences would be (if any)?
It would become a definition. Definitions are bad in a header.
Headers should contain declarations, not definitions.
--
Dig the even newer still, yet more improved, sig! http://alphalink.com.au/~phaywood/
"Ain't I'm a dog?" - Ronny Self, Ain't I'm a Dog, written by G. Sherry & W. Walker.
I know it's not "technically correct" English; but since when was rock & roll "technically correct"?
Hiho,
pete wrote: Method Man wrote:
[snip header-file]static int c;
[snip] Having static c in the header file, defeats the whole point of the static keyword.
Not necessarily. You can for example use a header for
testing/extended error state returns and so on and count
the number of errors encountered/store error states and
so on. In order to make sure that the translation units
or modules do not get confused, you use static variables.
I have seen similar mechanisms in large code.
However, if possible I'd rather make do without as it
certainly does not enhance clarity...
Cheers
Michael
Michael Mair wrote: Hiho,
pete wrote: Method Man wrote: > [snip header-file]static int c; >
[snip] Having static c in the header file, defeats the whole point of the static keyword.
Not necessarily. You can for example use a header for testing/extended error state returns and so on and count the number of errors encountered/store error states and so on. In order to make sure that the translation units or modules do not get confused, you use static variables. I have seen similar mechanisms in large code.
I don't understand how that header file is used, and how there
would be a benefit from having a static object declaration in it.
What would a program that used it, be like?
Which C files would include it, in a program?
How many C files would there be in a program which used it.
--
pete
Hi pete,
sorry for getting back to you only now (busy today, so answers
which require much thought take longer)
pete wrote: Michael Mair wrote:
Hiho,
pete wrote: [snip]
Having static c in the header file, defeats the whole point of the static keyword. Not necessarily. You can for example use a header for testing/extended error state returns and so on and count the number of errors encountered/store error states and so on. In order to make sure that the translation units or modules do not get confused, you use static variables. I have seen similar mechanisms in large code.
I don't understand how that header file is used, and how there would be a benefit from having a static object declaration in it.
As I said in the snipped part, I do not think it is a good
technique. I do no longer have access to the code but an
untested sample header file could look like that:
#ifndef CATCH_ERROR
#define CATCH_ERROR
#include <stddef.h> /* for size_t */
/* error states */
enum ce_errortypes {
CE_OK=0,
CE_INVALID_INPUT,
/* Easy checks ^ */
CE_START_BAD_ERRORS,
/* Bad Errors v */
CE_INVALID_OP,
CE_INVALID_RANGE,
CE_END
};
static unsigned long int ce_statecounters[(size_t)CE_END+1];
#ifdef COUNT_ERRORS
# define RETURN(ret_int) \
{ ce_statecounters[( (ret_int) >= 0 && (ret_int)< CE_END \
&& (int)(ret_int)==(ret_int) ) \
? (int)(ret_int) : CE_END] += 1; \
return (ret_int);}
#else
# define RETURN(ret_int) return (ret_int);
#endif
#define HOW_MANY_CHECK_ERRORS(num) {enum ce_errortypes counter;\
(num) = 0; for(counter=1;counter<CE_START_BAD_ERRORS;\
counter++) {(num) += ce_statecounters[counter];}}
#define HOW_MANY_BAD_ERRORS(num) {enum ce_errortypes counter;\
(num) = CE_START_BAD_ERRORS+1; for(counter=1;\
counter<CE_END;counter++)\
{(num) += ce_statecounters[counter];}}
#define HOW_MANY_STRANGE_ERRORS(num) (num) = ce_statecounters[CE_END]
#endif
It is right now only for (non-negative) int returns but I did
not bother wo write more tests and mapping and so on.
The functions return 0/CE_OK on success and you do
if (ret=fun1(....))
RETURN(..appropriate error value..);
You just include the header for the files you want to test and use
RETURN instead of return.
In your test routine or somewhere else you just find out
about the types of encountered errors by using HOW_MANY_..._ERRORS
It can come in handy for simulation software where you do not
necessarily have convergence in every step; so you just count the
"not converged" errors and decide based on that number whether
the result is acceptable or whether you suspect that the result
and the repercussions if wrong might get your customers to want
you to pay for the damage...
You make ce_statecounters static because you only want to count
it per file.
What would a program that used it, be like?
Ugly. I think this is answered above.
Which C files would include it, in a program?
Those which need this kind of treatment?
I am not trying to be evasive but I am not sure what you want to
know. In the example with the simulation software, typically
the high level solver routines and the matrix assembly would use
that kind of stuff.
How many C files would there be in a program which used it.
42.
Honestly, are you kidding?
--Michael
Michael Mair wrote: Hi pete,
sorry for getting back to you only now (busy today, so answers which require much thought take longer)
pete wrote: Michael Mair wrote:
Hiho,
pete wrote: [snip]
Having static c in the header file, defeats the whole point of the static keyword.
Not necessarily. You can for example use a header for testing/extended error state returns and so on and count the number of errors encountered/store error states and so on. In order to make sure that the translation units or modules do not get confused, you use static variables. I have seen similar mechanisms in large code.
You make ce_statecounters static because you only want to count it per file.
Thank you.
--
pete This thread has been closed and replies have been disabled. Please start a new discussion. Similar topics
by: A |
last post by:
Hi,
Consider this code:
//Header File - Foo.h
int i = 0; // non-static global variable
class Foo{
...
|
by: Eric Lilja |
last post by:
Hello, I have a few global variables in my program. One of them holds the
name of the application and it's defined in a header file globals.hpp (and
the point of definition also happen to be the...
|
by: Thomas Matthews |
last post by:
Hi,
I'm getting linking errors when I declare a variable in the
global scope, but not inside a function. The declarations
are the same (only the names have been changed...).
class Book
{...
|
by: rick |
last post by:
Noob problem. I prefer to keep all my scripts in an external '.js' file.
I am currently loading the external '.js' file from the header. Problem is I
would like to declare
a global variable in the...
|
by: Michael |
last post by:
Hi newsgroup,
as the subject indicates I am looking for an advice
using global variables. I am not if this problem is more
about style then C. If its wrong in thi group, sorry.
So I have a...
|
by: fabio |
last post by:
Why? i' ve heard about this, the usage of global vars instead of
locals is discouraged, but why?
thx :)
|
by: Roman Ziak |
last post by:
Hello,
there were times when I used to be looking for a way to access
JavaScript Global object similar to those found in VBScript or PHP
($GLOBALS). At present this has only academic value for...
|
by: the_init |
last post by:
Hi friends,
Can you please explain me why the following code prints 10, instead of
20 - Here I am little confused with the static and global declaration
of i in the same program.
...
|
by: istillshine |
last post by:
When I control if I print messages, I usually use a global variable
"int silent". When I set "-silent" flag in my command line
parameters, I set silent = 1 in my main.c.
I have many functions...
|
by: emmanuelkatto |
last post by:
Hi All, I am Emmanuel katto from Uganda. I want to ask what challenges you've faced while migrating a website to cloud.
Please let me know.
Thanks!
Emmanuel
|
by: BarryA |
last post by:
What are the essential steps and strategies outlined in the Data Structures and Algorithms (DSA) roadmap for aspiring data scientists? How can individuals effectively utilize this roadmap to progress...
|
by: nemocccc |
last post by:
hello, everyone, I want to develop a software for my android phone for daily needs, any suggestions?
|
by: Sonnysonu |
last post by:
This is the data of csv file
1 2 3
1 2 3
1 2 3
1 2 3
2 3
2 3
3
the lengths should be different i have to store the data by column-wise with in the specific length.
suppose the i have to...
|
by: Hystou |
last post by:
There are some requirements for setting up RAID:
1. The motherboard and BIOS support RAID configuration.
2. The motherboard has 2 or more available SATA protocol SSD/HDD slots (including MSATA, M.2...
|
by: Hystou |
last post by:
Most computers default to English, but sometimes we require a different language, especially when relocating. Forgot to request a specific language before your computer shipped? No problem! You can...
|
by: Oralloy |
last post by:
Hello folks,
I am unable to find appropriate documentation on the type promotion of bit-fields when using the generalised comparison operator "<=>".
The problem is that using the GNU compilers,...
|
by: jinu1996 |
last post by:
In today's digital age, having a compelling online presence is paramount for businesses aiming to thrive in a competitive landscape. At the heart of this digital strategy lies an intricately woven...
|
by: agi2029 |
last post by:
Let's talk about the concept of autonomous AI software engineers and no-code agents. These AIs are designed to manage the entire lifecycle of a software development project—planning, coding, testing,...
| |