On Mon, Aug 27, 2001 at 10:32:03AM +0400, Alexander V. Lukyanov wrote:
> On Fri, Aug 24, 2001 at 03:58:58PM -0400, Glenn F. Maynard wrote:
> > these things periodically, but good data is scarce. (Some ex-Windows *NIX
> > programmers are still avoiding internal for() variable scoping!)
>
> It is
On Fri, Aug 24, 2001 at 03:58:58PM -0400, Glenn F. Maynard wrote:
> these things periodically, but good data is scarce. (Some ex-Windows *NIX
> programmers are still avoiding internal for() variable scoping!)
It is still unportable. Sometimes I receive reports that lftp cannot be
compiled with s
if you want it, just yell,
> and I'll throw it somewhere ;-)
>
> It will sure need some fixes to match your exact need, but I'm sure you
> won't have to rewrite everything.
I'll probably look for something with the same interface as C++ strings,
so we can switch over
> On Wed, Jul 25, 2001 at 04:25:31PM +0400, Alexander V. Lukyanov wrote:
> > A simple string class can be useful. But passing it by value can be costly.
> > I think much of c++ bloat goes from that.
>
> Well, most of the time it's passed by reference (const string &); more often, the
> cost is te
On Wed, Jul 25, 2001 at 04:25:31PM +0400, Alexander V. Lukyanov wrote:
> A simple string class can be useful. But passing it by value can be costly.
> I think much of c++ bloat goes from that.
Well, most of the time it's passed by reference (const string &); more often, the
cost is temporaries du
On Wed, 25 Jul 2001, Alexander V. Lukyanov wrote:
> On Tue, Jul 24, 2001 at 06:30:00PM -0400, Glenn F. Maynard wrote:
> > Why not introduce some sort of string class into lftp? It's understandable
> A simple string class can be useful. But passing it by value can be costly.
> I think much of c+
On Tue, Jul 24, 2001 at 06:30:00PM -0400, Glenn F. Maynard wrote:
> Why not introduce some sort of string class into lftp? It's understandable
> to avoid system STL and C++ strings (they're taking absurdly long to actually
> become implemented well outside of g++), b
xfree(cur_pwd);
cur_pwd = xstrdup(job->pwd);
}
(And again for lpwd.)
Why not introduce some sort of string class into lftp? It's understandable
to avoid system STL and C++ strings (they're taking absurdly long to actually
become implemented well outside of g++), but it'd p