Re: glib-tml-980819-0.patch
- From: "Michael T. Smith" <michael csuite ns ca>
- To: Gtk+ Developers <gtk-devel-list redhat com>
- Subject: Re: glib-tml-980819-0.patch
- Date: Fri, 21 Aug 1998 09:13:03 -0300 (ADT)
On Fri, 21 Aug 1998, Tor Lillqvist wrote:
> Hmm, what is lcc-win32 and where do I get it ?
It's Jacob Navia's free compiler, http://www.cs.virginia.edu/~lcc-win32/
> Yes, but isn't the problem here that g_log_default_handler should work
> even if stdio has been seriously damaged by lack of memory? Isn't
> that's why it uses straight system calls on Unix? (Or is it the case
> that if you are this seriously out of memory on Windows, something is
> screwed up and you will have to reboot anyway, so we could as well
> just try fprintf...:-))
I hadn't thought of that. But if you're that seriously out of memory on
Windows, yes, you'll have to reboot. ;) I don't think stdio is any
more/less vulnerable than AllocConsole, but I could be wrong.
However there are a few other problems with stdio: I can't remember the
specifics but for some reason printf doesn't work before/within main
window creation (at least with lcc-win32 and CRTDLL). Plus, g_debug is
probably writing to stderr anyway, so it should probably try to open a
messagebox instead of a console.
Personally I'd like to see GTK+ apps under Win32 not opening a console
window.
----
Michael Smith, michael@csuite.ns.ca
Technical Support, Central Region
Nova Scotia Community Access Program
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]