Prev: VB6 disks
Next: Quick Graphic Question
From: dpb on 9 Mar 2010 16:08
Is there an issue in moving to VB - net/Fred/whatever from Classic in
array storage order or is it still column-major? That is, switching to
match C as opposed to Fortran convention didn't happen, too, did it
along w/ the other C/Java-like things?

Query came up in Fortran language group (c.l.f) wrt to using VB GUI
frontend. I realized I'm not absolutely sure, so before I respond
thought I'd check with those who are bound to know...

Actually, I did respond to the OP w/ the consistency of a major
advantage of VB in conjunction w/ Fortran DLLs and another respondent
asked if was still so which is where I had the "uhhhh, ya' know, I'm not
completely sure" reaction.

--
From: Nobody on 9 Mar 2010 16:51
"dpb" <none(a)non.net> wrote in message
news:hn6df4$eta$1(a)news.eternal-september.org...
> Is there an issue in moving to VB - net/Fred/whatever from Classic

Try asking here instead:

news://msnews.microsoft.com/microsoft.public.dotnet.languages.vb


From: Karl E. Peterson on 9 Mar 2010 18:36
dpb wrote:
> Is there an issue in moving to VB - net/Fred/whatever from Classic in array
> storage order or is it still column-major? That is, switching to match C as
> opposed to Fortran convention didn't happen, too, did it along w/ the other
> C/Java-like things?
>
> Query came up in Fortran language group (c.l.f) wrt to using VB GUI frontend.
> I realized I'm not absolutely sure, so before I respond thought I'd check
> with those who are bound to know...
>
> Actually, I did respond to the OP w/ the consistency of a major advantage of
> VB in conjunction w/ Fortran DLLs and another respondent asked if was still
> so which is where I had the "uhhhh, ya' know, I'm not completely sure"
> reaction.

Given all variables are objects, there may not *be* an answer. <G>
He11, this is just the sort of confusion they invite by removing the
language that one extra step away from the hardware. I think the
correct answer is, "Bad boy! You're not supposed to be doing that!"

--
..NET: It's About Trust!
http://vfred.mvps.org


From: Paul Clement on 10 Mar 2010 08:41
On Tue, 09 Mar 2010 15:08:31 -0600, dpb <none(a)non.net> wrote:

� Is there an issue in moving to VB - net/Fred/whatever from Classic in
� array storage order or is it still column-major? That is, switching to
� match C as opposed to Fortran convention didn't happen, too, did it
� along w/ the other C/Java-like things?
�
� Query came up in Fortran language group (c.l.f) wrt to using VB GUI
� frontend. I realized I'm not absolutely sure, so before I respond
� thought I'd check with those who are bound to know...
�
� Actually, I did respond to the OP w/ the consistency of a major
� advantage of VB in conjunction w/ Fortran DLLs and another respondent
� asked if was still so which is where I had the "uhhhh, ya' know, I'm not
� completely sure" reaction.

I believe that .NET (System.Array) implements the ECMA-335 standard (CLI) which is row major.


Paul
~~~~
Microsoft MVP (Visual Basic)
From: dpb on 10 Mar 2010 09:00
Paul Clement wrote:
....

> I believe that .NET (System.Array) implements the ECMA-335 standard
> (CLI) which is row major.

I did some searching and it does appear so, sadly for the purpose. :(

What also appears to make it even more of a pita for mixed language
programming is that apparently neither Option Base nor individual arrays
can be referenced from anything other than 0-based indices automagically.

The ease of VB as a frontend GUI engine to Fortran DLLs has taken a
major hit afaict. :(

--
 | 
Pages: 1
Prev: VB6 disks
Next: Quick Graphic Question