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:Keith MacDonald (kei@textpad.com)
Date:11/29/2000 11:08:46 AM
List:com.mysql.lists.plusplus

Hey Keith have you ever heard of the commands

ren *.hh *.hpp ren *.cc *.cpp

Will that help with the #include's within those *.cc and *.hh files, or with keeping up to date with each new release of MySQL++?

- Keith MacDonald

-----Original Message----- From: Jupiter Punungwe [mailto:punu@yahoo.com] Sent: Wednesday, November 29, 2000 6:30 PM To: Keith MacDonald; plus@lists.mysql.com Subject: Re: Visual C++

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++.