Ruby as a Programming Language

 

SEE ATTACHED TEMPLATE FOR FONTS, FORMATTING, AND LAYOUT.

In this project, you need to write a five page report on the chosen language. The report must include following sections in addition to title and author information:
• Introduction, which should explain founder and history of the language as well as applications built by the language;
• Philosophy, which should explain any principles founder(s) follow when designing the language. This section should also specify the motivation and problem domains or areas for which this language was designed.
• Influence, which should explain features of earlier language it adopt, its features that are incorporated into later language, and other positive or negative influence on later language design and computing;
• Criticism, which should explain common complains on the language;
• OO programming, which should explain its support to OO programming, including but not limited to encapsulation, inheritance, nested classes, and dynamic/static binding.
• References, which should list publications and online resource your report cites.

Must include references from:
https://www.ruby-lang.org
https://ruby-doc.org

Up to one picture per page.
Up to on coding example per page.
Up to one graph per page.

A template of the report is provided. Refer to this template for format of the report.

SEE ATTACHED TEMPLATE FOR FONTS, FORMATTING, AND LAYOUT.
ACM Word Template for SIG Site

1. INTRODUCTION
The proceedings are the records of the conference. ACM hopes to give these conference by-products a single, high-quality appearance. To do this, we ask that authors follow some simple guidelines. In essence, we ask you to make your paper look exactly like this document. The easiest way to do this is simply to download a template from [2], and replace the content with your own material.
2. PAGE SIZE
All material on each page should fit within a rectangle of 18 × 23.5 cm (7″ × 9.25″), centered on the page, beginning 1.9 cm (0.75″) from the top of the page and ending with 2.54 cm (1″) from the bottom. The right and left margins should be 1.9 cm (.75″). The text should be in two 8.45 cm (3.33″) columns with a .83 cm (.33″) gutter.
3. TYPESET TEXT
3.1 Normal or Body Text
Please use a 9-point Times Roman font, or other Roman font with serifs, as close as possible in appearance to Times Roman in which these guidelines have been set. The goal is to have a 9-point text, as you see here. Please use sans-serif or non-proportional fonts only for special purposes, such as distinguishing source code text. If Times Roman is not available, try the font named Computer Modern Roman. On a Macintosh, use the font named Times. Right margins should be justified, not ragged.
3.2 Title and Authors
The title (Helvetica 18-point bold), authors’ names (Helvetica 12-point) and affiliations (Helvetica 10-point) run across the full width of the page – one column wide. We also recommend phone number (Helvetica 10-point) and e-mail address (Helvetica 12-point). See the top of this page for three addresses. If only one address is needed, center all address text. For two addresses, use two centered tabs, and so on. For more than three authors, you may have to improvise.
3.3 First Page Copyright Notice
Please leave 3.81 cm (1.5″) of blank text box at the bottom of the left column of the first page for the copyright notice.
3.4 Subsequent Pages
For pages other than the first page, start at the top of the page, and continue in double-column format. The two columns on the last page should be as close to equal length as possible.

Table 1. Table captions should be placed above the table
Graphics Top In-between Bottom
Tables End Last First
Figures Good Similar Very well

3.5 References and Citations
Footnotes should be Times New Roman 9-point, and justified to the full width of the column.
Use the “ACM Reference format” for references – that is, a numbered list at the end of the article, ordered alphabetically and formatted accordingly. See examples of some typical reference types, in the new “ACM Reference format”, at the end of this document. Within this template, use the style named references for the text. Acceptable abbreviations, for journal names, can be found here: http://library.caltech.edu/reference/abbreviations/. Word may try to automatically ‘underline’ hotlinks in your references, the correct style is NO underlining.
The references are also in 9 pt., but that section (see Section 7) is ragged right. References should be published materials accessible to the public. Internal technical reports may be cited only if they are easily accessible (i.e. you can give the address to obtain the report within your citation) and may be obtained by any reader. Proprietary information may not be cited. Private communications should be acknowledged, not referenced (e.g., “[Robertson, personal communication]”).
3.6 Page Numbering, Headers and Footers
Do not include headers, footers or page numbers in your submission. These will be added when the publications are assembled.
4. FIGURES/CAPTIONS
Place Tables/Figures/Images in text as close to the reference as possible (see Figure 1). It may extend across both columns to a maximum width of 17.78 cm (7”).
Captions should be Times New Roman 9-point bold. They should be numbered (e.g., “Table 1” or “Figure 2”), please note that the word for Table and Figure are spelled out. Figure’s captions should be centered beneath the image or picture, and Table captions should be centered above the table body.
5. SECTIONS

The heading of a section should be in Times New Roman 12-point bold in all-capitals flush left with an additional 6-points of white space above the section head. Sections and subsequent sub- sections should be numbered and flush left. For a section head and a subsection head together (such as Section 3 and subsection 3.1), use no additional space above the subsection head.
5.1 Subsections
The heading of subsections should be in Times New Roman 12-point bold with only the initial letters capitalized. (Note: For subsections and subsubsections, a word like the or a is not capitalized unless it is the first word of the header.)
5.1.1 Subsubsections
The heading for subsubsections should be in Times New Roman 11-point italic with initial letters capitalized and 6-points of white space above the subsubsection head.
5.1.1.1 Subsubsections
The heading for subsubsections should be in Times New Roman 11-point italic with initial letters capitalized.
5.1.1.2 Subsubsections
The heading for subsubsections should be in Times New Roman 11-point italic with initial letters capitalized.
6. ACKNOWLEDGMENTS
Our thanks to ACM SIGCHI for allowing us to modify templates they had developed.
7. REFERENCES
[1] Bowman, M., Debray, S. K., and Peterson, L. L. 1993. Reasoning about naming systems. ACM Trans. Program. Lang. Syst. 15, 5 (Nov. 1993), 795-825. DOI= http://doi.acm.org/10.1145/161468.16147.
[2] Ding, W. and Marchionini, G. 1997. A Study on Video Browsing Strategies. Technical Report. University of Maryland at College Park.
[3] Fröhlich, B. and Plate, J. 2000. The cubic mouse: a new device for three-dimensional input. In Proceedings of the SIGCHI Conference on Human Factors in Computing Systems (The Hague, The Netherlands, April 01 – 06, 2000). CHI ’00. ACM, New York, NY, 526-531. DOI= http://doi.acm.org/10.1145/332040.332491.
[4] Tavel, P. 2007. Modeling and Simulation Design. AK Peters Ltd., Natick, MA.
[5] Sannella, M. J. 1994. Constraint Satisfaction and Debugging for Interactive User Interfaces. Doctoral Thesis. UMI Order Number: UMI Order No. GAX95-09398., University of Washington.
[6] Forman, G. 2003. An extensive empirical study of feature selection metrics for text classification. J. Mach. Learn. Res. 3 (Mar. 2003), 1289-1305.
[7] Brown, L. D., Hua, H., and Gao, C. 2003. A widget framework for augmented interaction in SCAPE. In Proceedings of the 16th Annual ACM Symposium on User Interface Software and Technology (Vancouver, Canada, November 02 – 05, 2003). UIST ’03. ACM, New York, NY, 1-10. DOI= http://doi.acm.org/10.1145/964696.964697.

[8] Yu, Y. T. and Lau, M. F. 2006. A comparison of MC/DC, MUMCUT and several other coverage criteria for logical decisions. J. Syst. Softw. 79, 5 (May. 2006), 577-590. DOI= http://dx.doi.org/10.1016/j.jss.2005.05.030.

[9] Spector, A. Z. 1989. Achieving application requirements. In Distributed Systems, S. Mullender, Ed. ACM Press Frontier Series. ACM, New York, NY, 19-33. DOI= http://doi.acm.org/10.1145/90417.90738.

Columns on Last Page Should Be Made As Close As Possible to Equal Length

Sample Solution

find the cost of your paper