[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-core-devel
Subject:    kio_interface.h
From:       Matthias Ettrich <ettrich () troll ! no>
Date:       1999-12-04 17:02:29
[Download RAW message or body]


The KIOConnectionSignal class (and probably others) contain char*s in the API
all over the place.

For example:

  virtual bool put( const char *_url, int _mode, bool _overwrite, bool _resume, int _size );
  virtual bool mkdir( const char *_url, int _mode );
  virtual bool copy( const char* _source, const char *_dest );
  virtual bool copy( QStringList&_source, const char *_dest );
  virtual bool move( const char *_source, const char *_dest );
  virtual bool move( QStringList& _source, const char *_dest );

What's the point in having char* in combination with QStringList functions
other than necessary conversions from QString to const char* ? Even worse, the
code itself contains ugly strcpy calls.

Other than slowing everything down, I don't see any reason to use const char*.


Matthias

[prev in list] [next in list] [prev in thread] [next in thread]