Skip to content

Documentation improvement ▼#282

Open
Dayvison wants to merge 7 commits into
pawn-lang:masterfrom
Dayvison:documentation
Open

Documentation improvement ▼#282
Dayvison wants to merge 7 commits into
pawn-lang:masterfrom
Dayvison:documentation

Conversation

@Dayvison

@Dayvison Dayvison commented Feb 3, 2018

Copy link
Copy Markdown
  • Add location tag <location file="" startline="" endline="">
  • Fix transition tag
  • Escape special characters in documentation
  • Fix enumerators documentation
  • Fix constant documentation
  • Add documentation for enumerators items
  • Add new atributes for member
    • const
    • deprecated
    • entry
    • enum
    • enum_field
    • forward
    • missing
    • naked
    • native
    • pre_defined
    • prototyped
    • public
    • returns
    • return_type
    • static
    • stock
    • unused
  • Update pawndoc.xsl to support new features
  • Fix a bug, when you documentate one prototype without keyword forward the documentation go to global

I've change how the compiler check if symbol are static, but don't worry all work fine
Remove xml escape
remove comments from sc1.
Missed /
Fixed constant location
@Dayvison

Dayvison commented Feb 3, 2018

Copy link
Copy Markdown
Author

I don't know what will be the tests for this.

I've change how the compiler check if symbol are static, but don't worry all work fine(Tested)

@Y-Less

Y-Less commented Feb 3, 2018

Copy link
Copy Markdown
Member

I use several organisational tags, including <section>, <subsection>, and <library>. It would be nice if these were properly hierarchical so that functions declared within one stayed within it.

Better yet, one generic <section> (or similar) tag that can nest other sections and language features, and would take parameters to determine what sort of section it was to make the possibilities endless.

@Dayvison

Dayvison commented Feb 3, 2018

Copy link
Copy Markdown
Author

Can you give a example of usage?

Comment thread source/compiler/sc.h
@Dayvison

Dayvison commented Feb 4, 2018

Copy link
Copy Markdown
Author

@YashasSamaga @Y-Less The actual way is ignore all unused symbols, in my opinion even symbol are unused they should go to documentation, with unused attribute

@stale

stale Bot commented Oct 26, 2018

Copy link
Copy Markdown

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale Bot added the state: stale label Oct 26, 2018
@Y-Less

Y-Less commented May 30, 2020

Copy link
Copy Markdown
Member

@YashasSamaga You've looked in to this. Merge thoughts?

@stale stale Bot removed the state: stale label May 30, 2020
@YashasSamaga

YashasSamaga commented May 31, 2020

Copy link
Copy Markdown
Member

@Dayvison can you please rebase with dev?

@stale

stale Bot commented Aug 29, 2020

Copy link
Copy Markdown

This issue has been automatically marked as stale because it has not had recent activity.

@stale stale Bot added the state: stale label Aug 29, 2020
@Dayvison Dayvison requested a review from a team as a code owner September 20, 2020 11:50
@stale stale Bot removed the state: stale label Sep 20, 2020
@stale

stale Bot commented Dec 24, 2020

Copy link
Copy Markdown

This issue has been automatically marked as stale because it has not had recent activity.

@stale stale Bot added the state: stale label Dec 24, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants