Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[sev]

I wish I knew what the f*ck you lot are on about :-/

 

lol....the thermal paper.....marvelous stuff.

Used to put sheets of it on the girls chairs at uni and over about half an hour it would give an imprint of thier arse.....what a sad life we led at the time!

  That... is a thing of beauty...

[BazMV6]

You youngsters...    I'm writing ALGOL today.  

[TheBoy]

Done C as well - but not a lot, but enough to maintain C programs and write routines in it.

Worst languages and 4GLs, tried Progress - very restrictive, Visual Basic has a very nasty IDE.

The dbase interactive environments are rubbish compared to the compilers.

Before getting a job I learnt COBOL, BASIC, some XBASE

The non .net versions were kinda hampered by trying to be familiar to users of previous versions, which itself was kinda hampered by the VB for DOS product (actually rather good, but quirky interface).

VB's biggest problem was the mess it got in tryinging to kludge new ideas into a language not really geared to take it - sterling effort by MS, but was never going to be truely achieveable, hence VB.NET being very, very different.


Sadly, I still have to maintain a medium size VB6 app that can't port to .net - and VB6 has just gone out of support.  Fortunately, as the runtimes are included in XP and Vista, they continue to get security fixes...

[Jay w]

i still have an unbuilt ZX81 in storage....managed to get 2 of then in the 80's i built one and left the other

[cem_devecioglu]

Done C as well - but not a lot, but enough to maintain C programs and write routines in it.

Worst languages and 4GLs, tried Progress - very restrictive, Visual Basic has a very nasty IDE.

The dbase interactive environments are rubbish compared to the compilers.

Before getting a job I learnt COBOL, BASIC, some XBASE

The non .net versions were kinda hampered by trying to be familiar to users of previous versions, which itself was kinda hampered by the VB for DOS product (actually rather good, but quirky interface).

VB's biggest problem was the mess it got in tryinging to kludge new ideas into a language not really geared to take it - sterling effort by MS, but was never going to be truely achieveable, hence VB.NET being very, very different.

Sadly, I still have to maintain a medium size VB6 app that can't port to .net - and VB6 has just gone out of support.  Fortunately, as the runtimes are included in XP and Vista, they continue to get security fixes...

yep..  VB.NET very different.. in prev version you can write codes in n  similiar to the speed you write a normal document..development is really quick..

for .NET you need serious planning .. But once you finish I have seen the same code working 40-50 times faster

and also porting VB6 apllications very hard to nearly imposible in terms of project time..As most objects are changed and classes being very different..

But still I like vb6, very fast to develop for a specific task..And still many programmers prefer ..

[TheBoy]

Done C as well - but not a lot, but enough to maintain C programs and write routines in it.

Worst languages and 4GLs, tried Progress - very restrictive, Visual Basic has a very nasty IDE.

The dbase interactive environments are rubbish compared to the compilers.

Before getting a job I learnt COBOL, BASIC, some XBASE

The non .net versions were kinda hampered by trying to be familiar to users of previous versions, which itself was kinda hampered by the VB for DOS product (actually rather good, but quirky interface).

VB's biggest problem was the mess it got in tryinging to kludge new ideas into a language not really geared to take it - sterling effort by MS, but was never going to be truely achieveable, hence VB.NET being very, very different.

Sadly, I still have to maintain a medium size VB6 app that can't port to .net - and VB6 has just gone out of support.  Fortunately, as the runtimes are included in XP and Vista, they continue to get security fixes...

yep..  VB.NET very different.. in prev version you can write codes in n  similiar to the speed you write a normal document..development is really quick..

for .NET you need serious planning .. But once you finish I have seen the same code working 40-50 times faster

and also porting VB6 apllications very hard to nearly imposible in terms of project time..As most objects are changed and classes being very different..

But still I like vb6, very fast to develop for a specific task..And still many programmers prefer ..

with .net 2005 and 2008, vb6 generally important well ime, in so much as you have a functioning app.  It will take some tidying up to make it more ".net like", but will work.

It all goes Pete Tong when you drive certain bits of (some homemade some commercial) hardware directly

[cem_devecioglu]

Done C as well - but not a lot, but enough to maintain C programs and write routines in it.

Worst languages and 4GLs, tried Progress - very restrictive, Visual Basic has a very nasty IDE.

The dbase interactive environments are rubbish compared to the compilers.

Before getting a job I learnt COBOL, BASIC, some XBASE

The non .net versions were kinda hampered by trying to be familiar to users of previous versions, which itself was kinda hampered by the VB for DOS product (actually rather good, but quirky interface).

VB's biggest problem was the mess it got in tryinging to kludge new ideas into a language not really geared to take it - sterling effort by MS, but was never going to be truely achieveable, hence VB.NET being very, very different.

Sadly, I still have to maintain a medium size VB6 app that can't port to .net - and VB6 has just gone out of support.  Fortunately, as the runtimes are included in XP and Vista, they continue to get security fixes...

yep..  VB.NET very different.. in prev version you can write codes in n  similiar to the speed you write a normal document..development is really quick..

for .NET you need serious planning .. But once you finish I have seen the same code working 40-50 times faster

and also porting VB6 apllications very hard to nearly imposible in terms of project time..As most objects are changed and classes being very different..

But still I like vb6, very fast to develop for a specific task..And still many programmers prefer ..

with .net 2005 and 2008, vb6 generally important well ime, in so much as you have a functioning app.  It will take some tidying up to make it more ".net like", but will work.

It all goes Pete Tong when you drive certain bits of (some homemade some commercial) hardware directly

as usual..

my woriies are mostly API usage in vb6 as most of those are for win2000 and xp.. if windows 7 changed some APIs we need a long work..

And I'm not planning to rewrite those codes again unless somebody pay (which I dont expect)

[Kevin Wood]

It all goes Pete Tong when you drive certain bits of (some homemade some commercial) hardware directly

That's where the BBC model B comes in, surely?

Kevin

[TheBoy]

It all goes Pete Tong when you drive certain bits of (some homemade some commercial) hardware directly

That's where the BBC model B comes in, surely?

Kevin

might look a bit crap in my brother's shops if his tills were beebs...  ...i also reckon a ms-sql client might be difficult to obtain

[Martin_1962]

Done C as well - but not a lot, but enough to maintain C programs and write routines in it.

Worst languages and 4GLs, tried Progress - very restrictive, Visual Basic has a very nasty IDE.

The dbase interactive environments are rubbish compared to the compilers.

Before getting a job I learnt COBOL, BASIC, some XBASE

The non .net versions were kinda hampered by trying to be familiar to users of previous versions, which itself was kinda hampered by the VB for DOS product (actually rather good, but quirky interface).

VB's biggest problem was the mess it got in tryinging to kludge new ideas into a language not really geared to take it - sterling effort by MS, but was never going to be truely achieveable, hence VB.NET being very, very different.


Sadly, I still have to maintain a medium size VB6 app that can't port to .net - and VB6 has just gone out of support.  Fortunately, as the runtimes are included in XP and Vista, they continue to get security fixes...

VB 6 - I had edited a lot of the .bas in an external editor, for power reasons, then reloaded and VB screwed all my formatting .

I ended up rewriting to change all the variable names to the same length.

All the decent xbases short cut on statements (to be faster), pretty sure C does as well, does VB no it doesn't

IF a or b and if a passes still does b ect aghhhhhhhhhhhhhhh!!!!!!!!!!

Really shitty language

When I converted a load of code to produce some data routines it took days!

First time I had changed language and had to change structure of these routines. (Locking control ect, ported all over the place VB was worst) Oh I do like the Clipper dialect!

[Martin_1962]

Hmmm data - I love Advantage Database Server.

We are investigating environments for our next project which will be (deleted because our competitors might read) but sticking with CA-VO and VC++ for the current product

[TheBoy]

Done C as well - but not a lot, but enough to maintain C programs and write routines in it.

Worst languages and 4GLs, tried Progress - very restrictive, Visual Basic has a very nasty IDE.

The dbase interactive environments are rubbish compared to the compilers.

Before getting a job I learnt COBOL, BASIC, some XBASE

The non .net versions were kinda hampered by trying to be familiar to users of previous versions, which itself was kinda hampered by the VB for DOS product (actually rather good, but quirky interface).

VB's biggest problem was the mess it got in tryinging to kludge new ideas into a language not really geared to take it - sterling effort by MS, but was never going to be truely achieveable, hence VB.NET being very, very different.


Sadly, I still have to maintain a medium size VB6 app that can't port to .net - and VB6 has just gone out of support.  Fortunately, as the runtimes are included in XP and Vista, they continue to get security fixes...

VB 6 - I had edited a lot of the .bas in an external editor, for power reasons, then reloaded and VB screwed all my formatting .

I ended up rewriting to change all the variable names to the same length.

All the decent xbases short cut on statements (to be faster), pretty sure C does as well, does VB no it doesn't

IF a or b and if a passes still does b ect aghhhhhhhhhhhhhhh!!!!!!!!!!

Really shitty language

When I converted a load of code to produce some data routines it took days!

First time I had changed language and had to change structure of these routines. (Locking control ect, ported all over the place VB was worst) Oh I do like the Clipper dialect!

Pre .net variants did suffer a messy, inconsistent langauge, due to its history.  Still a lot of apps run on it though, including some big-ish websites. Its done a great job, but old style VB should be retired (or used for scripting as .vbs).

[Martin_1962]

Our last surviving VB app is hated by everyone for maintenance, if a rewrite gets required it will end up in Visual Objects quicker than anything.

[TheBoy]

Our last surviving VB app is hated by everyone for maintenance, if a rewrite gets required it will end up in Visual Objects quicker than anything.

simply as thats what you're used to.

[Martin_1962]

Our last surviving VB app is hated by everyone for maintenance, if a rewrite gets required it will end up in Visual Objects quicker than anything.

simply as thats what you're used to.

Looks like a mix between C++ and Clipper!