Re: Maintaining a Dusty Deck
From: rih5342 (rob.hickey_at_nospam.alum.mit.edu)
Date: 10/14/04
- Next message: John C. Bollinger: "Re: Maintaining a Dusty Deck"
- Previous message: Richard E Maine: "Re: Maintaining a Dusty Deck"
- In reply to: rih5342: "Maintaining a Dusty Deck"
- Next in thread: bv: "Re: Maintaining a Dusty Deck"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Thu, 14 Oct 2004 16:23:12 -0400
My real problem is that I over estimated the "quality"
of the code and under estimated the amount of time
needed to improve it.
The countless errors are reasonable, understandable
and fixable, but always times 500, just about every file
needing attention, and many times.
Show some code, good point point, speak with data.
I planned on organizing the code roughly as follows.
c typical contents of file
c module one
c contains
include "sub1.for"
include "sub2.for"
.
include "sub120.for"
c end module one
c typical contents of file
c module two
c contains
include "sub300.for"
include "sub301.for"
.
include "sub400.for"
c end module two
When I'm done, I'll just uncomment the module lines
and continue.
I took on this project and bit off more than I can chew.
I appreciate all your comments.
Thanks.
- Next message: John C. Bollinger: "Re: Maintaining a Dusty Deck"
- Previous message: Richard E Maine: "Re: Maintaining a Dusty Deck"
- In reply to: rih5342: "Maintaining a Dusty Deck"
- Next in thread: bv: "Re: Maintaining a Dusty Deck"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|