By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
424,962 Members | 1,767 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 424,962 IT Pros & Developers. It's quick & easy.

Borland C++ compiler 5.0.1 needed

P: n/a
I am looking for a copy of Borland C++ 5.0.1. I have a project at work
that was written using this version, and cannot open the project files
with a later (or an earlier) version. If you know where a copy would be
available, please let me know. Thanks!
Jun 16 '07 #1
Share this Question
Share on Google+
7 Replies


P: n/a

"Henry" <gr*******@optonline.netwrote in message
news:bc***************@newsfe12.lga...
>I am looking for a copy of Borland C++ 5.0.1. I have a project at work
that was written using this version, and cannot open the project files with
a later (or an earlier) version. If you know where a copy would be
available, please let me know. Thanks!
You may have better luck at one of borland's newsgroups.
Try the server newsgroups.borland.com - probably one of
the non tech ones.

I know that you can get free borland compilers and that you
can get a Turbo C++ download for free (BDS2006 sort of)
but I don't think you're going to find 5.01 on their download
site. If it was written at work, don't they have a copy? If not,
your likely going to have to port it to something more recent.
Jun 17 '07 #2

P: n/a

"Henry" <gr*******@optonline.netwrote in message
news:bc***************@newsfe12.lga...
>I am looking for a copy of Borland C++ 5.0.1. I have a project at work
that was written using this version, and cannot open the project files with
a later (or an earlier) version. If you know where a copy would be
available, please let me know. Thanks!
Why not create a new project in some other IDE with the source files (or
better yet, some makefiles)? Perhaps you want the exact compiler settings
and stuff that are hidden away in the proprietary project files? That's why
production code should be built with makefiles, IMO. I have 5.02 installed
on my machine still, but I don't know what good that will do ya. To actually
import to Borland's (CodeGear's) new environment, you'd probably have to
have some/all the in-between releases of C++ Builder.

John

Jun 17 '07 #3

P: n/a
We have the project files, but we did not write it - it was provided by
another group in the company, and at least part of was done off-shore.
Whoever did it originally is long gone, and just getting the source code
was a struggle all by itself. So, now that we have to update the
software, we need to be able to look at it at in detail... which means,
as I'm told, getting the compiler with which it was written.

JohnQ wrote:
>
"Henry" <gr*******@optonline.netwrote in message
news:bc***************@newsfe12.lga...
>I am looking for a copy of Borland C++ 5.0.1. I have a project at
work that was written using this version, and cannot open the project
files with a later (or an earlier) version. If you know where a copy
would be available, please let me know. Thanks!

Why not create a new project in some other IDE with the source files
(or better yet, some makefiles)? Perhaps you want the exact compiler
settings and stuff that are hidden away in the proprietary project
files? That's why production code should be built with makefiles, IMO.
I have 5.02 installed on my machine still, but I don't know what good
that will do ya. To actually import to Borland's (CodeGear's) new
environment, you'd probably have to have some/all the in-between
releases of C++ Builder.

John
Jun 17 '07 #4

P: n/a
The source code files are separate from the project file. The project file
organizes the source tree into compilation units, organizes the workspace
and the like. You can rebuild the application program(s) with another
compiler by introducing the files into the new compiler system's environment
(or use make files). It's not a "push this button" kind of thing. It sounds
like you may be in over your head a bit.

John

"Henry" <gr*******@optonline.netwrote in message
news:dS************@newsfe12.lga...
We have the project files, but we did not write it - it was provided by
another group in the company, and at least part of was done off-shore.
Whoever did it originally is long gone, and just getting the source code
was a struggle all by itself. So, now that we have to update the
software, we need to be able to look at it at in detail... which means, as
I'm told, getting the compiler with which it was written.

JohnQ wrote:
>>
"Henry" <gr*******@optonline.netwrote in message
news:bc***************@newsfe12.lga...
>>I am looking for a copy of Borland C++ 5.0.1. I have a project at work
that was written using this version, and cannot open the project files
with a later (or an earlier) version. If you know where a copy would be
available, please let me know. Thanks!

Why not create a new project in some other IDE with the source files (or
better yet, some makefiles)? Perhaps you want the exact compiler settings
and stuff that are hidden away in the proprietary project files? That's
why production code should be built with makefiles, IMO. I have 5.02
installed on my machine still, but I don't know what good that will do
ya. To actually import to Borland's (CodeGear's) new environment, you'd
probably have to have some/all the in-between releases of C++ Builder.

John
Jun 18 '07 #5

P: n/a
Actually we're not in over our heads - I gave the wrong information in
my original message. The problem isn't with project files - the problem
lies with class libraries, which changed between versions. My colleague
cannot compile the project because of compile-time errors, with messages
something like, "Function does not match the library definition." For
example, in one compiler version, there is the variable bool. The other
version (I don't remember if it's the earlier or the later version) the
variable is BOOL. In any case, the class definitions changed from
version 5.0.0 to version 5.0.1, so we are stuck. (Sorry I was mistaken
earlier.)

So, that is actually why we need the slightly later version of the
compiler. Again, if anyone can be of help, we'd greatly appreciate it.
Thank you for your responses.

JohnQ wrote:
The source code files are separate from the project file. The project
file organizes the source tree into compilation units, organizes the
workspace and the like. You can rebuild the application program(s)
with another compiler by introducing the files into the new compiler
system's environment (or use make files). It's not a "push this
button" kind of thing. It sounds like you may be in over your head a bit.

John

"Henry" <gr*******@optonline.netwrote in message
news:dS************@newsfe12.lga...
>We have the project files, but we did not write it - it was provided
by another group in the company, and at least part of was done
off-shore. Whoever did it originally is long gone, and just getting
the source code was a struggle all by itself. So, now that we have
to update the software, we need to be able to look at it at in
detail... which means, as I'm told, getting the compiler with which
it was written.

JohnQ wrote:
>>>
"Henry" <gr*******@optonline.netwrote in message
news:bc***************@newsfe12.lga...
I am looking for a copy of Borland C++ 5.0.1. I have a project at
work that was written using this version, and cannot open the
project files with a later (or an earlier) version. If you know
where a copy would be available, please let me know. Thanks!

Why not create a new project in some other IDE with the source files
(or better yet, some makefiles)? Perhaps you want the exact compiler
settings and stuff that are hidden away in the proprietary project
files? That's why production code should be built with makefiles,
IMO. I have 5.02 installed on my machine still, but I don't know
what good that will do ya. To actually import to Borland's
(CodeGear's) new environment, you'd probably have to have some/all
the in-between releases of C++ Builder.

John
Jun 21 '07 #6

P: n/a
On 2007-06-22 01:12, Henry wrote:
JohnQ wrote:
>The source code files are separate from the project file. The project
file organizes the source tree into compilation units, organizes the
workspace and the like. You can rebuild the application program(s)
with another compiler by introducing the files into the new compiler
system's environment (or use make files). It's not a "push this
button" kind of thing. It sounds like you may be in over your head a bit.

John

"Henry" <gr*******@optonline.netwrote in message
news:dS************@newsfe12.lga...
>>We have the project files, but we did not write it - it was provided
by another group in the company, and at least part of was done
off-shore. Whoever did it originally is long gone, and just getting
the source code was a struggle all by itself. So, now that we have
to update the software, we need to be able to look at it at in
detail... which means, as I'm told, getting the compiler with which
it was written.

JohnQ wrote:

"Henry" <gr*******@optonline.netwrote in message
news:bc***************@newsfe12.lga...
I am looking for a copy of Borland C++ 5.0.1. I have a project at
work that was written using this version, and cannot open the
project files with a later (or an earlier) version. If you know
where a copy would be available, please let me know. Thanks!

Why not create a new project in some other IDE with the source files
(or better yet, some makefiles)? Perhaps you want the exact compiler
settings and stuff that are hidden away in the proprietary project
files? That's why production code should be built with makefiles,
IMO. I have 5.02 installed on my machine still, but I don't know
what good that will do ya. To actually import to Borland's
(CodeGear's) new environment, you'd probably have to have some/all
the in-between releases of C++ Builder.
Actually we're not in over our heads - I gave the wrong information
in my original message. The problem isn't with project files - the
problem lies with class libraries, which changed between versions. My
colleague cannot compile the project because of compile-time errors,
with messages something like, "Function does not match the library
definition." For example, in one compiler version, there is the
variable bool. The other version (I don't remember if it's the
earlier or the later version) the variable is BOOL. In any case, the
class definitions changed from version 5.0.0 to version 5.0.1, so we
are stuck. (Sorry I was mistaken earlier.)

So, that is actually why we need the slightly later version of the
compiler. Again, if anyone can be of help, we'd greatly appreciate
it. Thank you for your responses.
First of, please don't post HTML-messages, see your newsreader's
documentation about how to fix this. Second, please don't top-post, your
replies belong below the text you are replying to (I've fixed it here).

As to your problem, if the code is important it might well be worth the
effort to "fix" it so that it compiles on a modern compiler and it might
be easier than trying to find the correct version (and getting it to
run) of Borland.

--
Erik Wikström
Jun 22 '07 #7

P: n/a
>Actually we're not in over our heads - I gave the wrong information
in my original message. The problem isn't with project files - the
problem lies with class libraries, which changed between versions. My
colleague cannot compile the project because of compile-time errors,
with messages something like, "Function does not match the library
definition." For example, in one compiler version, there is the
variable bool. The other version (I don't remember if it's the
earlier or the later version) the variable is BOOL. In any case, the
class definitions changed from version 5.0.0 to version 5.0.1, so we
are stuck. (Sorry I was mistaken earlier.)

So, that is actually why we need the slightly later version of the
compiler. Again, if anyone can be of help, we'd greatly appreciate
it. Thank you for your responses.
Is it an OWL program? Perhaps generated by the IDE wizardry? (Just curious).

Are you sure you mean "5.0.1" and not "5.01"? There seem to be all flavors
of 5.0 on ebay for $50 to $80.

John

Jun 22 '07 #8

This discussion thread is closed

Replies have been disabled for this discussion.