Welcome, Guest. Please login or register.

Author Topic: C vs C++ ... or whatever language  (Read 21035 times)

Description:

0 Members and 1 Guest are viewing this topic.

Offline Kronos

  • Resident blue troll
  • Hero Member
  • *****
  • Join Date: Feb 2002
  • Posts: 4017
    • Show all replies
    • http://www.SteamDraw.de
Re: C vs C++ ... or whatever language
« on: February 17, 2018, 05:33:05 PM »
GCC obviously.

You could also go with StormC which might have been a MaxonC derivate from V1 to V3 and was GCC based in V4.
1. Make an announcment.
2. Wait a while.
3. Check if it can actually be done.
4. Wait for someone else to do it.
5. Start working on it while giving out hillarious progress-reports.
6. Deny that you have ever announced it
7. Blame someone else
 

Offline Kronos

  • Resident blue troll
  • Hero Member
  • *****
  • Join Date: Feb 2002
  • Posts: 4017
    • Show all replies
    • http://www.SteamDraw.de
Re: C vs C++ ... or whatever language
« Reply #1 on: February 19, 2018, 11:32:20 AM »
Quote from: nicholas;836255
SAS/C 7.01 supports a subset of C++ too.

http://aminet.net/package/dev/c/expsascxx


You obviously never tried to compile C++ with that.

I did, on an 68030 with 7MB (4MB on the A2630,2MB Z2 and 1MB CHIP).

It might be somewhat useable with today's resources (NG or UAE) ....



.... for compiling and running........
1. Make an announcment.
2. Wait a while.
3. Check if it can actually be done.
4. Wait for someone else to do it.
5. Start working on it while giving out hillarious progress-reports.
6. Deny that you have ever announced it
7. Blame someone else
 

Offline Kronos

  • Resident blue troll
  • Hero Member
  • *****
  • Join Date: Feb 2002
  • Posts: 4017
    • Show all replies
    • http://www.SteamDraw.de
Re: C vs C++ ... or whatever language
« Reply #2 on: February 19, 2018, 04:58:37 PM »
Quote from: nicholas;836307

SAS/C 7 ran fine under MorphOS on my PowerBook last time I tried (circa 2013) .


C or C++?

Compiling C with SAS on an 68030 was just fine in 199x.
Compiling C++ with Storm on an 68030 was just fine in 199x.
Compiling C++ with SAS on an 68030 was just useless in 199x.

SAS C++ isn't really a compiler but a preprocessor taking ages to create oversized C code.
SAS C then compiled that code into bloated object code (again taking ages).
1. Make an announcment.
2. Wait a while.
3. Check if it can actually be done.
4. Wait for someone else to do it.
5. Start working on it while giving out hillarious progress-reports.
6. Deny that you have ever announced it
7. Blame someone else