Search results for query: *

The problem is that Fortran 90 Standard did not define clearly if locally declared allocatable arrays are deallocated automatically when they go out of scope. Only Fortran 95 Standard guarantees this feature explicitly.

Remark: As far as I know, automatic deallocations some kinds of local allocatable arrays was introduced in Fortran 95 and later...

PRIVATE attribute regulates visibility of names declared in MODULE scope. It does not relate to the life span of declared variables. All your allocatable arrays (and integer variables) are locals in its own subroutines. These names are not directly accessible out of subroutine scope(s). You...

The 3rd line of your output is: ... is 89 (please, look at your program output again;) It's a wrong way to get max row values: it does not work for negative values. Right way: #define N 3 int maxval; int a[N][N] = { ... ... for (i = 0; i < N; ++i) { maxval = a[i][0]; for (j = 1; j < N...

Try to close opened units (not only reopen them for another external files) then see what happens.

Please, look at the chaotic source text in OP. Post the program again, embed your source in code TGML tag (press help button on the posting panel for instruction).

What a pity!..

Visual (not Virtual) Fortran?.. As far as I know Compaq Visual Fortran was embedded to Visual Studio IDE. VS IDE Editor shows line numbers after that: Tools|Options|Text Editor|All Languages then Display/Line numbers check on... May be it helps...

Why you have used n before initialization? You allocate arrays with undefined n. Of course, your program crashed after that...

Some notes: 1. It's impossible to represent n! for n > 170 as a double value (170! ~ 7.25E306). All double n! values after 18! are factorial approximations only. 2. It's impossible to represent n! exactly for n > 20 as integer*8 value (20! = 2432902008176640000). It's not Fortran issue: it's...

If it's possible, try to pass your problem(s) to the personal expert(s); don't waste a time on forums ;) BTW, many years ago we solved 1-2-3GB data physical problems with 192K byte computer memory. Key words: proper algorithmes selection ;)

Dangerous code. You assign pointers to global variables, don't free (and never check) cleanbuffer allocation. You compare short buffer[iii] with pointer value NULL (why?). The last loop is exactly buffer and clearbuffer "assign zero to all elements" operation (think why - and look at the...

exit(1)... Probably, it's bedtime... Good luck!

Sorry, must be == NULL in my prev snipet ;(

Well, it seems you understand the problem ;) Your if (condition) is not stupid, it's incorrect expression example (see operator priorities in C). That's it in C language style (look at parenteses balance): if ((_buffer = malloc(elementos*sizeof(double))) != NULL) { /* no need for cast if you...

>I've heard that in this cases is better to change the programming language to other that deals better with dereferences. It sounds like after crash in the expression x/0.0 you want to switch to the programming language that deals better with divide by zero operations. Better look at the malloc...

There are three ways "to transfer the desired value from subroutine 2 into subroutine 1": 1. Use subroutine parameters... 2. ...or some kind of common storage (old-fashioned common blocks or modules in modern fortran)... 3. ...or external storage (write then read files). But you never transfer...

=> - lambda operator (C# 3.0). See: http://msdn.microsoft.com/en-us/library/bb397687.aspx <= - less or equal to operator. Simple and clear...

May be it helps: http://www.codeproject.com/Articles/14353/Creating-a-Basic-Windows-Service-in-C (don't worry, it's about Csharp, not C;)...

It sound like this: can you help me to assign value 2 to all constants 1 in my code? PARAMETER statements define symbolic names of CONSTANTS. Don't mix up PARAMETER defined names with routine parameters. Better present your codes where you are trying "making a new set a parameter equal to the...