> Looks like a major task of parsing here. Yup, I think it is going to be.
> More than > that, it branches into AI, > since it requires major sensitivity to contextual > cues. > That I don't know. > There is a better way. Writing separate programs > requires shelling out to > communicate between them. Very inflexible. I would > recommend instead that you > learn about the use of subroutines. > Well, I'd like to use them as subroutines in one big program, but to get there, I'd have to start with the smaller tasks of parsing for scores, parsing for assists, parsing for rebounds etc. Then, I'd put them all together, line them up and call them one after the other. > As you take on complex tasks, you will benefit by > writing compact, mofular > subroutines to handle processes at any particular > level of abstraction. I expect so. I'd love to be able to write a subroutine that I use over and over again for different programs. Right now, I'm at the level of writing a subroutine that is useful for a very specific task, and nothing else. I'm aware of this, and love to get to that point, but that's going to take time, perhaps even more time than I have, as this is a hobby. I struggle with this because I majored in Political Science... :) > To use > subroutines well, you of course must be comfortable > with the use of references. > That makes sense. > With these two tools available, you will be > well-equipped to taake on > object-oriented programming. I see this as the > point where you would want to > branch out to multi-file programming. I have the > feeling that by the time you > have a good solution to this problem, you may need > to develop some > representative objects, since it is not a trivial > task. > I recognize it's not trivial to me. I always thought that an experienced Perl programmer could knock it out in about a week. > > > > Then, I plan on putting them all together, either > as > > includes > > C includes, Perl uses > gotcha. Same idea though, right? But I understand there's a value in getting the terminology correct. > > into one main, > > No main in Perl, unless you define and explicitly > call it. > I know this too, which makes it difficult to talk like there is one. It's just how I think of programming as that's how I was first taught. > > or cutting and pasting them > > into one file. I expect to use a lot of regular > > expressions to parse the files, and some hashes, > > arrays, and perhaps a bit more complex data > structures > > like ArraysOfArrays, or HashesOfHashes, to store > the > > information. > > Please slow down a bit here. Not that all these > tools may not be called upon > along the way, but this point is first to define the > needed outcome, and then > choose the tools needed at any stage along the way. > The sample data you posted > included a number of different types of information, > each of which probably > calls for special handling. I don't know which of these, if any of these, data structures I might need to use. I'm just presupposing. > Have you enumerated the > specific types of > information contained? You will probably need to do > so. > Do you mean the type of information I want out of this? If so, then yes, this was one of the very first things I did. > A well-named set of subroutines can make the task > much easier. Something like-- > <snip> I agree with that. > > Does that help? > > You tell us. > yup. I'm trying to decide if I want to take a break from this specific task and get into the examples of subroutines and references in my book. On the one hand, that should give me a much better grip on them, but on the other, that's time spent that I could be using to work on my own program. I could be taking a program that I know pretty well now, and tweak it to include references and subroutines, like I've been trying to do. All of you are being very helpful though, and I'm appreciative of that. Thanks. __________________________________ Do you Yahoo!? Yahoo! Finance Tax Center - File online. File on time. http://taxes.yahoo.com/filing.html -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] <http://learn.perl.org/> <http://learn.perl.org/first-response>
