The error code does not match the example error code

[WexeI]

Hello. I'm having problems with the examples

Code:

program main
  use ErrorInstanceModule
  use ErrorCriteriaModule
  implicit none

  type(ErrorCriteria) :: eh
  type(ErrorInstance) :: error
  call eh%init()
  error = eh%limit(3,0,2)
  call eh%trigger(error=error)
end program main

Expected results:

$ Error: Value must be between 0 and 2. Given value: 3.
$ ERROR STOP 105

Actual results:

←[91mError:←[0m Value must be between 0 and 2. Given value: 3.


ERROR STOP 1

What mean "←[91mError:←[0m" ?
I'm using fpm with gfortran on Windows

[samharrison7]

Thanks for the message. There are two issues here:

• The [91m are colour codes to make the "Error" text red. We recently changed how these are dealt with. Which version of the error handler are you using, and what terminal are you on? If you're on the latest commit in the develop branch, you shouldn't be getting those codes printed out (the text should be coloured instead). But if you're on an older version (including the tagged v1.0.4), it requires an extra compiler flag (-fbackslash for gfortran, /assume:bscc for ifort). I will tag a new release to clear up this issue.
• The error code doesn't match (it is always 1). This was changed a while back and I haven't got around to updating the docs yet. I think this was because using variables as error stop codes is not strictly supported by the standard and so not supported by all compilers. At some point I will update the code to print out the error code in the message (as opposed to the stop code).

Can you let me know if updated to the latest commit on the develop branch clears up the colour code issue, and if so I will tag a new release?

[WexeI]

Which version of the error handler are you using, and what terminal are you on

Thanks for the answer. I found problem. The problem appear when I use cmd, but there are no problems with this:
https://stackoverflow.com/questions/2048509/how-to-echo-with-different-colors-in-the-windows-command-line

With git bash it works fine
(lastest error handler version from develop branch).

I haven't got around to updating the docs yet.

Oh, good. I thought I was doing something wrong