mirror of
https://github.com/EiffelSoftware/eiffel-org.git
synced 2025-12-07 23:32:42 +01:00
Author:halw
Date:2009-12-16T04:59:44.000000Z git-svn-id: https://svn.eiffel.com/eiffel-org/trunk@370 abb3cda0-5349-4a8f-a601-0c33ac3a8c38
This commit is contained in:
Binary file not shown.
|
After Width: | Height: | Size: 1.5 KiB |
@@ -0,0 +1,3 @@
|
||||
title=AutoTest information icon
|
||||
author=halw
|
||||
path=content/autotest-information-icon
|
||||
Binary file not shown.
|
After Width: | Height: | Size: 10 KiB |
@@ -0,0 +1,3 @@
|
||||
title=AutoTest interface results execution
|
||||
author=halw
|
||||
path=content/autotest-interface-results-execution
|
||||
Binary file not shown.
|
After Width: | Height: | Size: 10 KiB |
@@ -0,0 +1,3 @@
|
||||
title=AutoTest test results details
|
||||
author=halw
|
||||
path=content/autotest-test-results-details
|
||||
Binary file not shown.
|
After Width: | Height: | Size: 15 KiB |
@@ -0,0 +1,3 @@
|
||||
title=AutoTest testing pane execution results
|
||||
author=halw
|
||||
path=content/autotest-testing-pane-execution-results
|
||||
@@ -100,7 +100,7 @@ Features of reusable classes should use consistent names. A set of standard name
|
||||
|
||||
For local entities and formal arguments of routines, it is all right to use abbreviated names, since these identifiers only have a local scope, and choosing a loud name would give them too much pretense, leading to potential conflicts with features.
|
||||
|
||||
The complete set of style rules applied by ISE is available on the web in both <span> [http://www.eiffel.com/doc/manuals/language/style/ HTML] </span> and <span> [http://www.eiffel.com/doc/manuals/language/style/style.pdf PDF] </span> forms. These rules are an integral part of the Eiffel method; in quality software, there is no such thing as a detail. Applying them systematically promotes consistency between projects in the Eiffel world, enhances reusability, and facilitates everyone's work.
|
||||
The complete set of style rules applied by ISE is available on the web in both <span> [http://archive.eiffel.com/doc/manuals/language/style/page.html HTML] </span> and <span> [http://archive.eiffel.com/doc/manuals/language/style/style.pdf PDF] </span> forms. These rules are an integral part of the Eiffel method; in quality software, there is no such thing as a detail. Applying them systematically promotes consistency between projects in the Eiffel world, enhances reusability, and facilitates everyone's work.
|
||||
|
||||
|
||||
|
||||
|
||||
Reference in New Issue
Block a user