6502/llvm-6502
1
0
Fork 0
mirror of https://github.com/c64scene-ar/llvm-6502.git synced 2025-01-01 00:33:09 +00:00
Code Issues Projects Releases Wiki Activity

Fix a couple typos.

Browse Source 
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@29416 91177308-0d34-0410-b5e6-96231b3b80d8
This commit is contained in:
Jim Laskey 2006-07-31 20:18:49 +00:00
parent 6966c48767
commit f55914a529
2 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/CodingStandards.html
View File

@ -161,7 +161,7 @@ included, as well as any notes or "gotchas" in the code to watch out for.</p>
<b>Class overviews</b>
<p>Classes are one fundemental part of a good object oriented design. As such,
<p>Classes are one fundamental part of a good object oriented design. As such,
a class definition should have a comment block that explains what the class is
used for... if it's not obvious. If it's so completely obvious your grandma
could figure it out, it's probably safe to leave it out. Naming classes

2
docs/CommandLine.html
View File

@ -1763,7 +1763,7 @@ your custom data type.<p>
<p>This approach has the advantage that users of your custom data type will
automatically use your custom parser whenever they define an option with a value
type of your data type. The disadvantage of this approach is that it doesn't
work if your fundemental data type is something that is already supported.</p>
work if your fundamental data type is something that is already supported.</p>
</li>