Show Bid Request Lex/Yacc assignment Bid Request Id: 4180 Bookmark in my 'To Do' list Posted by: Ian3665 (4 ratings) (Software buyer rating 10) Non-action Ratio: Very Good - 0.00% Buyer Security Verifications: Unverified Approved on: Oct 27, 2001 6:11:10 AM EDT Bidding Closes: Nov 15, 2001 6:13:07 AM EDT Viewed (by coders): 359 times Phase: 100% of work completed and accepted. Coder has been paid. Max Accepted Bid: Bidding is closed Project Type: Personal Project / Homework Help Bidding Type: Open Auction Categories: Language Specific, Testing / Quality Assurance, Platforms, Other, UNIX Enter chat room for this bid request (0 active users at Jul 12, 2003 9:42:07 AM EDT) Description: Please visit http://www.cs.ucf.edu/courses/cop3402/lab4.txt Deliverables: Complete and fully-functional working program(s) in executable form as well as complete source code of all work done. Special Conditions / Other: Deadline is Nov. 18 Remember that contacting the other party outside of the site (by email, phone, etc.) on all business projects < $500 (before the buyer's money is escrowed) is a violation of both the software buyer and seller agreements. We monitor all site activity for such violations and can instantly expel transgressers on the spot, so we thank you in advance for your cooperation. If you notice a violation please help out the site and report it. Thanks for your help.   Bidding/Comments: All monetary amounts on the site are in United States dollars. Rent a Coder is a closed auction, so coders can only see their own bids and comments. Buyers can view every posting made on their bid requests. See all rejected bids (and all comments) Name   Bid Amount    Date   Coder Rating   Chris Hixon (2 ratings) in Boulder, Colorado United States Bid id: 41,745   $30 (USD) Oct 29, 2001 10:18:03 PM EDT  10 (Excellent)     I've used lex/yacc for several things: parsers, simple programming languages, etc. I could probably do this in an hour or so after digging up some old source code. I'll include good comments to help you learn.           See 5 private reply(ies) to/from Chris Hixon.