Program Real Line Counter. Anyone want to jump in?

[bplus]

Well unless anyone else has anything missed to add, I think this cake is backed. I like method #2 best, but I haven't speed tested them. Too me, QB64 handles these types a text functions so fast, it really doesn't make much of a difference.

Now, if nothing more gets added, we just need some beta tests to see if anything can be broke or simply doesn't function as expected.

Pete

I'm a bit bemused by all of this... why is it important to know how many lines it can be broken down into? Does this have a bearing on a programmes's speed, or usefulness, or memory-useage? Surely the file size and design can tell you what you need to know?

1) It's parsing, which makes it fun.

2) Practical use: Contests.

Once in a blue moon someone will put together a contest. Maybe write a pong game in 100 lines or less. Maybe even fewest lines wins. Anyway, colons make it possible to place many statements on a single line. Parsing out the colons, which serve that purpose, makes judging the actual lines used to code the program quantifiable.

Pete

Like I always say, "Don't take it parsenally!"

Now what you need to work on is a QB64PE-Merge program which recursively loads all $INCLUDE files and then saves the whole program as a singular BAS file for total line count, quick reference, formatting, and debugging purposes. 

Ha! I am jumping in today because what I would like to do is rewrite MasterGY's 89 IDE lines with 20 blank lines but 85 colons to 174 IDE lines without all the dang colons, so I might begin to study the thing.

So that would be the use of this little excursion.

Steve makes a good point about counting lines in includes. Using include for my GUI experiment was not really helpful but then I was still working on the Include code.

So the cake may be baked but I haven't gazed upon it frosted.

Oh I missed Old Moses post, yes it is interesting how many actual LOC it took to do something or what some function costs in LOC.

Isn't it a sign of a smart coder to get something done with less LOC and not taking off points for blank lines and comments.