Sorry Sir, I didn't see the mailing list first.Thanks for excuse me. On Wed, Aug 4, 2010 at 10:43 PM, koustava goswami <[email protected]>wrote:
> Sir,am I selected for project work????as there is no name of mine > > > On Wed, Aug 4, 2010 at 3:39 AM, <[email protected]> wrote: > >> Send Users mailing list submissions to >> [email protected] >> >> To subscribe or unsubscribe via the World Wide Web, visit >> http://lists.dgplug.org/listinfo.cgi/users-dgplug.org >> or, via email, send a message with subject or body 'help' to >> [email protected] >> >> You can reach the person managing the list at >> [email protected] >> >> When replying, please edit your Subject line so it is more specific >> than "Re: Contents of Users digest..." >> >> >> Today's Topics: >> >> 1. Re: Programming assignment (Shakthi Kannan) >> >> >> ---------------------------------------------------------------------- >> >> Message: 1 >> Date: Tue, 3 Aug 2010 14:55:49 +0530 >> From: Shakthi Kannan <[email protected]> >> To: [email protected] >> Subject: Re: [dgplug-users] Programming assignment >> Message-ID: >> >> <[email protected]<aanlktin0%2bm3w3%2bypzggaxfembij0pk6dr383dx%[email protected]> >> > >> Content-Type: text/plain; charset=UTF-8 >> >> Hi, >> >> --- On Mon, Aug 2, 2010 at 12:25 PM, Shakthi Kannan >> <[email protected]> wrote: >> | Thanks to those who submitted their solutions. We will review them, >> | and get back to you folks with comments and feedback. >> \-- >> >> The reason why we didn't give any guidelines for code submission is to >> see what code we will receive without any expectations in mind. Thanks >> for your submissions: >> >> * When you submit code, it helps to give a meaningful name for your >> .tar.gz or .zip file. If you put yourselves in our shoes, we wouldn't >> know the difference between who submitted dgplug_assignment.tar.gz, or >> pgms.tar, or problems.tar, or Program.tar. >> >> * If you knew how to use revision control (svn, git), as already >> discussed in our previous IRC sessions, you could have used it and >> provided us with a history of your code commits. >> >> * When you submit code files, it helps to give instructions on how to >> build and test your code. It cannot be assumed that the other person >> knows how to do the same. If you know Makefiles, you can write a >> simple one, that builds all your code examples, and also cleans the >> object and executable files. Or atleast put a README file, that >> explains how to use the same. >> >> * Some of you have written your name, date, description of the >> program, which is a good habit. You will also need to put an e-mail >> address, so the person reading the code knows how to contact you. In >> real life, you will have to deal with licenses, so it helps to put a >> license info as well. >> >> * None of you provided a URL in your code comments as to which problem >> you are trying to solve. From problem1.cpp, or first.py or Program2.c >> how do we know which problem you are trying to solve? >> >> * Following coding style guidelines is very essential. A person >> reading your code should be able to understand easily what you are >> trying to do. If you follow it, follow it consistently. Treat code as >> poetry, not as garbage. >> >> * I like code which is 80x25, and is readable. YMMV. >> >> * Avoid use of magic numbers in your code. Declare them as >> variables/macros. >> >> * Solving a problem for a given requirement is good, but, solving a >> problem for 'n' dimension will save you lot of headache if the >> requirement scope evolves. >> >> Only Praveen Kumar got all the answers correct. Congratulations! The >> others are also selected for project work, not because, you didn't get >> everything right, but, because you made an effort to deliver code. In >> no particular order: >> >> + Bamacharan Kundu >> + Pranay Agarwal >> + Praveen Kumar >> + Sayan Chowdhury >> >> Regards, >> >> SK >> >> -- >> Shakthi Kannan >> http://www.shakthimaan.com >> >> >> ------------------------------ >> >> _______________________________________________ >> Users mailing list >> [email protected] >> http://lists.dgplug.org/listinfo.cgi/users-dgplug.org >> >> >> End of Users Digest, Vol 32, Issue 3 >> ************************************ >> > >
_______________________________________________ Users mailing list [email protected] http://lists.dgplug.org/listinfo.cgi/users-dgplug.org
