16 messages in com.mysql.lists.plusplusRe: Visual C++
FromSent OnAttachments
Keith MacDonald29 Nov 2000 03:45 
Bruce E. Wells29 Nov 2000 07:20 
luc...@mach8.nl29 Nov 2000 07:27 
Thimble Smith29 Nov 2000 09:52 
Jupiter Punungwe29 Nov 2000 10:29 
Keith MacDonald29 Nov 2000 11:01 
Keith MacDonald29 Nov 2000 11:08 
Jacques Huard29 Nov 2000 11:42 
luc...@mach8.nl29 Nov 2000 11:51 
Jupiter Punungwe30 Nov 2000 02:13 
Florian G. Pflug30 Nov 2000 17:06 
Don Thompson30 Nov 2000 23:32 
Keith MacDonald01 Dec 2000 02:27 
Florian G. Pflug01 Dec 2000 16:20 
Keith MacDonald02 Dec 2000 03:32 
Jupiter Punungwe02 Dec 2000 04:48 
Subject:Re: Visual C++
From:Jupiter Punungwe (punu@yahoo.com)
Date:11/29/2000 10:29:54 AM
List:com.mysql.lists.plusplus

----- Original Message ----- From: Keith MacDonald <kei@textpad.com> To: <plus@lists.mysql.com> Sent: Wednesday, November 29, 2000 1:45 PM Subject: Visual C++

The decision to adopt MySQL++ as the official C++ API is commendable, but why make it so difficult to use with Visual C++? The choice of .cc and .hh as file name extensions is an absolute barrier to even getting started, so I wonder if they were chosen wilfully!

You may criticise the fact that Visual C++ (including version 7.0 beta 1) only recognises .c, .cpp, .h and .hpp, but it is the most productive software development tool that I have ever used, and there are probably more people using it than the free compilers.

If you really are planning to make MySQL++ work with other SQL databases, why not rename its source files now, to minimize the number of users that are inconvenienced?

Hey Keith have you ever heard of the commands

ren *.hh *.hpp

ren *.cc *.cpp

Anyway I wonder what your problem is. Any good compiler can include any file

#include <whatever.hh> works exactly the same way as #include <whatever.hpp> or #include <whatever.xqj> provide the contents of the included files are the same.

Besides MySQL is a database PRIMALY developed on Linux/Unix systems and is open source so the naming conventions are PRIMARILY for people with that background.

I haven't used MySQL++ but if it meets the ANSI standards then the problem is with Visual C++ and not MySQL++

Forget about Visual C++.