Hello again,
On Tue, Jun 19, 2018 at 4:31 PM Brad Chamberlain <[email protected]> wrote:
First, note that you're pointing to the 1.14 version of the documentation
> but probably want to be looking at the current (1.17) version. I'm
> guessing you got there through a Google search. We've been working to
>
Yes, that is what happened. Thanks for calling my attention to it.
values. Coming from Fortran (and looking at the example on the
>
Like you, I'm not a Fortran programmer. My interest in Chapel is in (large)
part motivated by a desire to avoid Fortran as much as possible. My
experience as a programmer is in C, SQL, Java, Perl, Python, and a
hand-full of other languages that have since fallen out of favor.
allocatable arrays page you pointed to), you're much more likely to want
> to use Chapel's rectangular domains and arrays which are described here:
>
> https://chapel-lang.org/docs/primers/arrays.html
OK, yes, I did read up on rectangular arrays before asking this. The
trouble I was having in the Fortran90 was scads (hundreds) of ALLOCATABLE
arrays being declared everywhere, without the array bounds (or domains,
apart from the mathematical concept of "all positive natural numbers" )
being known at the declaration point. I imagine it is possible to know them
much later in the code, but I haven't gotten there yet (also, being an
absolute novice at this, I was trying to keep my translation as *1:1* as
possible, to avoid confusion when referring to the Fortran90 in the future,
which is still under active development).
Third, if you're a Stack Overflow user, questions like this are great to
> post there so that they'll help others in the future as well. Gitter is
> another place that short questions can be asked if you prefer a chat
> format.
>
OK. I have used Stack Overflow as reader before, but not as a poster. I'll
do that.
OK, now to your specific question about allocatable arrays: Chapel's
> arrays are _very_ dynamically allocatable (and reallocatable). There are
> a few ways you can approach this (and the primer above may be more useful
> than my terse response here):
>
Thanks very much for the (not terse!) explanation.
Andy
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Chapel-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/chapel-users
