Compiler / Interpreter ???
Moderator: Board moderators
-
- Experienced poster
- Posts: 202
- Joined: Fri Mar 22, 2002 2:00 am
- Location: Chittagong. CSE - CUET
- Contact:
Compiler / Interpreter ???
Hi!
Here most of the users are C/C++ users. The number of PASCAL and Java users is coming little slowly but strongly. And now this poll is to know which compiler/interpreters the most problem solvers use. Note, I have said problem solvers not software developers! As there are many well-known IDE for developers that we usually don
Here most of the users are C/C++ users. The number of PASCAL and Java users is coming little slowly but strongly. And now this poll is to know which compiler/interpreters the most problem solvers use. Note, I have said problem solvers not software developers! As there are many well-known IDE for developers that we usually don
We are all in a circular way, no advances, only moving and moving!
Just like you have said, beginners use Turbo C++, I normally code using Turbo C++ but I am slowly moving on to VC++.
Indeed you are right about the version 6.0 of VC++ we use which can be troublesome at some time.
Here is another problem with VC++
[cpp]
#include<string>
#include<iostream.h>
using namespace std;
int main()
{
string str;
cin>>str;
cout<<str;
}
[/cpp]
This fragment never compiles in VC++ 6.0, but is compiled by the UVA compiler.
As for the contest goes, i normally code in Turbo C++ since it is better to debug (char *) using Turbo C++ and VC++ when I need STL.
Indeed you are right about the version 6.0 of VC++ we use which can be troublesome at some time.
Here is another problem with VC++
[cpp]
#include<string>
#include<iostream.h>
using namespace std;
int main()
{
string str;
cin>>str;
cout<<str;
}
[/cpp]
This fragment never compiles in VC++ 6.0, but is compiled by the UVA compiler.
As for the contest goes, i normally code in Turbo C++ since it is better to debug (char *) using Turbo C++ and VC++ when I need STL.
-
- Experienced poster
- Posts: 202
- Joined: Fri Mar 22, 2002 2:00 am
- Location: Chittagong. CSE - CUET
- Contact:
Oh! Reallyabiczo wrote:A workaround for the scope bug:
[cpp]
#define for if(0); else for
[/cpp]
Put this somewhere near the top of your source file, and 'for' will behave as it should.
I think as we have seen GNU C++ is error free and supported by the contest systems....then we can rely on this.........and typical windows users can use cygwin, I think it's fine
But if you people can find any bugs please notify us...of course these are useful things
We are all in a circular way, no advances, only moving and moving!
-
- Experienced poster
- Posts: 202
- Joined: Fri Mar 22, 2002 2:00 am
- Location: Chittagong. CSE - CUET
- Contact:
Oh! Not really! But we are developing a contest system like this "online-judge.uva.es". You may say it a project/survey for that!Arnold wrote:Moni,is it thesis work?
Besides, is it not important to know the limitations of the compilers we use?
We are all in a circular way, no advances, only moving and moving!
-
- Learning poster
- Posts: 54
- Joined: Sun Oct 28, 2001 2:00 am
- Location: Bangladesh
-
- Learning poster
- Posts: 54
- Joined: Sun Oct 28, 2001 2:00 am
- Location: Bangladesh
I think the g++ is the most frequently updated one.
I think the latest version of g++ 3.2 or 3.3.
I don't know about VC 7.0 as I haven't used it.
But don't plan on using every feature that g++ 3.2 supports.
The OJ uses g++ but a somewhat older version. They don't
update it so frequently as does the linux community.
I think gcc is the version of g++ which only supports C. I'm
not sure though. But whether my code is pure C or C++, I
always compile it using g++.
I'm not also sure if g++ latest version completely supports
the latest STL standard. But I'm pretty much sure that the
version OJ uses do not support the latest STL standard.
May be some wise guy would like to confirm my guesses.
I think the latest version of g++ 3.2 or 3.3.
I don't know about VC 7.0 as I haven't used it.
But don't plan on using every feature that g++ 3.2 supports.
The OJ uses g++ but a somewhat older version. They don't
update it so frequently as does the linux community.
I think gcc is the version of g++ which only supports C. I'm
not sure though. But whether my code is pure C or C++, I
always compile it using g++.
I'm not also sure if g++ latest version completely supports
the latest STL standard. But I'm pretty much sure that the
version OJ uses do not support the latest STL standard.
May be some wise guy would like to confirm my guesses.
-
- New poster
- Posts: 9
- Joined: Fri Feb 20, 2004 6:48 am
- Location: India
- Contact:
Judge Compiler
That's right
g++ version 3.2 and the newer g++ 3.3 have features not supported by judge.
Judge uses g++/gcc 2.96
luckily my institution uses the same compiler.
So in theory atleast I should get no "Compiler Error"
g++ version 3.2 and the newer g++ 3.3 have features not supported by judge.
Judge uses g++/gcc 2.96
luckily my institution uses the same compiler.
So in theory atleast I should get no "Compiler Error"
-
- Guru
- Posts: 834
- Joined: Wed May 29, 2002 4:11 pm
- Location: Wroclaw, Poland
- Contact:
I code in MS VC++ with all its advantages and disadvantages
Before that I coded in BC 3.1 and I think, that was very good compiler
A word about scope bug in VC++ (this in for statement): I think that Java behave the same - after the loop i variable is still in scope ... but maybe I'm wrong. I don't check C/C++ specification, but I think, that declaring variables in any place is very nice, but code is cleaner when we declare it in one place.
And about second bug:
This compiles on my computer very well - I don't try to execute it, but compiles with no error So maybe you shamim has some misconfigurations in compiler ?? I use VC++ 6.0 with no SP (I think), so with better SP it should work too
BTW. your piece of code should got warning or error (no return value in main function)
Best regards
DM
Before that I coded in BC 3.1 and I think, that was very good compiler
A word about scope bug in VC++ (this in for statement): I think that Java behave the same - after the loop i variable is still in scope ... but maybe I'm wrong. I don't check C/C++ specification, but I think, that declaring variables in any place is very nice, but code is cleaner when we declare it in one place.
And about second bug:
Code: Select all
#include <string>
#include <iostream> // removing .h
using namespace std;
int main(void)
{
string s;
cin >> s;
cout << s;
return 0;
}
BTW. your piece of code should got warning or error (no return value in main function)
Best regards
DM
If you really want to get Accepted, try to think about possible, and after that - about impossible ... and you'll get, what you want ....
Born from ashes - restarting counter of problems (800+ solved problems)
Born from ashes - restarting counter of problems (800+ solved problems)