Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
senf
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Package Registry
Container Registry
Model registry
Operate
Environments
Terraform modules
Monitor
Incidents
Service Desk
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
wiback
senf
Commits
b3fbb1c7
Commit
b3fbb1c7
authored
18 years ago
by
tho
Browse files
Options
Downloads
Patches
Plain Diff
typo fix
parent
c5d0f0d1
No related branches found
Branches containing commit
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
Mainpage.dox
+2
-2
2 additions, 2 deletions
Mainpage.dox
with
2 additions
and
2 deletions
Mainpage.dox
+
2
−
2
View file @
b3fbb1c7
...
@@ -330,7 +330,7 @@
...
@@ -330,7 +330,7 @@
\section conventions Coding Conventions
\section conventions Coding Conventions
Here we have laid down the coding conventions used throughout the SENF framework. Please adhere
Here we have laid down the coding conventions used throughout the SENF framework. Please ad
here
to these conventions when changing or adding code. If you use emacs, you can use the C++ IDE for
to these conventions when changing or adding code. If you use emacs, you can use the C++ IDE for
emacs from http://g0dil.de which greatly simplifies following these conventions.
emacs from http://g0dil.de which greatly simplifies following these conventions.
...
@@ -369,7 +369,7 @@
...
@@ -369,7 +369,7 @@
Boost.Preprocessor library</td></tr> </table>
Boost.Preprocessor library</td></tr> </table>
\par Rationale:
\par Rationale:
There are two part's to this: First, separating the implementation of inlines and temp
a
ltes
There are two part's to this: First, separating the implementation of inlines and templ
a
tes
out of the header file makes the header file much easier to read. This is important, since
out of the header file makes the header file much easier to read. This is important, since
the header file will be used as a reference by the developers.
the header file will be used as a reference by the developers.
\par
\par
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment