![]() For example, I could have easily said something like, add my AlphaImage control OCX to your project, and provide only 2 needed lines: load & render. Then you see code with multiple executions on the same line, continuation character to extend lines, calling class/modules methods, etc, etc. Kinda like "who can come up with a 1 liner for this or that?". But this isn't a 'challenge' I participate in, there are no rules. Please don't perceive this as aggression rather than the fun sidebar I thought it was dll wrapper for my apis', for now let's just say it should have no relation to the procedure code any more than your API and type declares do) (although we could also dispute whether an extremely diverse general-purpose thing like oleexp counts as a special-purpose module à la 'i made a. So I'm not counting the underlying way GDI+ is accessed, I'm counting the actual procedure. Your code uses those declares directly, mine goes through an interface that ultimately uses them. Both image display procedures depend on GDI+. I suppose I could count the lines to define those interfaces, but that's not really the point.Įdit: Since I'm sure the comment is coming, I'll clarify a little further. Your code depends on a bunch of GDI+ APIs, mine depends on an interface definition in a TLB. I said less lines of code in-procedure, your LoadPNG vs. What I'm saying is that interface definitions in TLB are the same as depending on a bunch of "Declare Function.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |