e2ecdcfe33
Former-commit-id:a02aeb236c[formerly9f19e3f712] [formerlya02aeb236c[formerly9f19e3f712] [formerly06a8b51d6d[formerly 64fa9254b946eae7e61bbc3f513b7c3696c4f54f]]] Former-commit-id:06a8b51d6dFormer-commit-id:8e80217e59[formerly3360eb6c5f] Former-commit-id:377dcd10b9
16 lines
1 KiB
HTML
16 lines
1 KiB
HTML
|
|
<html>
|
|
<head>
|
|
<meta http-equiv="content-type"
|
|
content="text/html; charset=ISO-8859-1">
|
|
<title></title>
|
|
</head>
|
|
<body>
|
|
<center>
|
|
<h2> Text Formatter User Guide for Tabular Products</h2>
|
|
<h3>13. Smart Text Products - Naming Conventions</h3>
|
|
<hr>
|
|
<a href=Slide12.html>Previous Slide</a> <a href=Slide14.html>Next Slide</a> <br><img SRC=Slide13.JPG border=1><br></center>
|
|
<p><p><big>Smart Text Products inherit from the TextRules and SampleAnalysis libraries. Within the libraries, variables, in general, start with lower case letters and can use capitals and underscores to delineate words. We opt in favor of longer names to for clarity and readability of the code. It it imperative that when you create new variables or methods in the Standard or Local Text Product files, you begin their names with an underscore. This will ensure that you are not inadvertently overriding a variable or method from the Infrastructure which could break your product or produce undesirable results.<br><br><br></big>
|
|
</body>
|
|
</html>
|