[f2py] Protected memory in shared fortran libs?

[Louis Wicker]

All:

Supposed I have a shared fortran lib which allocates an array, call it  
U()

I have a python application which loads a shared lib that has the "U" -  
it allocates it, inits it, maybe writes it to a file.

Now, from that python application I want to spawn another job (e.g.,  
via the 'os.system()' command)

which starts another python job that loads the SAME shared library,  
creates memory, reads data into U(),

does calculations on it, etc.

So the shared lib is loaded into two programs at once.  I assume that  
the multiple "invocations" of loading that module creates two
separate regions of memory, correct?

I am getting strange behavior with this type of system - but I am  
pretty sure its my problem, not this.  But I would thought I would ask  
since
I cannot seem to track the problem.

Lou

------------------------------------------------------------------------ 
----
|  Dr. Louis J. Wicker
|  Research Scientist, National Severe Storms Lab
| 1313 Halley Cir, Norman, OK 73069
| E-mail:   Louis.Wicker at noaa.gov
| HTTP:  www.nssl.noaa.gov/~lwicker
| Phone:    (405) 366-0416
| Fax:       (405) 366-0472
|
------------------------------------------------------------------------ 
----
|
| "The contents  of this message are mine personally and
| do not reflect any position of  the Government or NOAA."
|
------------------------------------------------------------------------ 
----