Hi,

 ac> Yes, all global variables would end up in the one module, which I
 ac> think is an advantage over having them scattered everywhere.
One moment. I understand this in the following way:

static struct globalvars glob;

int foo()
{
     return glob.a;
}

int bar()
{
     return glob.b;
}

This works as long as the whole source code is in one module. Otherwise you
wouldn't have the same glob in two different modules. Then it's not global
and you don't need it at all. Or I don't understand what you mean with
"static". (module reads source file in C or is there some way to
change this, I'm not aware of)
 
 ac> I don't know about nify advantages, but it fits your requirement of
 ac> prefixing names of globals.
I had something more descriptive in mind. The prefix tells where the
functions comes from. In some sense object oriented. AreaOpen(),
AreaClose(), etc. (as example) do something with areas and come from
area.c. The prefix |--> file mapping isn't that important, but this
gives a good division of the source code. I hope you get my meaning.

Ciao
Meikel

--- timEd/FreeBSD 1.11.a5