Spot the bug (three line program) and a question on how to order execution flow in a OOP
- From: raylopez99 <raylopez99@xxxxxxxxx>
- Date: Mon, 24 Sep 2007 16:42:20 -0700
Spot the bug (hint: case sensitive).
Gave me an infinite loop, and drove me nuts (lost over an hour finding
it). This sort of stuff should IMO be caught by the compiler.
/*
private int ccUsrInputArrLength;
public int CcUsrInputArrLength
{ get { return CcUsrInputArrLength; } }
*/
Now another question: how's the best way to order how your OOP will
execute? I have a bunch of methods, and they have to execute in a
particular order.
Right now, I just comment each method saying "run this method first/
second/third" etc.
Is there a more rigorous way (for code maintenance)?
RL
.
- Follow-Ups:
- Re: Spot the bug (three line program) and a question on how to order execution flow in a OOP
- From: raylopez99
- Re: Spot the bug (three line program) and a question on how to order execution flow in a OOP
- From: Mads Bondo Dydensborg
- Re: Spot the bug (three line program) and a question on how to order execution flow in a OOP
- From: Peter Duniho
- Re: Spot the bug (three line program) and a question on how to order execution flow in a OOP
- From: Doug Semler
- Re: Spot the bug (three line program) and a question on how to order execution flow in a OOP
- From: Tom Dacon
- Re: Spot the bug (three line program) and a question on how to order execution flow in a OOP
- From: Tom Dacon
- Re: Spot the bug (three line program) and a question on how to order execution flow in a OOP
- Prev by Date: Re: Tidy up blank methods
- Next by Date: FrontPage and c#
- Previous by thread: Re: Sending a struct to embeded CPU over the Ethernet
- Next by thread: Re: Spot the bug (three line program) and a question on how to order execution flow in a OOP
- Index(es):
Relevant Pages
|