rcml-group1 — Incremental development group 1

[Rcml-group1] Weekly Stock Picks

[<li3...@ba...>]

This Stock Is Our New Momentum Alert! This stock is climbing!

Trade Date: Thursday, Aug 1
Short Term Target Price: $1.15
Symbol traded: H A I_R
Price: $0.035
Company Name: Biostem US

BIG Pick at cheap price coming up and premarket analysis is ready. It 
Could be setting up to make the next Leg up!

[Rcml-group1] The first-rate method to gratify your beloved one!

[<co...@le...>]

Dream to act like a porndirector? Bang a wonder pill! http://insteellimited.com/4r6m7lgr.html

[Rcml-group1] She needs YOU to upsize your cock!

[<in...@ho...>]

Desire to act like a xxx-director? Nail a blu-colored med! http://ftp1.gbcchennai.com/yrer36e.html

Re: [Rcml-group1] hi david..

[John B. <jx...@ga...>]

> 
> yes i did but i guess that it's at the end of the
> pseudocode ..at the bottom yes it's there and i have
> committed it ..
> maruthi..

  It's not in there, and cvs doesn't show any commits from you for
that file.  I'm not entirely sure what happened.  If you commit from
the src/ directory, you won't pick up any changes in doc/ .

  Don't worry about it; I put the pseudocode in last night.

jdb

Re: [Rcml-group1] hi david..

[<tma...@ya...>]

yes i did but i guess that it's at the end of the
pseudocode ..at the bottom yes it's there and i have
committed it ..
maruthi..


__________________________________________________
Do You Yahoo!?
Yahoo! Shopping - Thousands of Stores. Millions of Products.
http://shopping.yahoo.com/

Re: [Rcml-group1] The rest of the work

[John B. <jx...@ga...>]

  applyDiff() has been tested and works correctly.

  Now, I will put getRevision() into doc/pseudocode.txt .  Maruthi
said this had been done, but I think he may have forgotten to cvs
commit it.
> 
>   Okay; here's my plan of action:
> 
> put Reymond's RevisionTree::getRevision() in doc/pseudocode.txt
> code RevisionTree::getRevision()
> test checkout()
> release on SourceForge and let Dr. Levine know
> 
> 
>   If you are awake and working with me tonight, please select your
> preferred task from the list above, announce your intention to
> complete it via email, complete it, test it, check it into CVS,
> announce the fact that you've completed it via email, and pick another
> task.

Re: [Rcml-group1] The rest of the work

[John B. <jx...@ga...>]

  Okay, now I have fixed the invalid branch number issue.  My next
task will be to test applyDiff().

> 
>   Okay; here's my plan of action:
> 
> put Reymond's RevisionTree::getRevision() in doc/pseudocode.txt
> test Text::applyDiff()
> code RevisionTree::getRevision()
> test checkout()
> release on SourceForge and let Dr. Levine know
> 
> 
>   If you are awake and working with me tonight, please select your
> preferred task from the list above, announce your intention to
> complete it via email, complete it, test it, check it into CVS,
> announce the fact that you've completed it via email, and pick another
> task.  This is the order I would prefer you select them in:
> getRevision() pseudocode
> applyDiff()
> checkout()
> getRevision()
> but you can do whatever you feel most useful doing.
> 
>   Do cvs update often (***definitely*** before you start after being
> away for an hour or two) to pick up everyone else's changes and make
> sure you can still compile.  Don't cvs update until you're sure you've
> gotten your part working (and everything compiles).
> 
>   Thanks.

Re: [Rcml-group1] The rest of the work

[John B. <jx...@ga...>]

  co.cpp has been modified to take the -r argument to determine which
revision to check out.

  checkout (and its design) needs to be modified to check to be sure
that the branch number is not invalid.  (This is the issue Maruthi
raised about checking out a revision with a number of 2.2 or so.)
This will be my next task.

> 
>   Okay; here's my plan of action:
> 
> make checkout() report requests for invalid branches
> put Reymond's RevisionTree::getRevision() in doc/pseudocode.txt
> test Text::applyDiff()
> code RevisionTree::getRevision()
> test checkout()
> release on SourceForge and let Dr. Levine know
> 
> 
>   If you are awake and working with me tonight, please select your
> preferred task from the list above, announce your intention to
> complete it via email, complete it, test it, check it into CVS,
> announce the fact that you've completed it via email, and pick another
> task.  This is the order I would prefer you select them in:
> getRevision() pseudocode
> applyDiff()
> checkout()
> getRevision()
> but you can do whatever you feel most useful doing.
> 
>   Do cvs update often (***definitely*** before you start after being
> away for an hour or two) to pick up everyone else's changes and make
> sure you can still compile.  Don't cvs update until you're sure you've
> gotten your part working (and everything compiles).
> 
>   Thanks.

Re: [Rcml-group1] hi david..

[John B. <jx...@ga...>]

> 
> hi david ..i have done that and committed it..
> actually i have added that getrevision at the end of
> the pseudocode and i think there will be few things
> which u want to change like one which i have mentioned
> previously..

  Did you do a cvs commit after adding the method to the pseudocode?
I'm not getting it when I do cvs update.

  Thanks,
  jdb

[Rcml-group1] Class Diagram in Html

[Kalyani A. <kan...@ho...>]

Hi! JDavid,

This is the class diagram for increment 3 in html....check it out and let me 
know if u any problems opening it or something like that...

Thanks

Kalyani
_____________________________________________________________________________________
Get more from the Web.  FREE MSN Explorer download : http://explorer.msn.com

[Rcml-group1] hi david..

[<tma...@ya...>]

hi david ..i have done that and committed it..
actually i have added that getrevision at the end of
the pseudocode and i think there will be few things
which u want to change like one which i have mentioned
previously..
--- John Blackstone <jx...@ga...> wrote: > 
 checkout() has now been coded, but it will depend
> on getRevision()
> to function.  It will need to be further tested at
> that point.
> yes for the rest see u in the class ..i guess u are 
on the way anyway..
:-) maruthi..
>   Also, co.cpp needs to respect the -r argument to
> request a revision
> by number.
> 
>   See you in class.
> > 
> >   Okay; here's my plan of action:
> > 
> > put Reymond's RevisionTree::getRevision() in
> doc/pseudocode.txt
> > test Text::applyDiff()
> > code RevisionTree::getRevision()
> > test checkout()
> > add command-line processing to co.cpp
> > release on SourceForge and let Dr. Levine know
> > 
> > 
> >   If you are awake and working with me tonight,
> please select your
> > preferred task from the list above, announce your
> intention to
> > complete it via email, complete it, test it, check
> it into CVS,
> > announce the fact that you've completed it via
> email, and pick another
> > task.  This is the order I would prefer you select
> them in:
> > getRevision() pseudocode
> > applyDiff()
> > checkout()
> > getRevision()
> > but you can do whatever you feel most useful
> doing.
> > 
> >   Do cvs update often (***definitely*** before you
> start after being
> > away for an hour or two) to pick up everyone
> else's changes and make
> > sure you can still compile.  Don't cvs update
> until you're sure you've
> > gotten your part working (and everything
> compiles).
> > 
> >   Thanks.
> _______________________________________________
> Rcml-group1 mailing list
> Rcm...@li...
>
http://lists.sourceforge.net/mailman/listinfo/rcml-group1


__________________________________________________
Do You Yahoo!?
Yahoo! Shopping - Thousands of Stores. Millions of Products.
http://shopping.yahoo.com/

Re: [Rcml-group1] The rest of the work

[John B. <jx...@ga...>]

  checkout() has now been coded, but it will depend on getRevision()
to function.  It will need to be further tested at that point.

  Also, co.cpp needs to respect the -r argument to request a revision
by number.

  See you in class.
> 
>   Okay; here's my plan of action:
> 
> put Reymond's RevisionTree::getRevision() in doc/pseudocode.txt
> test Text::applyDiff()
> code RevisionTree::getRevision()
> test checkout()
> add command-line processing to co.cpp
> release on SourceForge and let Dr. Levine know
> 
> 
>   If you are awake and working with me tonight, please select your
> preferred task from the list above, announce your intention to
> complete it via email, complete it, test it, check it into CVS,
> announce the fact that you've completed it via email, and pick another
> task.  This is the order I would prefer you select them in:
> getRevision() pseudocode
> applyDiff()
> checkout()
> getRevision()
> but you can do whatever you feel most useful doing.
> 
>   Do cvs update often (***definitely*** before you start after being
> away for an hour or two) to pick up everyone else's changes and make
> sure you can still compile.  Don't cvs update until you're sure you've
> gotten your part working (and everything compiles).
> 
>   Thanks.

Re: [Rcml-group1] The rest of the work

[John B. <jx...@ga...>]

  Maruthi has finished coding applyDiff().  It looks like things went
quite smoothly, but it could use some testing.

  As a reminder, do "cvs update" often.  Especially whenever you start
working again after not doing so for a while.  If you see a message
about "conflicts found," you need to edit the appropriate file and
find a section (or sections) that looks like:

<<<<<<
your version
======
other person's version
>>>>>>

  These sections are places where somebody has changed the file since
you last updated it or checked it out.  You will have to fix this and
then do another update before doing anything else.

> 
>   Okay; here's my plan of action:
> 
> put Reymond's RevisionTree::getRevision() in doc/pseudocode.txt
> test Text::applyDiff()
> code RevisionTree::getRevision()
> code Archive::checkout()
> release on SourceForge and let Dr. Levine know
> 
> 
>   If you are awake and working with me tonight, please select your
> preferred task from the list above, announce your intention to
> complete it via email, complete it, test it, check it into CVS,
> announce the fact that you've completed it via email, and pick another
> task.  This is the order I would prefer you select them in:
> getRevision() pseudocode
> applyDiff()
> checkout()
> getRevision()
> but you can do whatever you feel most useful doing.
> 
>   Do cvs update often (***definitely*** before you start after being
> away for an hour or two) to pick up everyone else's changes and make
> sure you can still compile.  Don't cvs update until you're sure you've
> gotten your part working (and everything compiles).
> 
>   Thanks.

Re: [Rcml-group1] The rest of the work

[John B. <jx...@ga...>]

  Okay, checkin() is working completely and I have changed the
Makefile.  Now, when you compile, two programs are produced: ci and
co.

  I think I will code checkout() now, with stubs for the methods it
needs that do not yet exist.

> 
>   Okay; here's my plan of action:
> 
> put Reymond's RevisionTree::getRevision() in doc/pseudocode.txt
> code Text::applyDiff()
> code RevisionTree::getRevision()
> code Archive::checkout()
> release on SourceForge and let Dr. Levine know
> 
> 
>   If you are awake and working with me tonight, please select your
> preferred task from the list above, announce your intention to
> complete it via email, complete it, test it, check it into CVS,
> announce the fact that you've completed it via email, and pick another
> task.  This is the order I would prefer you select them in:
> getRevision() pseudocode
> applyDiff()
> checkout()
> getRevision()
> but you can do whatever you feel most useful doing.
> 
>   Do cvs update often (***definitely*** before you start after being
> away for an hour or two) to pick up everyone else's changes and make
> sure you can still compile.  Don't cvs update until you're sure you've
> gotten your part working (and everything compiles).
> 
>   Thanks.

[Rcml-group1] Re: hi david..

[John B. <jx...@ga...>]

> 
> may be what i was saying is not relevent to the
> getrevision..what i said that..
> if u are using getrevision in checkout then i found
> that as we can give a revision number higher than
> head id like ..if the headid=1.1 and the revision to
> be
> checked out is 1.3 then it checkout 1.1..
> but if the revision to be checked out is specified as
> 2.3 or something like that..it says that the revision
> is absent..

  Oh!  I understand now.  I'm slow, sometimes. :)

  Yes, we want it to work just like RCS.  To RCS, if you checkout
something on a non-existent branch, it isn't there.  The branch
numbers are any odd-count number, such as 1, 2, or 1.3.1 .  So, the
increment 3 system should refuse to perform a checkout for anything
with a branch other than 2.

  You're right; this should be added into getRevision().  I believe it
should have a fatal error (error message and exit) if the user does
this.

> anyway i guess the above thing should be included in
> the pseudocode of checkout..
> i have an exam tommorrow..that's why i can't do much
> today..i'll be coding..the appdiff..but i guess 
> i didn't have the total idea about the deque and 
> pop and push things..so please gothrough that code
> after cvs updating it..
> i got quite hectic schedule ..i got to submit my db
> project on next monday..n/w's project due this
> wednesday..it's 7:45 p.m..i'll be here upto 9 p.m

  I understand.  I've been there. :)  Just do your best, and that will
be all right.  Check the docs for the STL at
http://www.sgi.com/Technology/STL/ for information on the methods
available on a deque; it can be accessed just like an array, too.

  Please do your best to make sure that everything at least compiles
before doing a cvs commit.  (I haven't checked yet to see if you did
one yet, but discovered that problem Saturday; commits can break what
other people are working on at times.)

jdb

[Rcml-group1] Naptime

[John B. <jx...@ga...>]

  Going to take a 3 1/2 hour break now to sleep.  Then, to work.
Please, make some time during the day tomorrow to try to knock out
some of the tasks mentioned in the previous emails.

  When I get home around 3 or 4 tomorrow, I will either get back on it
or go to sleep and then get back on it.

jdb

Re: [Rcml-group1] The rest of the work

[John B. <jx...@ga...>]

  The mechanics of checkin() are now working completely.  I just need
to add in the same output messages RCS produces.

> 
>   Okay; here's my plan of action:
> 
> finish checkin()  # half of it is working; the rest needs the method above
> put Reymond's RevisionTree::getRevision() in doc/pseudocode.txt
> code Text::applyDiff()
> code RevisionTree::getRevision()
> code Archive::checkout()
> modify the makefile to create ci and co executables
> release on SourceForge and let Dr. Levine know
> 
> 
>   If you are awake and working with me tonight, please select your
> preferred task from the list above, announce your intention to
> complete it via email, complete it, test it, check it into CVS,
> announce the fact that you've completed it via email, and pick another
> task.  This is the order I would prefer you select them in:
> getRevision() pseudocode
> applyDiff()
> checkout()
> getRevision()
> but you can do whatever you feel most useful doing.
> 
>   Do cvs update often (***definitely*** before you start after being
> away for an hour or two) to pick up everyone else's changes and make
> sure you can still compile.  Don't cvs update until you're sure you've
> gotten your part working (and everything compiles).
> 
>   Thanks.

[Rcml-group1] Suggestion

[John B. <jx...@ga...>]

  I'm finding it more useful to refer to the .h files than it is to
refer to the class diagram.

jdb

Re: [Rcml-group1] The rest of the work

[John B. <jx...@ga...>]

  Completed the getCollectionOfRevision() accessor method.  About to
test checkin().

> 
>   Okay; here's my plan of action:
> 
> finish checkin()  # half of it is working; the rest needs the method above
> put Reymond's RevisionTree::getRevision() in doc/pseudocode.txt
> code Text::applyDiff()
> code RevisionTree::getRevision()
> code Archive::checkout()
> modify the makefile to create ci and co executables
> release on SourceForge and let Dr. Levine know
> 
> 
>   If you are awake and working with me tonight, please select your
> preferred task from the list above, announce your intention to
> complete it via email, complete it, test it, check it into CVS,
> announce the fact that you've completed it via email, and pick another
> task.  This is the order I would prefer you select them in:
> getRevision() pseudocode
> applyDiff()
> checkout()
> getRevision()
> but you can do whatever you feel most useful doing.
> 
>   Do cvs update often (***definitely*** before you start after being
> away for an hour or two) to pick up everyone else's changes and make
> sure you can still compile.  Don't cvs update until you're sure you've
> gotten your part working (and everything compiles).
> 
>   Thanks.
> 
> jdb
> _______________________________________________
> Rcml-group1 mailing list
> Rcm...@li...
> http://lists.sourceforge.net/mailman/listinfo/rcml-group1
> 

[Rcml-group1] Communication tonight

[John B. <jx...@ga...>]

  The most reliable means of communication tonight will probably be
the talk command on either gamma or rcml.sourceforge.net .  A close
second would be a page to my cellphone from
http://message.swbellwireless.com/dpcs/ .  Calling the cellphone may
not be good; I'm getting bad reception in the area, plus it means I
can't type examples to you like I could with talk.

jdb

[Rcml-group1] The rest of the work

[John B. <jx...@ga...>]

  Okay; here's my plan of action:

RevisionTree::getCollectionOfRevision()  # the existing one doesn't do what I want
finish checkin()  # half of it is working; the rest needs the method above
put Reymond's RevisionTree::getRevision() in doc/pseudocode.txt
code Text::applyDiff()
code RevisionTree::getRevision()
code Archive::checkout()
modify the makefile to create ci and co executables
release on SourceForge and let Dr. Levine know


  If you are awake and working with me tonight, please select your
preferred task from the list above, announce your intention to
complete it via email, complete it, test it, check it into CVS,
announce the fact that you've completed it via email, and pick another
task.  This is the order I would prefer you select them in:
getRevision() pseudocode
applyDiff()
checkout()
getRevision()
but you can do whatever you feel most useful doing.

  Do cvs update often (***definitely*** before you start after being
away for an hour or two) to pick up everyone else's changes and make
sure you can still compile.  Don't cvs update until you're sure you've
gotten your part working (and everything compiles).

  Thanks.

jdb

Re: [Rcml-group1] (no subject)

[John B. <jx...@ga...>]

> 
> HI everybody,
> 
> Sorry , I could not attend the meeting today.
> 
> I had been awake for the past 2 nights , and somehow
> slept thru'out the day today. Woke up just now at
> 5:50pm!! Please do your bit and don't hesitate to
> leave the remaining work for me .
> 
> I will be sitting thru'out tonight , so I would
> complete the remaining work .
> 
> regards,
> RANA

  That's cool; I understand and have been there before.  Grab an
uncoded method and start coding.  Grab the code and start testing.
I just got back home; I'll try to have a more specific suggestion in a
little bit, once I cvs update, see what's been done so far, and get my
bearings.

jdb

[Rcml-group1] Re: getRevision pseudocode & code

[John B. <jx...@ga...>]

> 
> --Herd_of_Walrus_547_000
> Content-Type: TEXT/plain; charset=us-ascii
> Content-MD5: 7jxsVTP9tF+qE4fMWZBCbg==
> 
> hey JD,
> 
> here's what we came up for getRevision
> prob'ly need some revision ... hey, getRevision needs revision :)
> and it's my first c++ code... so be patient
> 
> tq
> Rey

  Looks good.  A few changes below, noted in comments.

> 
> --Herd_of_Walrus_547_000
> Content-Type: TEXT/plain; name="getRevision.code"; charset=us-ascii; x-unix-mode=0644
> Content-Description: getRevision.code
> Content-MD5: 1B2M2Y8AsgTpgAmY7PhCfg==
> 
> --Herd_of_Walrus_547_000
> Content-Type: TEXT/plain; name="getRevision.pcode."; charset=us-ascii; x-unix-mode=0644
> Content-Description: getRevision.pcode.
> Content-MD5: CrVEPCMLoFQusjqaYq1ong==
> 
> # Pseudocode for the RevisionTree::getRevision() method
> # Purpose: construct a Text object representing a particular revision
> # Returns: a Text object
> # Parameter: revno, a RevisionNumber object
> # Parameter: a, an Archive object
# You won't need to take an Archive as a parameter.  The RevisionTree
# the method is called on is all that is needed; an Archive just
# provides additional stuff unneeded for this method.  (That's some
# form of coupling; stamp, I think.)
> 
> RevisionTree::getRevision(RevisionNumber revno, Archive a)
>   assign current head ID to currev
>   copy the current head revision to a new Text object curtext
# Actually, you're copying the current head Text to a new
>   # do applyDiff until the specified revision is found
>   do while (revno!=currev AND deque is not empty)
>     pop a Revision from the deque
>     assign Revision->revisionID to currev
>     curtext.applyDiff(Revision->differFromNext)
>   enddo
# 100% correct!
>   # either found the revision or the deque is empty
>   if (revno!=currev)
>     error "invalid revision number"  # or "revision not found" ?
# Experiment with RCS and copy the exact error messaage you get when
# you do that.
>   else
>     return curtext
>   endif
> end
> 
> --Herd_of_Walrus_547_000--
> 

  Add it into doc/pseudocode.txt in the rcml/ directory that you get
out of CVS and commit.  Then, feel free to start coding.

jdb

[Rcml-group1] (no subject)

[ABHISHEK R. <abh...@ya...>]

HI everybody,

Sorry , I could not attend the meeting today.

I had been awake for the past 2 nights , and somehow
slept thru'out the day today. Woke up just now at
5:50pm!! Please do your bit and don't hesitate to
leave the remaining work for me .

I will be sitting thru'out tonight , so I would
complete the remaining work .

regards,
RANA

__________________________________________________
Do You Yahoo!?
Yahoo! Calendar - Get organized for the holidays!
http://calendar.yahoo.com/

[Rcml-group1] findArchiveFilename() works

[<jx...@ga...>]

  My preliminary tests indicate that the findArchiveFilename() method
is working.  I can't get all of checkin() to work, yet, but I think it
will, soon.

jdb