Skip to main content
replaced http://codereview.stackexchange.com/ with https://codereview.stackexchange.com/
Source Link

As a general rule, we prefer to see: Your full code, unedited, exactly as it appears in your IDE. Code Review has an extended 65,535 character limit. Unless you're getting close to exceeding that, your code isn't too long.

With code split across multiple files, it is generally best to use separate code blocks in your question, with a title for each so people can easily navigate them.

A few hundred lines of code is not out-of-the-ordinary for this site, don't worry about it.

As an example on how to structure your post, take thisthis question of mine which is split across 7 code modules.

As a general rule, we prefer to see: Your full code, unedited, exactly as it appears in your IDE. Code Review has an extended 65,535 character limit. Unless you're getting close to exceeding that, your code isn't too long.

With code split across multiple files, it is generally best to use separate code blocks in your question, with a title for each so people can easily navigate them.

A few hundred lines of code is not out-of-the-ordinary for this site, don't worry about it.

As an example on how to structure your post, take this question of mine which is split across 7 code modules.

As a general rule, we prefer to see: Your full code, unedited, exactly as it appears in your IDE. Code Review has an extended 65,535 character limit. Unless you're getting close to exceeding that, your code isn't too long.

With code split across multiple files, it is generally best to use separate code blocks in your question, with a title for each so people can easily navigate them.

A few hundred lines of code is not out-of-the-ordinary for this site, don't worry about it.

As an example on how to structure your post, take this question of mine which is split across 7 code modules.

added 159 characters in body
Source Link
Kaz
  • 8.8k
  • 1
  • 12
  • 19

As a general rule, we prefer to see: Your full code, unedited, exactly as it appears in your IDE. Code Review has an extended 65,535 character limit. Unless you're getting close to exceeding that, your code isn't too long.

With code split across multiple files, it is generally best to use separate code blocks in your question, with a title for each so people can easily navigate them.

A few hundred lines of code is not out-of-the-ordinary for this site, don't worry about it.

As an example on how to structure your post, take this question of mine which is split across 7 code modules.

As a general rule, we prefer to see: Your full code, unedited, exactly as it appears in your IDE.

With code split across multiple files, it is generally best to use separate code blocks in your question, with a title for each so people can easily navigate them.

A few hundred lines of code is not out-of-the-ordinary for this site, don't worry about it.

As an example, take this question of mine which is split across 7 code modules.

As a general rule, we prefer to see: Your full code, unedited, exactly as it appears in your IDE. Code Review has an extended 65,535 character limit. Unless you're getting close to exceeding that, your code isn't too long.

With code split across multiple files, it is generally best to use separate code blocks in your question, with a title for each so people can easily navigate them.

A few hundred lines of code is not out-of-the-ordinary for this site, don't worry about it.

As an example on how to structure your post, take this question of mine which is split across 7 code modules.

Source Link
Kaz
  • 8.8k
  • 1
  • 12
  • 19

As a general rule, we prefer to see: Your full code, unedited, exactly as it appears in your IDE.

With code split across multiple files, it is generally best to use separate code blocks in your question, with a title for each so people can easily navigate them.

A few hundred lines of code is not out-of-the-ordinary for this site, don't worry about it.

As an example, take this question of mine which is split across 7 code modules.