[wopox3]

So I noticed this.
This code is compiled without problems:
FlDamage ? (Float: flDamage) : 0.0

But, if we remove the brackets, then we get a compilation error.


And, could you remove the output that is highlighted in red on the output? This also hinders.

[klippy]

Originally Posted by wopox3 So I noticed this. This code is compiled without problems: FlDamage ? (Float: flDamage) : 0.0 But, if we remove the brackets, then we get a compilation error. ...

Just as I thought, parenthesis are required. Maybe I can make a regex that will take that into account, but I'm not sure.

Originally Posted by wopox3 And, could you remove the output that is highlighted in red on the output? This also hinders.

Yes, I agree. This should be a setting though. I think I'll be working more with the compiler output in the next version.
However, should the displayed path be relative to workspace maybe? What if there's no workspace open? I'm looking for a detailed explanation of how it should be displayed.

[wopox3]

If there is a working folder - hide the path.
Otherwise - show the full path. Although ... it does not matter.
Simple setting in the disclosure of this information globally - will be enough for everyone.

[wopox3]

The parser still doesn't parse #define statements, but it's on TODO. Didn't plan for that hovering thing, but it seems good as well, will try to do it in the future.

In theory, it should work for: const, #define, enum.

[voed]

Originally Posted by KliPPy Just as I thought, parenthesis are required. Maybe I can make a regex that However, should the displayed path be relative to workspace maybe? What if there's no workspace open? I'm looking for a detailed explanation of how it should be displayed.

Maybe just like this:

Compiling C:/path/to/sma/filename.sma
AMX Mod X Compiler 1.8.3-dev+5074
Copyright (c) 1997-2006 ITB CompuPhase // maybe we can remove copyrights?
Copyright (c) 2004-2013 AMX Mod X Team
Line 17 : warning 224: indeterminate array size in "sizeof" expression (symbol "")
...

File name to head of output, and in body just print line name and warning

[kristi]

How to make this match exact words? For example, it would only show up if there was a variable named 'else_whatever'.

[klippy]

Originally Posted by kristi How to make this match exact words? For example, it would only show up if there was a variable named 'else_whatever'.

That's VSCode's fuzzy search that picks up almost every word in the file, it's not something my extension is outputting.
There is a setting 'editor.wordBasedSuggestions' which controls that, take a look at the Settings pane.

[klippy]

0.5.0 has been published.

## [Version 0.5.0] - 2017-08-31
### Added
- Syntax highlight for "native" keyword
- Append `'('` (or `'()'` if function has no arguments) on function autocompletion
- Hover information when hovering over functions, variables and constants
- `amxxpawn.compiler.reformatOutput` - reformats compiler output to clear unimportant information and remove clutter
- Compiler warnings and errors get turned into diagnostics

### Changed
- Syntax highlight now highlights only known tags from AMXX
- Completion search is now case-insensitive (e.g: typing `null` now mathces `NULL_VECTOR`)
- `amxxpawn.language.webApiLinks` and `amxxpawn.compiler.showInfoMessages` settings are now false by default

New compiler output (if turned on through settings):


Errors turning into diagnostics:


Hover information:

[voed]

Originally Posted by KliPPy 0.5.0 has been published. Hover information:

Can you show this popup permanently on click? Or even better, show it while editing function arguments, like with autocomplete


UPD: also, compiler warnings now showing only with `showInfoMessages: true`, looks like bug

[klippy]

Originally Posted by voed Can you show this popup permanently on click? Or even better, show it while editing function arguments, like with autocomplete

No, but you can delete the ',' and type it in again and signature help will show up. The signature help triggers on '(' and ',' characters. There's really nothing more I can do and that's how other languages in VSCode (or actually most editors) work.

Originally Posted by voed UPD: also, compiler warnings now showing only with `showInfoMessages: true`, looks like bug

I'll take a look at that. By "compiler warnings", do you mean messages in the output window or diagnostics?