On Seg, 2006-03-06 at 18:00 +, Gustavo J. A. M. Carneiro wrote:
> On Seg, 2006-03-06 at 08:27 -0500, Michael Sweet wrote:
> > Alexander Larsson wrote:
> > > On Fri, 2006-03-03 at 13:59 -0500, Morten Welinder wrote:
> > >> What's the status of thread safety? Last I looked at cups it was
> > >>
John (J5) Palmieri wrote:
...
The eggcupsutils stuff is just wrapping the CUPS APIs to manage the
whole request, including authentication, but it doesn't expose
enough to allow an event-driven (think select() or poll() on the FD)
application to "do the right thing" for truly asynchronous operati
On Seg, 2006-03-06 at 08:27 -0500, Michael Sweet wrote:
> Alexander Larsson wrote:
> > On Fri, 2006-03-03 at 13:59 -0500, Morten Welinder wrote:
> >> What's the status of thread safety? Last I looked at cups it was
> >> not thread safe due to calling setlocale, and there was little
> >> understand
Michael Sweet wrote:
>> The approach to conflicts is: Remove all choices that conflict with the
>> default settings in the InstallableOptions group, since we don't show
>> these options (that is up to the system configuration tool). For
>> conflicts between normal settings we show a warning icon ne
On Sat, 2006-03-04 at 13:07 -0500, Michael Sweet wrote:
> John (J5) Palmieri wrote:
> > ...
> > That would be great. I would say eggcupsutils.c should be looked at
> > closely and perhaps can be reworked to become part of the CUPS library
> > itself. It provides a generic async framework for POST
On Mon, 2006-03-06 at 10:03 -0500, Michael Sweet wrote:
> > The unfortunate effect is that sscanf is not going to be useful
> > for a library. Unless you are willing to fork() but that comes
> > with its own set of problems.
>
> Well, fuck, so much for the CUPS 1.2 beta release today...
This is
On Mon, 2006-03-06 at 09:55 -0500, Michael Sweet wrote:
> >> OK, sounds reasonable, but I predict that users will be asking why
> >> they can't see those options... :)
> >
> > We'll just have to make sure the system print admin dialog is easy to
> > use and easy to find.
>
> ... with some way for
Morten Welinder wrote:
The man page for setlocale() says nothing about thread safety, but
given how all of the other standard C calls work I'm frankly shocked
that setting the locale in one thread affects the others. Is this
just a bug on Linux, or is it a general problem on other operating
syst
Alexander Larsson wrote:
On Mon, 2006-03-06 at 08:14 -0500, Michael Sweet wrote:
Alexander Larsson wrote:
On Sat, 2006-03-04 at 12:27 -0500, Michael Sweet wrote:
ppd_text_to_utf8() leaks memory for UTF-8 encoded text - you can
set encoding to a constant string there, too!
I don't see the lea
On Mon, 2006-03-06 at 08:14 -0500, Michael Sweet wrote:
> Alexander Larsson wrote:
> > On Sat, 2006-03-04 at 12:27 -0500, Michael Sweet wrote:
> >
> >> ppd_text_to_utf8() leaks memory for UTF-8 encoded text - you can
> >> set encoding to a constant string there, too!
> >
> > I don't see the leak.
> The man page for setlocale() says nothing about thread safety, but
> given how all of the other standard C calls work I'm frankly shocked
> that setting the locale in one thread affects the others. Is this
> just a bug on Linux, or is it a general problem on other operating
> systems?
Solaris'
On Mon, 2006-03-06 at 08:27 -0500, Michael Sweet wrote:
> The man page for setlocale() says nothing about thread safety, but
> given how all of the other standard C calls work I'm frankly shocked
> that setting the locale in one thread affects the others. Is this
> just a bug on Linux, or is it a
Alexander Larsson wrote:
On Fri, 2006-03-03 at 13:59 -0500, Morten Welinder wrote:
What's the status of thread safety? Last I looked at cups it was
not thread safe due to calling setlocale, and there was little
understanding as to why that was a problem.
(And recall that just about any gtk+ pr
Alexander Larsson wrote:
On Sat, 2006-03-04 at 12:27 -0500, Michael Sweet wrote:
ppd_text_to_utf8() leaks memory for UTF-8 encoded text - you can
set encoding to a constant string there, too!
I don't see the leak. It just returns a strdup of the passed in text
(which is supposed to be freed b
On Fri, 2006-03-03 at 13:59 -0500, Morten Welinder wrote:
> What's the status of thread safety? Last I looked at cups it was
> not thread safe due to calling setlocale, and there was little
> understanding as to why that was a problem.
>
> (And recall that just about any gtk+ program is at least
On Sat, 2006-03-04 at 12:27 -0500, Michael Sweet wrote:
> ppd_text_to_utf8() leaks memory for UTF-8 encoded text - you can
> set encoding to a constant string there, too!
I don't see the leak. It just returns a strdup of the passed in text
(which is supposed to be freed by callers).
> I think yo
Adriano skrev:
Hello people,
I'm a mac user type and I'm trying to build Gtk on Mac because I hope
I can contribute some code to help integrate it on Mac.
That's great news!
Probably the things I'm gonna ask are basic to you, but that's that
Unix stuff I'm not familiar with. Please understa
17 matches
Mail list logo