Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Use pseudocode or real code in explanations#215

appgurueu started this conversation inGeneral
Discussion options

Sparked bythis comment, I'd like to discuss whether explanations should use pseudocode or "real" code.

Reasons against pseudocode:

  • It isn't standardized. This leads to inconsistencies.
  • It's typically less precise than real code; it may be harder to understand, being more informal.
  • You can't execute and test it.
  • There is no "pseudocode" syntax highlighting in GFM; you'd have to pick the syntax highlighting of a "real" programming language and hope it works decently well with your pseudocode.

Reasons against "real" code:

  • It may obstruct the algorithm by introducing language boilerplate; it is less flexible than pseudocode.

Ultimatively, I'd say I'm fine withboth pseudocode and "real" code. If "real" code doesn't have significantly more boilerplate than pseudocode, I'd lean towards real code. If the boilerplate makes the algorithm much harder to understand, I'd prefer textual or pseudocode descriptions.

You must be logged in to vote

Replies: 0 comments

Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment
Category
General
Labels
1 participant
@appgurueu

[8]ページ先頭

©2009-2025 Movatter.jp