[Arkshine]

The original plugin has been changed with my own style, including the comments.

┌────────────────────────────────┐
│ See the table of characters ;) │
└────────────────────────────────┘

[Tirant]

You make those comments yourself by hand or do you use a program? If you make them by hand, I think I might write a quick little thing in Java and see if I can automate it. They look really good ;)

I've been trying to find some sort thing that can document pawn code like javadoc does for java. Would help you guys as approvers a lot as well, because some people code like crap, but documentation would help.

[Arkshine]

By hand, but you know, you do it one time then after it's very fast to copy-paste or adjusting.

[Tirant]

Ya, but how much easier would it be to have it auto-generated? Besides, I've been on a mission since I came back to coding pawn and realized how horrible amxx studio and pawn studio are. I've been trying a couple things, and documentation generation is something I wanted to see if I could get. I was thinking about trying to create a custom class of files for NetBeans or Eclipse, but that would probably be beyond me.

[Arkshine]

I would love to see a tool which generates a documentation like does Doxygen, but of course something simplified for pawn. So making a decent comments in the sma would make a lot of sense. Such tool would help definitively to understand better/fastly the flow of the plugin. Also, it would be nice to attach that near of "Get Source", you would have "Get Documentation", it will redirects you directly to a generated documentation from the plugin source, and you would be able to download the whole thing too. Well, I'm dreaming, but since here there is a severe lack of documentation, it would really helpful.

[Tirant]

I installed Doxygen earlier and it worked fine when compiling test commands for one of my files. I've been working on creating my own language support for amxx/pawn in NetBeans, I think I'm actually making progress. I have the language like initialized, I think I just need to add add the lexer tags, which doesn't scare be half as bad as having to set up syntax (which I will prolly at during that step). (If you want to help, I don't mind ). I really don't think I will finish because I have no idea of the complete functionality of the Pawn language, but if I did, it would be pretty sweet having auto-complete and stuff, and seeing errors as they appear in the syntax.

EDIT: I take back what I said, I think it is working right now. Even though the syntax highlighting is completely wrong and the includes think they are C++, one of my templates included amxmodx and amxmisc, and its pretty cool (progress is progress IMO)... it even has documentation for the amxx natives loaded

[BeasT]

Originally Posted by Arkshine With the fix above, the crash still happens ?

Yes

[Tirant]

Hey Ark., just wanted to tell you that I got Doxygen to start working. It produces decent documentation, but it considers all enums of the same type one enum, and then shows that enum everywhere you had an enum. Besides that, it's not bad.

[Arkshine]

Since the syntax is near of C, it doesn't surprise me the output is somehow decent. I'm sure it would be not too hard to modify Doxygen to fix some part.

[Tirant]

Except Pawn is typeless, which is kind of a big difference when trying to check syntax.