Re: passing a variable number of args/vectors to a routine
- From: Mirko.Vukovic@xxxxxxxxx
- Date: Wed, 30 Jan 2008 16:57:26 -0800 (PST)
On Jan 30, 6:07 pm, dpb <n...@xxxxxxx> wrote:
Mirko.Vuko...@xxxxxxxxx wrote:
...
I pass the data to the TecPlot dump routine by calling:
call dump_data( vData1,vData2, ...)
That's not the question -- where do vDataN come from and why can't they
be an ALLOCATED array of the proper dimension, instead?
--
Hmm, I am not sure what you're getting at. But here's my story:
I am doing a 1-D time-dependent electromagnetic simulation and
calculate E and B fields. These are stored in their own vectors.
After each time step, I want to pass the two vectors to the tecplot
dump routine. So, I do allocate the two vectors at the beginning of
the run.
But I want to write the tecplot dump routine because eventually, I
will be following more variables than that, and I will be passing it
more vectors.
Hope this clarifies things a bit.
Thanks,
Mirko
.
- Follow-Ups:
- References:
- passing a variable number of args/vectors to a routine
- From: Mirko . Vukovic
- Re: passing a variable number of args/vectors to a routine
- From: dpb
- Re: passing a variable number of args/vectors to a routine
- From: Mirko . Vukovic
- Re: passing a variable number of args/vectors to a routine
- From: dpb
- passing a variable number of args/vectors to a routine
- Prev by Date: Re: IVF + Xp (32bit) = 3Gb
- Next by Date: Re: IVF + Xp (32bit) = 3Gb
- Previous by thread: Re: passing a variable number of args/vectors to a routine
- Next by thread: Re: passing a variable number of args/vectors to a routine
- Index(es):