QuickTopic (SM) free message boards QuickTopic (SM) free message boards
Skip to Messages
  Sign In to access your topic list  |New Topic |My Topics|Profile
Upgrade to Pro   Customize, show pictures, add an intro, and more:   QuickTopic Pro...and check out QuickThreadSM
Topic: CSE 130 Homework #6
Views: 901, Unique: 403 
Subscribers: 0
What's
this?
Printer-Friendly Page
Subscribe to get & post, or stop messages by email Subscribe
All messages            1-16 of 16        
About these ads
Who | When
Messagessort recent-top   
Post a new message
 
Amir  1
02-18-2004 02:02 AM ET (US)
Would it be alright if we did problem 6.2 in java?

Amir
Amir  2
02-18-2004 02:12 AM ET (US)
what exactly is question 6.4 asking for?

what is a module buffer?
what is a class buffer?
lee  3
02-18-2004 06:12 PM ET (US)
for both 6.1 & 6.4, it said "design a program", so I don't need to write the actual code, right?
Student 18  4
02-19-2004 12:20 AM ET (US)
This homework is taking 50x longer than all the others...
ron  5
02-19-2004 01:10 AM ET (US)
man... just started hw... what's auxiliary? is that just a fancy way of saying a "stack?" did i miss it in the text?

ron
Derrick  6
02-19-2004 02:20 AM ET (US)
Where are the TA's??? We need answers to those questions...
130temp  7
02-19-2004 02:45 AM ET (US)
Edited by author 02-19-2004 02:46 AM
I can't compile .cpp file because I include a bunch of standard libraries, and under ieng9, they can't be found. is there any alternative way?
Fox Harrell  8
02-19-2004 03:33 AM ET (US)
You may use Java.

Problem 6.4:
The chapter describes aspects of both classes and modules. For this problem you should implement a buffer, as described in example 6.1, as both a class and as a module.
Fox Harrell  9
02-19-2004 03:46 AM ET (US)
The auxiliary stack is a stack used as a supporting data structure within your algorithm.
Fox Harrell  10
02-19-2004 04:04 AM ET (US)
Lee: The book describes the elements of the design process (see section 6.3 for example). Your design should include pseudocode (or real code if you prefer) as detailed as what is in Sethi's discussion of the design process. Also, please include clear comments within your code.
Fox Harrell  11
02-19-2004 04:15 AM ET (US)
Problem 6.4 clarification:

You should "design" (rather than implement) a buffer, as in example 6.1, as both a class and as a module.
Yongbo Jing  12
02-19-2004 01:57 PM ET (US)
"Problem 6.4:
The chapter describes aspects of both classes and modules. For this problem you should implement a buffer, as described in example 6.1, as both a class and as a module."
Since I already implemented a buffer, would that be alright?
Yongbo Jing  13
02-19-2004 02:09 PM ET (US)
Edited by author 02-19-2004 02:10 PM
On page 225 of our textbook, the author gives an definition for module. It seems to me that that is no a lot different from a class in Java. This might be a silly question, but can you state the difference between a module and a class?
Fox Harrell  14
02-19-2004 02:53 PM ET (US)
Edited by author 02-19-2004 02:54 PM
Yongbo Jing:

Implementing it is fine (in fact it is easier for us to grade if you include an output file). I was trying to steer you to the section in the chapter regarding the design process. It includes implementation, but he only describes implementation details informally.

The difference between classes and modules is the point of the question. You should read the chapter carefully and your question should be answered. If you already implemented it using a class, perhaps you should design a module for the other half of the question.
hello  15
08-22-2005 05:13 PM ET (US)
Deleted by author 08-22-2005 05:14 PM
   16
07-21-2006 05:53 PM ET (US)
Deleted by topic administrator 07-22-2006 09:28 AM
RSS link What's this?
All messages            1-16 of 16        
QuickTopicSM message boards
Over 200,000 topics served
Learn more Frequently asked questions  Acknowledgements
What they're saying about QuickTopic
 Questions, comments, or suggestions? Contact Us
Read our use policy before beginning. We value your privacy; please read our privacy statement.
Copyright ©1999-2008 Internicity Inc. All rights reserved.