Re: Connection::connect() interface is changing

Warren Young schrieb:

> I've given up on the reordering change that can cause silent breakage.
>
> But you must accept that I do intend to break things. If I am not
> allowed to break anything, there's no point to v3.

No problem with that, but if you break it, make it obvious.

>> Personally, I even think it is no good to have default parameters for 
>> setting up connections at all: this is something where I always want 
>> the developper to better think twice than just proceed using the 
>> default values.

Why not have different interfaces for the different implementations?

Make the default (and possibly copy-) constructor private and have factory methods as public interface, like:

static Connection Connection::connectTCP ( host, user, port, ... );
static Connection Connection::connectNamedPipe ( ... );
static Connection Connection::connectDomainSocket ( ... );

Then use like this:
Connection con = Connection::connectTCP(...);

Or create a new connection factory class for this.

Axel

-- 
MySQL++ Mailing List
For list archives: 
http://lists.mysql.com/plusplus
To unsubscribe:    
http://lists.mysql.com/plusplus?unsub=lists@pantek.com

Do you need help?

In addition to our free technical library, Pantek provides professional IT services to companies who utilize Open Source software: Learn more about Pantek's Technical Support offerings Place an order for 24/7/365 Technical Support here Learn more about Pantek, who we are, and what we do Chat with a Live Operator Related lists.mysql.com Links announce benchmarks bugs certification cluster commits dotnet gui-tools internals java maxdb myodbc mysql mysqldoc packagers perl plusplus replication win32 Request more information about Pantek