Re: private routines
> His example's procedure only has scope with in the function
> in other words private outside of his function
> That would be a benifit.
Like I said, in my first respond. The need for such tight scoping rules is only
due to not-so-great scoping rules currently.
You shouldn't have libraries this big, complex and conflicting anyway. The
second includes are modularized, the scope advantage
can be achieved by using the much more clean approach of includes. (moduralized:
each include file is its own independent
identity. In other words, there should be no way to 'add' or 'remove' things
into the scope from anywhere else except from the
file and the files it directly includes.)
Ralf
|
Not Categorized, Please Help
|
|
