[klippy]

Hello guys.
Can any of you test if this code gets your compiler stuck? I am using 1.8.2 compiler on Linux (Lubuntu 14.10):

PHP Code:

#define regex_compile(%0)            _:regex_compile(%0) 


If anyone wonders why am I even doing this, it is because I want to get rid of tag casting ("retagging"?), because my enum structure looks like:

PHP Code:

enum E_REWRITE
{
    m_pattern,
    m_flags,
    m_message[MAX_MESSAGE_LENGTH + 1]
}; 


So I don't have to put _: in before regex_compile() and Regex: in before variable name while passing m_pattern member to other Regex functions.

There is actually another workaround which compiler accepts:

PHP Code:

native regex_compile_notag(const pattern[], &ret, error[], maxLen, const flags[]="") = regex_compile;
#define regex_compile(%0)            regex_compile_notag(%0) 


but I don't think it is worth doing it.

Again, this is all just to get rid of tag casting... Because I am lazy, and I find tag casting very untidy and stupid.

[Arkshine]

Oh come one, just tag your member.

[klippy]

Like this?

PHP Code:

enum E_REWRITE
{
    Regex: m_pattern,
    m_flags,
    m_message[MAX_MESSAGE_LENGTH + 1]
}; 


Or in the code itself (when using variable)? Because the thing above doesn't work in Pawn, which I hate, and that is the reason I am doing this.

[Arkshine]

Ah, sorry. Yeah, it's kind of buggy. It seems that tag at right will try to match tag on the variable holding m_pattern member and not that member. So you need to untag.
Will check if something can be done for that. Meanwhile yeah you can use a macro or your another workaround but sounds like you're wasting a lot of time for nothing \o/.

[klippy]

Well macro doesn't work, so I will go with the other one.
Well anyway, thank you for your time.

[Arkshine]

You can actually use a trick with the magic any tag, like that:

enum E_REWRITE
{
    m_pattern,
    m_flags,
    m_message[256]
};  

new any:Data[E_REWRITE];

Data[m_pattern] = regex_compile("Something");

Since the check is done on Data, now you can set what you want which is tagged, it should not throw a tag mismatch.
You can tag as well m_pattern or not with Regex:, it doesn't matter, this would be just for consistency/readability.

[klippy]

Oh, that is awesome, thank you! I totally forgot about the any: tag.
Anyway, will that compiler bug (is it a bug?) be fixed in the future versions, preferably 1.8.3?

[Arkshine]

This behavior has always annoyed me and got curious. Long story short, after some research and testing several compiler of old AMXX versions, I've found issue has been introduced in AMXX 1.60 (!). It's about a regression from a fix and since then until now, no one has asked "why the hell I need to add a _:". \o/

It should be fixed in latest build. If you want more information, see https://github.com/alliedmodders/amxmodx/pull/164. Compatibility should be kept (meaning old plugin using _:).

[klippy]

That you for fixing it. That thing annoyed me for a while now.