error unexpected assignment statement in module at (1)

Unexpected assignment statement in module?

Daniel Carrera

Erik Toussaint

James Van Buskirk

> integer, parameter :: p = pref > real(p) :: ck_a(6,6) = reshape( (/ & > 0.0_p , 0.0_p , 0.0_p , 0.0_p , 0.0_p , > 0.0_p , & > 1.0_p/5 , 0.0_p , 0.0_p , 0.0_p , 0.0_p , > 0.0_p , & > 3.0_p/40, 9.0_p/40 , 0.0_p , 0.0_p , 0.0_p , > 0.0_p , & > 3.0_p/10, -9.0_p/10 , 6.0_p/5 , 0.0_p , 0.0_p , > 0.0_p , & > -11.0_p/54, 5.0_p/2 , -70.0_p/27 , 35.0_p/27 , 0.0_p , > 0.0_p , & > 7.0_p/8 , 1631.0_p/55296, 175.0_p/512, 575.0_p/13824, > 44275.0_p/110592, 253.0_p/4096 & > /), (/ 6, 6 /) )

integer, parameter :: p = pref

Richard Maine

> On 04/30/2011 04:28 PM, Erik Toussaint wrote: > > It is not allowed to have executable statements by themselves in a > > module. They need to be inside a procedure, or in the main program. > > Hmm... I need some module constants that are shared by several > procedures. That's why I had those variables in the module directly.

> Hmm... It looks like I can still assign a value in the variable declaration: > > real(pref) :: foo = 3

Note that is not an assignment statement. It is an initialization. It doesn't require execution to happen. Instead, it defines the value of the variable when the program starts. -- Richard Maine | Good judgment comes from experience; email: last name at domain . net | experience comes from bad judgment. domain: summertriangle | -- Mark Twain

module ode use types implicit none real(pref) :: ck_c(6), ck_b4(6), ck_b5(6), ck_a(6,6)

contains subroutine init

ck_c = (/ 0, 1/5, 3/10, 3/5, 1, 7/8 /) ck_b5 = (/ 37/378, 0, 250/621, 125/594, 0, 512/1771 /)

Tobias Burnus

> reshape( [ real(p) :: 0, 0, 0, 1.0_p/5.0_p, 0, 0, ... ], [6,6]) > > The "real(p) :: " makes sure that the constructed array has that type; I > think it is required if elements have different types.

(I think I counted the blanks right, but no guarantee). In f90/f95, the need for careful blank counting deterred me from using character array constructors most of the time.

> The "real(p) :: " makes sure that the constructed array has that type; I > think it is required if elements have different types. You still need to > add the _p for, e.g. 1.0_p/5.0_p as you might loose digits when you use > "1.0/5.0" - or more obviously "1/5" (= 0).

Ok. Thanks.

Ron Shepard

> Well, you could write: > > reshape( [ real(p) :: 0, 0, 0, 1.0_p/5.0_p, 0, 0, ... ], [6,6]) > > The "real(p) :: " makes sure that the constructed array has that type; I > think it is required if elements have different types. You still need to > add the _p for, e.g. 1.0_p/5.0_p as you might loose digits when you use > "1.0/5.0" - or more obviously "1/5" (= 0).

real(p) :: ck_a(6,6) = reshape( (/ &

(/ 6, 6 /) )

$.02 -Ron Shepard

ck_a(6,6) = reshape( [ real(p) :: 0_p, 1.0_p, 1.5555555555_p, 1.0_p/5.0_p, ... ], [6,6])

>> add the _p for, e.g. 1.0_p/5.0_p as you might loose digits when you use >> "1.0/5.0" - or more obviously "1/5" (= 0). > > Is this true? This is something that has been confusing me for a while. > > While the standard doesn't specify it, the default for real literal > constants on most compilers is single precision.

> >> Is there any way to avoid adding ".0_p" on every single element of the > >> array?

As mentioned above, I more than half suspect it was just a typo, but it still seems like an opportunity for making that point.

glen herrmannsfeldt

> Another suggestion in these situations is to use the shape() > intrinsic to avoid having to specify the dimensions twice. That is, > instead of > real(p) :: ck_a(6,6) = reshape( (/ & > ..., > (/ 6, 6 /) ) > you can have > real(p) :: ck_a(6,6) = reshape( (/ & > ..., > shape(ck_a) ) > Is isn't obvious that this should work, since the dimensions are > declared in the same statement that they are used, but fortunately > things were defined so that it does. In the future, if you ever > need to change the dimensions to, say (6,7), then you would only > need to change that in one place (in addition to adding the new > column of numbers, of course).

> On 4/30/2011 1:12 PM, Daniel Carrera wrote: > > On 04/30/2011 07:47 PM, Richard Maine wrote: > >> So when you write 0_p, that's just like writing 0_8, which has nothing > >> in particular to do with reals. That's just a kind of integer. It might > >> plausibly be a 64-bit integer, or it might be an invalid integer kind. > >> But it certainly is not a real. > > > > I think that's evil.

> How could the syntax possibly be anything else and let one specify > differing KINDs of INTEGERs as well as REALs????????????????

Too late for that one also, as pretty much everyone uses kind value sets that are not disjoint. And far too many people write code that depends on specific kind numbers. That one would not technicaly invalidate any code that was already standard conforming and portable. But it would invalidate an awful lot of code, and it just would not fly. Not even worth seriously proposing.

> Nothing said or implied about good, bad, evil or indifferent as far as > the choice made/adopted, only how the expression has to be interpreted > given what was the adopted syntax.

Oh, sorry. I misunderstood. I was talking about dreams about how things might have been rather than about how things are.

> Fortran has this unfortunate historical baggage of making darn near > everything into integers, even when their current usage has nothing to

>> Compilers could fix this by not reusing any KIND between different >> types, except between REAL and COMPLEX, as required by the standard. >> > > That sounds like a good feature. Even something that I might dream some > day could make its way into the standard.

> Or even if kind values were integers, one could have required that the > kind values for integers and for reals be disjoint sets. The standard > already requires that the compiler be able to diagnose using invalid > kind values, which would apply.

> Too late for that one also, as pretty much everyone uses kind value sets > that are not disjoint. And far too many people write code that depends > on specific kind numbers. That one would not technicaly invalidate any > code that was already standard conforming and portable. But it would > invalidate an awful lot of code, and it just would not fly. Not even > worth seriously proposing.

It would make a nice compiler switch, though. Probably would have to make kind numbers for integer and logical types of the same size the same because there doesn't seem to be a selected_logical_kind intrinsic. Also the switch should guarantee that CHARACTER(C_CHAR) doesn't yield a length-1 string, a sore point for me. Being disjoint from previous values would be nice, too, allowing diagnosis of unportable constructions such as INTEGER(4) MY_HANDLE.

> "Richard Maine" <[email protected]> wrote in message > news:1k0jbxf.1o4vo9hh8rmqN%[email protected]... > > > Or even if kind values were integers, one could have required that the > > kind values for integers and for reals be disjoint sets.

> > But it would > > invalidate an awful lot of code, and it just would not fly. Not even > > worth seriously proposing. > > It would make a nice compiler switch, though.

True. I was referring to it not having a chance at flight in the standard. There already exist compilers with switches to change kind numbering schemes, so it doesn't seem implausible there.

Steve Lionel

> Hmm... I need some module constants that are shared by several > procedures. That's why I had those variables in the module directly.

Refer to http://software.intel.com/en-us/articles/optimization-notice for more information regarding performance and optimization choices in Intel software products.

> > [...] You still need to

> > add the _p for, e.g. 1.0_p/5.0_p as you might loose digits when you use > > "1.0/5.0" - or more obviously "1/5" (= 0). >

Nonetheless I still learned something, so once again thanks for your answers (and patience).

Nope, wasn't me (I even double checked to make sure my memory doesn't fail me). Thanks for your answer though.

Cheers, Daniel.

Unclassifiable statement error with a function that seems fine

this is the code

wrong function call name… im so stupid

now its this and im confused

You are missing a contains statement.

I have forgotten the contains statement many times. Since beginners may also do this, a clear message would be good. For

I think the error message would ideally be something like

module procedure hello defined before contains statement

since that clarifies what needs to be done. For the code shown,

lfortran -c says

gfortran -c says

ifort -c says

Related Topics

Navigation Menu

Search code, repositories, users, issues, pull requests..., provide feedback.

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly.

To see all available qualifiers, see our documentation .

• Notifications

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement . We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cannot compile module.f90 with gfortran #1

Beliavsky commented Jul 3, 2021

• 😕 1 reaction

No branches or pull requests

eslint (no-console) Unexpected console statement [Solved]

Last updated: Mar 7, 2024 Reading time · 4 min

# Table of Contents

• eslint (no-console) Unexpected console statement
• Disable the no-console rule for a single line
• Disable the no-console rule for multiple lines
• Disable the no-console rule for an entire file
• Disabling the no-console rule in your package.json file

# eslint (no-console) Unexpected console statement

The ESLint error "eslint (no-console) Unexpected console statement" is shown when you use methods on the console object, e.g. console.log() .

To resolve the issue, set the no-console rule to off in your .eslintrc.js file to disable the rule.

Create a .eslintrc.js file if you don't already have one.

The file should be located in the root directory of your project, right next to your package.json file.

Add the following rule to the rules object in your .eslintrc.js file to disable the no-console rule.

In some cases, you might want to enable the no-console rule only in production but disable it in development and during testing.

The code sample uses the value of the process.env.NODE_ENV environment variable to determine whether the no-console rule should be disabled or enabled.

The ternary operator is very similar to an if/else statement.

In other words, if the process.env.NODE_ENV variable is set to production , then the no-console rule is set to error , otherwise, it is set to off .

You can also specify which methods on the console object you want to allow.

The allow array is used to allow using the specified methods on the console object.

By default, the rule is set to warn , so a warning is shown for any method on the console object that is not in the allow array.

If you use a .eslintrc.json configuration file, make sure to double-quote all keys and values.

Notice that there shouldn't be any trailing commas when writing JSON.

The ESLint no-console rule shows a warning or an error when you use methods on the console object, e.g.:

• console.log('your message')
• console.warn('your warning')
• console.error('an error occurred') .

The rule is used because these messages are used for debugging purposes and should not be shipped with your code in production.

# Disable the no-console rule for a single line

If you only want to disable the no-console rule for a single line, use the following comment.

As noted, the comment only applies to the next line so if you use console.log() multiple times, you'd have to repeat the comment.

If you want to disable the no-console rule for the current line, use the following inline comment.

However, using an inline comment is usually less readable than placing the comment above the console.log() call.

This might also cause another warning if your line exceeds a certain length.

# Disable the no-console rule for multiple lines

You can also use a comment if you need to disable the no-console rule for multiple lines.

The first comment starts the block in which the no-console ESLint rule is disabled and the second comment ends the block.

So if you have a console.log() call after the second comment, the warning is shown.

# Disable the no-console rule for an entire file

If you need to disable the ESLint no-console rule for an entire file, add the following comment to the top of your file.

No matter how many times you use the console.log() method after using the comment, no warnings are shown.

However, note that the comment has to be added at the top of your file before any calls to console.log() .

# Disabling the no-console rule in your package.json file

You can also disable the no-console rule in your package.json file if that's where you manage your ESLint configuration.

The package.json file is located in the root directory of your project.

However, note that ESLint won't look at the contents of your package.json file if your project contains a .eslintrc.js or .eslintrc.json file.

# Additional Resources

You can learn more about the related topics by checking out the following tutorials:

• [eslint] Delete CR eslint(prettier/prettier) issue
• React ESLint Error: X is missing in props validation
• eslint is not recognized as an internal or external command
• Plugin "react" was conflicted between package.json » eslint-config-react-app
• React: Unexpected use of 'X' no-restricted-globals in ESLint
• TypeScript ESLint: Unsafe assignment of an any value [Fix]
• ESLint: Expected property shorthand object-shorthand [Fixed]
• 'X' should be listed in the project's dependencies, not devDependencies
• ESLint: How to ignore the node_modules or dist/ directory
• ESLint: Unexpected lexical declaration in case block [Fixed]
• ESLint error Unary operator '++' used no-plusplus [Solved]
• ESLint Prefer default export import/prefer-default-export
• Assignment to property of function parameter no-param-reassign
• Expected parentheses around arrow function argument arrow-parens
• Arrow function should not return assignment. eslint no-return-assign
• Unexpected await inside a loop.eslint no-await-in-loop
• Import in body of module reorder to top eslint import/first
• ESLint: disable multiple rules or a rule for multiple lines
• Missing return type on function TypeScript ESLint error

Borislav Hadzhiev

Web Developer

Copyright © 2024 Borislav Hadzhiev

module - 模块中的意外赋值语句

标签 module fortran

Error: Unexpected assignment statement in MODULE

关于module - 模块中的意外赋值语句，我们在Stack Overflow上找到一个类似的问题： https://stackoverflow.com/questions/45086892/

上一篇： haskell - where block 的语法

下一篇： xcode4 - 在服务器中验证 mac 应用商店收据.

fortran - Fortran程序中的堆栈溢出

c - 如何将动态分配的数组传递给子例程

python - Python 中的动态导入

objective-c - swift 。无法构建 Objective-C 模块

perl - 当我使用模块时如何找到 Perl 加载的文件？

python - 如何使用 importlib.import_module 在 Python 中导入模块

从 Fortran 调用带有 **int 参数的 C 函数

c - 如何在 Fortran 中绑定(bind) C 的 char** 参数？

python - f2py 和 gfortran : undefined reference to `main' 编译错误

©2024 IT工具网   联系我们

• | New Account
• | Log In Remember [x]
• | Forgot Password Login: [x]
• Format For Printing
•  -  XML
•  -  Clone This Bug
•  -  Top of page

There was an error in evaluating the Pre-request Script: TypeError: Cannot read property 'shift' of undefined

I am new to Postman automation and facing some problem with running the test with different data set.

I am getting an error, “There was an error in evaluating the Pre-request Script: TypeError: Cannot read property ‘shift’ of undefined”

Pre-request script:

Appreciate your help if someone can tell me what’s wrong here?

Thanks in advance!

buyerProgramId is a defined array ? if so why is it inside if loop? Can you please explain a little bit more here, what’s your expectation? And what are you trying to Test? Also kindly place your scripts under ``` so that it will be easy to copy paste and work for…

Your if statement is evaluating to false, so buyerProgramId is never set. I’d recommend changing what you have so a slightly different version than what @bpricilla said.

This defaults your list of Ids to the hardcoded list, but if there is already a list defined in the globals, uses that instead.

In your test script, just modify it slightly:

Thanks @bpricilla for pointing that out. Actually, my task is to run the collection with a different dataset in each run(which is buyerProgramId in my case) until the size of the array.

So, I want to run the Postman test with 1st Iteration: 1961, 2nd Iteration: 1962, and so on.

I have now removed the array from the if condition. Now, I am no longer getting the above error but now, the request seems to be moving in an indefinite loop. It is always running the request with the buyerProgramId 1961 instead of picking other IDs in the array.

var Ids= pm.globals.get(‘buyerProgramId’) var buyerProgramId= [‘1961’, ‘1962’, ‘1972’, ‘1976’, ‘1977’];

if(!(Ids)){

var currentId= buyerProgramId.shift();

pm.globals.set(‘buyerProgramId’, buyerProgramId); pm.globals.set(‘currentId’,currentId) }

var Ids= pm.globals.get(“buyerProgramId”);

if(Ids && Ids.length>0){

postman.setNextRequest(‘Get Buyer Program Information by ID’);

Thanks @allenheltondev for your feedback. I tried with what you have suggested but still I am not able to iterarte through each and every ID in the buyerProgramId Array.

With your version, It’s picking up any 1 random buyerProgramId in the array and running the iteration only once.

I want to check the results with each and every buyerProgramId. Can you please help here?

let buyerProgramId= [‘1961’, ‘1962’, ‘1972’, ‘1976’, ‘1977’];

buyerProgramId= JSON.parse(pm.globals.get(‘buyerProgramId’))

catch(Exceptione){

let currentId= buyerProgramId.shift();

pm.globals.set(‘buyerProgramId’, JSON.stringify(buyerProgramId));

pm.globals.set(‘currentId’,currentId);

let Ids= JSON.parse(pm.globals.get(‘buyerProgramId’))

Are you running it in the collection runner? You have to do that if you want it to loop.

Running a single request manually will only ever run one request.

Yes, I am running it in collection runner. And the collection running is running the test for only 1 buyerProgramId in the array.

Does anything depend on this request name? Or, it could be any name?

@vdespa Can you please help here?

Check the answers here to figure out how to create a loop setNextRequest() doesn't work

You are calling Get Buyer Program Information by ID to perform the iteration, and if you are setting the buyerProgramId array either in this request or any request in between, the array will always be reset to its original state.

You need to structure your Collection in a way that the first request initializes your variables, and then the next requests are used for looping

I don’t think it’s resetting the array every time. It should be defaulting the array to the initial values, but then overwriting it with the value in the global variable.

I think where @vaibhav.sh.05 might be going wrong is the parameter he’s passing into postman.setNextRequest .

That value has to match the name of the request you want to run. If you want to make sure you loop back on the same request you are currently on, you could just do postman.setNextRequest(request.name)

Hi @amit thanks for your feedback.

I tried with your suggestion but still, the request is not picking up all the IDs I have given in the Array. It is running the request in collection runner for only the 1st ID i.e. ‘1961’.

var buyerProgramId= [‘1961’, ‘1962’, ‘1972’, ‘1976’, ‘1977’];

pm.globals.set(“buyerProgramId”, JSON.stringify(buyerProgramId));

var Ids = JSON.parse(pm.globals.get(“buyerProgramId”)); var nextId= Ids.pop(); pm.globals.set(“Ids”, JSON.stringify(Ids));

if(nextId == ‘1972’){

postman.setNextRequest(null);

postman.setNextRequest(nextId);

Can you check if I am doing anything wrong here?

I used request.name in the setNextRequest and it is still running into an indefinite loop with the 1st ID in the array

Ok your last message was telling of what was wrong.

Your prerequest script in fact is resetting the array every time.

This is where you want to do your array manipulation. You should be popping the array and saving the new contents here.

Then in your tests, you just need to evaluate if there are more items in the array

Thanks @allenheltondev . The array manipulation is now working in the way I wanted it to work. This is a perfect solution! Thanks for all your efforts and help.

Appreciate it! Cheers

Hi @vaibhav.sh.05 what is the body you used in request.name , wanted to check as i am running into error as well

Hi @vinay0010

I am not sure if I understand your question correctly. However, i am using setNextRequest to the same request as I wanted to loop in though all my buyer program IDs

Using this syntax: postman.setNextRequest(request.name)

And if you are talking about the data in body of postman request then I am not using any data in the body. I was getting the data by passing the path variable, id : {{currentId}}

where currentId I am getting from, let currentId = buyerProgramId.shift(); (from the pre script)

Hope this helps!

Best, Vaibhav Sharma

Hi @allan.helton I need help. Below you can see my code, the problem is very close to your answer. The difference is in array. I have generated an array of objects. It is big array and I should run the collection with a different dataset in each run until the size of the array. I have three properties in my array’s objects - "r_type", "r_target", "u_range" .

Pre-request script :

Test script :

How can I access to objects into array and use its properties as variables ?

I will be honest, this code is extremely hard to follow. I can’t figure out what its doing vs what you want it to do. Is there any way you could clarify, please?

Hi @allenheltondev , thanks for your feedback. First of all I have generated an array of objects. Then I need to iterate through each object into this array and use object’s properties as variable.

This is my array.

I have opened new topic in help category related to this question. Please, let me know if you need more information. Thanks in advance