1. When should a quick-and-dirty compiler be used? When should an optimizing com

Question

1. When should a quick-and-dirty compiler be used? When should an optimizing compiler be used?

2. Why, in your opinion, did ALGOL60 not become a widely used language?

3. Write an extended BNF description of a C++ function header. Assume the following have already been defined:

<type> : a valid type name (assume that parameters and return values can be of any type)        

                  <identifier> : a valid identifier

4. C++ does not provide subrange types. Is that a weakness? Why or why not?

5. Why are the pointers of most languages restricted to pointing at a single type object?

6. C and its derivatives are unique in having unary assignment operators. Why is this useful? What problems can this cause?

Explanation / Answer

1)

Quick and dirty compilers produce an object program quickly but in this stage code program may be inefficient of its storage consumption & its speed.

Cheaply made or done; of inferior quality: a quick-and-dirty construction project; a quick-and-dirty research report.

Describes a crock put together under time or user pressure. Used esp. when you want to convey that you think the fast way might lead to trouble further down the road.

Related Questions

Navigate

• Browse (All)
• Browse 1
• Subjects

Integrity-first tutoring: explanations and feedback only — we do not complete graded work. Learn more.