Eddie Lascu <[EMAIL PROTECTED]> wrote: > My sample method is a strip-down version of what I have in reality. My real > method does more than just promoting the state (the application implements a > parser). The method returns a boolean to signal whether everything went > smoothly inside. Reference parameters, including a StringBuilder that > constructs an error message in case something goes bad, are passed in.
I know you're not asking for advice, but if it were me, I'd put all the ref arguments into a class, and I'd throw an exception if there was an error. For recursive descent parsers with error recovery to detect more syntax errors later on in the token stream, you want the unwind behaviour anyway. -- Barry -- http://barrkel.blogspot.com/ =================================== This list is hosted by DevelopMentor® http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com
