[Licq-devel] ** LOW COST SOFTWARE DEVELOPMENT **

2002-06-04 Thread BrainCoders.com
Title: BrainCoders.com - Low Cost Software Development   | About Us  |  Services  |  Staff  |  Workflow  | Contact Us | Outsourcing Advantages | FAQ |   Dear Internet User, The eBusiness is changing the software applications and services landscape in a way that has

[Licq-devel] why CICQDaemon::PushPluginSignal is protected?

2002-06-04 Thread Juan F. Codagnone
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 as i said before i am cleaning the fifo code. almost all the fifo commands calls to public functions like icqSetStatus() To call only public function from fifo command is the right thing(tm). Fifo acts as an "external program" Soany tip to writ

Re: [Licq-devel] why CICQDaemon::PushPluginSignal is protected?

2002-06-04 Thread Tim van Erven
On Tue, Jun 04, 2002 at 12:28:21PM -0300, "Juan F. Codagnone" <[EMAIL PROTECTED]> wrote: > as i said before i am cleaning the fifo code. > > almost all the fifo commands calls to public functions like icqSetStatus() > To call only public function from fifo command is the right thing(tm). Fifo >

Re: [Licq-devel] why CICQDaemon::PushPluginSignal is protected?

2002-06-04 Thread Juan F. Codagnone
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tuesday 04 June 2002 13:01, Tim van Erven wrote: > > Just move the PushPluginSignal bits into two new public functions? that is why i am asking. design by necessity is not a nice thing. - -- Buenos Aires, Argentina -BEGIN PGP SIGNATURE-

[Licq-devel] Licq and contact list

2002-06-04 Thread Julian Terziev
Hello, I have a problem with Licq, when I log to the ICQ, a can not recieve automaticaly contact list, and can not see my friends. ICQ 2001 for Windows make this. When I log, I recieve all contact list from ICQ servers and when I go to other PC, without contact list I recieve from ICQ servers

Re: [Licq-devel] why CICQDaemon::PushPluginSignal is protected?

2002-06-04 Thread Tim van Erven
On Tue, Jun 04, 2002 at 01:24:15PM -0300, "Juan F. Codagnone" <[EMAIL PROTECTED]> wrote: > On Tuesday 04 June 2002 13:01, Tim van Erven wrote: >> >> Just move the PushPluginSignal bits into two new public functions? > > that is why i am asking. design by necessity is not a nice thing. Yes, com

Re: [Licq-devel] why CICQDaemon::PushPluginSignal is protected?

2002-06-04 Thread Tim van Erven
On Tue, Jun 04, 2002 at 08:38:30PM +0200, Tim van Erven <[EMAIL PROTECTED]> wrote: > On Tue, Jun 04, 2002 at 01:24:15PM -0300, "Juan F. Codagnone" ><[EMAIL PROTECTED]> wrote: >> On Tuesday 04 June 2002 13:01, Tim van Erven wrote: >>> >>> Just move the PushPluginSignal bits into two new public fu

Re: [Licq-devel] why CICQDaemon::PushPluginSignal is protected?

2002-06-04 Thread Juan F. Codagnone
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tuesday 04 June 2002 15:38, Tim van Erven wrote: > On Tue, Jun 04, 2002 at 01:24:15PM -0300, "Juan F. Codagnone" <[EMAIL PROTECTED]> wrote: > > On Tuesday 04 June 2002 13:01, Tim van Erven wrote: > >> Just move the PushPluginSignal bits into two n

Re: [Licq-devel] why CICQDaemon::PushPluginSignal is protected?

2002-06-04 Thread Juan F. Codagnone
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 > Bad things > o Due the generic argument parser, quoting is nessesary for > phrases. >| this break compatibility So.. its a good time to decide wheter this can be done or i go back to the if - else if - ... - else code structure. -

Re: [Licq-devel] why CICQDaemon::PushPluginSignal is protected?

2002-06-04 Thread Tim van Erven
On Tue, Jun 04, 2002 at 04:40:07PM -0300, "Juan F. Codagnone" <[EMAIL PROTECTED]> wrote: > The new code is much cleaner. > As it is today i can say: > > Good things > o improved design: each fifo command is as an C program (easy to > | mantain) (argv, argc interface) > o

Re: [Licq-devel] why CICQDaemon::PushPluginSignal is protected?

2002-06-04 Thread Juan F. Codagnone
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tuesday 04 June 2002 17:40, Tim van Erven wrote: > I'm curious, what's the benefit of separate C programs over functions > in this case? With functions you can still do the standard argument > parsing and clean design, but without the extra overh

[Licq-devel] about the use of strerror

2002-06-04 Thread Juan F. Codagnone
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 `man 3 strerror' says: The strerror_r() function is similar to strerror(), but is thread safe. It returns the string in the user-supplied buffer buf of length n. ~/src/licq/cvs/src$ grep strerror *.cpp|wc -l 33 - -- B

Re: [Licq-devel] about the use of strerror

2002-06-04 Thread Nick Pilon
On June 4, 2002 6:14 pm, Juan F. Codagnone wrote: > ~/src/licq/cvs/src$ grep strerror *.cpp|wc -l > 33 I believe grep strerror still matches strerror_r. Might grep strerror[^_] be a better pattern to use? -- Nick Pilon "I want a battalion of Stealth Elephants!" __

Re: [Licq-devel] Licq and contact list

2002-06-04 Thread Adam Young
On Tue, 4 Jun 2002 21:08:37 -0200 Julian Terziev <[EMAIL PROTECTED]> wrote: > Hello, > > I have a problem with Licq, when I log to the ICQ, a can not recieve > automaticaly contact list, and can not see my friends. > ICQ 2001 for Windows make this. When I log, I recieve all contact list > from

Re: [Licq-devel] about the use of strerror

2002-06-04 Thread Juan F. Codagnone
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tuesday 04 June 2002 18:16, Nick Pilon wrote: > On June 4, 2002 6:14 pm, Juan F. Codagnone wrote: > > ~/src/licq/cvs/src$ grep strerror *.cpp|wc -l > > 33 > > I believe grep strerror still matches strerror_r. Might grep > strerror[^_] be a bet

[Licq-devel] GTK+LICQ authors?

2002-06-04 Thread Robin Cook
Are the authors of gtk+licq still reading this list? CuZnDragon Robin Cook ___ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm _

SV: [Licq-devel] GTK+LICQ authors?

2002-06-04 Thread Mattias Eriksson
Yes we are //Snaggen > -Ursprungligt meddelande- > Från: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]] För Robin Cook > Skickat: den 5 juni 2002 03:54 > Till: licq-devel > Ämne: [Licq-devel] GTK+LICQ authors? > > > Are the authors of gtk+licq still reading this list? > > CuZnD