My programming knowledge ends at about turbo c++ 3.1 for dos. I'm wanting to get caught up with the times.

what would be the most practical next language for this day and age?

Visual Basic? , Borland Builder ?

my community collage offers a these and a few others, and suggestions to lead me in the correct direction would be very much apreshiated.

Thanks
-c1

---
þ Synchronet þ Vertrauen þ Home of Synchronet þ telnet://vert.synchro.net

Re: what next?
By: Creative1 to All on Fri Mar 16 2007 04:53 pm

My programming knowledge ends at about turbo c++ 3.1 for dos. I'm wanting to get caught up with the times.

what would be the most practical next language for this day and age?

Visual Basic?

This isn't considered a serious language or development tool by software developers.

Borland Builder

This is a C/C++ development environment for Win32.

my community collage offers a these and a few others, and suggestions to lea me in the correct direction would be very much apreshiated.

Go with C/C++. The development environment doesn't matter much unless you're looking to do GUI development (in which case, I'd recommend Borland C++ Builder).

digital man (xbox-live: digitlman)

Snapple "Real Fact" #58:
A sneeze travels out of your nose at 100mph.
Norco, CA WX: 62.6øF, 72% humidity, 0 mph N wind, 0.00 inches rain/24hrs

---
þ Synchronet þ Vertrauen þ Home of Synchronet þ telnet://vert.synchro.net

Re: what next?
By: Digital Man to Creative1 on Sat Mar 17 2007 08:38 am

my community collage offers a these and a few others, and suggestions to me in the correct direction would be very much apreshiated.

Go with C/C++. The development environment doesn't matter much unless you're looking to do GUI development (in which case, I'd recommend Borland C++ Builder).

So brush up / take the advanced classes for c/c++ and then builder is an enviornment to learn for developing windows apps and a good next step?

Thanks for the response.

-c1

---
þ Synchronet þ Vertrauen þ Home of Synchronet þ telnet://vert.synchro.net

my community collage offers a these and a few others, and suggestions to me in the correct direction would be very much apreshiated.

Go with C/C++. The development environment doesn't matter much unless you're looking to do GUI development (in which case, I'd recommend Borland C++ Builder).

Do you have any thoughts on Watcom/Open Watcom ?

(I use it because that's what Scott Dudley used).


---
þ Synchronet þ Vertrauen þ Home of Synchronet þ telnet://vert.synchro.net

Re: what next?
By: Hostile to Digital Man on Sat Apr 07 2007 03:36 pm

my community collage offers a these and a few others, and suggestions me in the correct direction would be very much apreshiated.

Go with C/C++. The development environment doesn't matter much unless you looking to do GUI development (in which case, I'd recommend Borland C++ Builder).

Do you have any thoughts on Watcom/Open Watcom ?

It's okay. I used to use it a lot back in the Synchronet for OS/2 days, but not so much any more.

(I use it because that's what Scott Dudley used).

Now that Borland and Microsoft have free C/C++ compilers, there's not much incetive (for me) to use Watcom for anything. Watcom was a good cross-compiler (e.g. you build OS/2 targets from DOS or vice versa), but since I don't run either DOS or OS/2, nor support them, that's not of much value to me now. <shrug>

digital man (xbox-live: digitlman)

Snapple "Real Fact" #95:
Squids can have eyeballs the size of volleyballs.
Norco, CA WX: 67.8øF, 57% humidity, 0 mph SE wind, 0.00 inches rain/24hrs

---
þ Synchronet þ Vertrauen þ Home of Synchronet þ telnet://vert.synchro.net

Do you have any thoughts on Watcom/Open Watcom ?

It's okay. I used to use it a lot back in the Synchronet for OS/2 days, but so much any more.

(I use it because that's what Scott Dudley used).

Now that Borland and Microsoft have free C/C++ compilers, there's not much incetive (for me) to use Watcom for anything. Watcom was a good cross-compil (e.g. you build OS/2 targets from DOS or vice versa), but since I don't run either DOS or OS/2, nor support them, that's not of much value to me now.

Cool. Thanks for your input.

I find myself a little out in the cold with Watcom sometimes, with stuff like

static void StatCmds(Inst_t * Conn, char *filename, enum CmdtTypes Cmd)

being an "Incomplete enum declaration" ...

Supposedly works for MVC :/


---
þ Synchronet þ Vertrauen þ Home of Synchronet þ telnet://vert.synchro.net

Re: what next?
By: Hostile to Digital Man on Sun Apr 08 2007 04:46 pm

static void StatCmds(Inst_t * Conn, char *filename, enum CmdtTypes Cmd)

being an "Incomplete enum declaration" ...

The enum would need to be declared first (most likely in the header file)

stat.h:
enum CmdtTypes {
fiddle
,frob
};


---
Synchronet - Jump on the Web 0.2 bandwagon!

---
þ Synchronet þ My Brand-New BBS (All the cool SysOps run STOCK!)

Re: what next?
By: Hostile to Digital Man on Sun Apr 08 2007 04:46 pm

Do you have any thoughts on Watcom/Open Watcom ?

It's okay. I used to use it a lot back in the Synchronet for OS/2 days, b so much any more.

(I use it because that's what Scott Dudley used).

Now that Borland and Microsoft have free C/C++ compilers, there's not muc incetive (for me) to use Watcom for anything. Watcom was a good cross-com (e.g. you build OS/2 targets from DOS or vice versa), but since I don't r either DOS or OS/2, nor support them, that's not of much value to me now.

Cool. Thanks for your input.

I find myself a little out in the cold with Watcom sometimes, with stuff lik

static void StatCmds(Inst_t * Conn, char *filename, enum CmdtTypes Cmd)

being an "Incomplete enum declaration" ...

Supposedly works for MVC :/

Perhaps 'enum CmdtTypes' is being defined in that scope.

digital man (xbox-live: digitlman)

Snapple "Real Fact" #17:
A hummingbird weighs less then a penny.
Norco, CA WX: 106.3øF, 23% humidity, 0 mph SSW wind, 0.00 inches rain/24hrs

---
þ Synchronet þ Vertrauen þ Home of Synchronet þ telnet://vert.synchro.net