Where's the -1 go? (Not another troll question)

"Rothenmaier, Deane C." <[email protected]> Fri, 5 Aug 2011 13:34:23 +0000
Newsgroups gmane.comp.lang.perl.active-perl
Message-ID <115007D93766724DAE9F518846E121DE93873B@DMS-S8MP-2MB.wagresources.walgreens.local>
Geniuses, Gurus, Wizards, et. al...

I'm working on some Win32::GUI code, with no formal training, and just enough OTJ to be really dangerous.  I've come up against a couple of questions that I cannot find answers to in my books.  Here's the code:

#===============
sub Exit_Click {
#===============
   MainWindow_Terminate();
}

#=========================
sub MainWindow_Terminate {
#=========================
   print LOG "="x80 . "\n";
   close( LOG );
   return( -1 );
}

And here's the questions:
First, when Exit_Click (E_C) calls MainWindow_Terminate (MW_T), it does nothing with the -1 that MW_T returns-or at least it looks that way (it is GUI, after all, and I'm learning that GUI does a lot of, um, "invisible" stuff). So where does that -1 go? Into the bit bucket? Or does GUI do some behind-the-curtain prestidigitation with it?  If this wasn't GUI code, I'd feel confident believing that it's just ignored. But it is. So I don't.

Second: Is there some GUI-related requirement behind E_C calling MW_T instead of doing, in its own code, the stuff MW_T does? That is, is there something in the murky depths of Win32::GUI that's expecting a "thing" called Exit_Click to call another "thing" called MainWindow_Terminate?

Thanks for sharing your wisdom.

Deane Rothenmaier
Programmer/Analyst - IT-StdCfg
Walgreens Corp.
2 Overlook Point #N51022D
MS 6515
Lincolnshire, IL 60069
224-542-5150

Vincit qui patitur. -- Persius

_______________________________________________
ActivePerl mailing list
[email protected]
To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs