"If you haven't noticed, most languages are based off of C. Therefore it is improper syntax because it isn't close to C. "
:eek:
I never realized a language was bad because it is different
Printable View
"If you haven't noticed, most languages are based off of C. Therefore it is improper syntax because it isn't close to C. "
:eek:
I never realized a language was bad because it is different
VB's biggest problem has always been that it attracts so many hack coders. Being accessible has its drawbacks. A lot of the disrespect is enhanced by so much junky code and dumb questions asked.
C for that matter was essentially a misbegotten hybrid of Fortran, Algol, and PDP-8 assembly language. There is little there that you could call innovative.
The original strength of the language was that as a low-level language the compiler could be tiny. Because of its origins in a regulated monopoly (AT&T) compilers spread widely for free or nearly so.
Small and free compilers were probably the main reason C became so popular. Even Microsoft gives away its C and C++ compiler.
One thing that annoys me is that VB still uses "End", etc which, is the improper way to go about closing your program. I can't remember if c, c++ or c# have that problem or not?
You can easily do the same thing in most compiled languages. For Windows this boils down to a call on ExitProcess before you've cleaned things up.
Yeah, but encouraging bad practice that is not a smart way to go about things.
This is the equivalent code in Delphi/Lazarus:Quote:
Originally Posted by Nightwalker83
Code:Application.Terminate;
I only use End by accident....when I accidentally delete the word following it, such as Sub or Function. Of course, the compiler catches that pretty quickly as it pretty well wrecks the code. I don't believe that anybody encourages the use of End to exit applications, so it is just an item that is there. Kind of the dirty laundry of the language, like GoTo.
C-style languages sure are popular. How unfortunate that such an archaic syntax should be so highly prized.
I personally don't think it's the 'job' of the language to discourage bad practice. The language should let you do pretty much anything you want. It's the job of the programmer to use the tools in his arsenal apropriately.
To bring up a recent debate, I don't think VB6 was wrong to support On Error Resume Next. I do think, on the other hand, that a developer is almost certainly wrong to use it. Although if the developer knows what they're doing, understands the cost and why it's considered a bad practice and still has a valid and justifiable reason to use it, then go ahead. They should expect to be challenged on it though.
I once had a conversation with a hardware programmer who thought VB6 was "Bad" because it was too easy. You've gotta love that kind of conceipt.
And compared to human languages?Quote:
Originally Posted by kayleigh
No! It's the job of the person/people developing the language to discourage bad practice... Take English for example... it's an absolute joke how some people use it and those are only the person that have English as their first language. :lol:Quote:
Originally Posted by FunkyDexter
END and GOTO just point out the "scripting" nature of the language from it's earlier days - mainframe days. COBOL has the "STOP RUN" commabd.
Think about it for a second - this all started on paper-based hardware - you sat at a READY PROMPT and entered RUN PROGRAMNAME to start the application (if it was compiled).
When all we had is interpretted versions of BASIC you had to LOAD your program into memory - or type it in line by line.
BASIC was an answer to COBOL when I started coding in the late 1970's. COBOL had commands that were several keywords long - everything was "literal" ("ADD YEARS TO AGE" is a real command). BASIC introduced "symbolic" representation - you could actually use a + and - sign to do math.
Just because C looks great in a railroad diagram - with every path clearly defined...
I still use GOTO in T-SQL STORED PROCEDURES - it's required in a scripting language. Not everything is about proper loops and what not. Loops are more of the unnatural thing to have in a scripting language. GOTO doesn't create spaghetti-code - it's just highly used in spaghetti-code.
I use this code in a splash screen to tell if I'm in the IDE - is this bad use of VB?
Code:On Error Resume Next
Debug.Print 1 / 0
gDebugMode = (Err.Number <> 0)
Er, no.Quote:
Originally Posted by szlamany
There is nothing "scripting" about VB, or Basic in general for that matter.
While the earliest Basics as well as many recent ones are interpreted instead of compiled, that doesn't make them "scripting" either. And if it does then all .Net languages as just as "scripting" or more so!
And for that matter look at VBScript, which is a scripting language. No "End" and no "Go To" in the language at all unless you count the single vestigial instance it has for VB-compatibility On Error GoTo 0 meaning "turn off structured error handling."
Basic was never "an answer to Cobol" (nobody spells these with all-caps anymore, they are names now not acronyms). It was "an answer to" Fortran actually, and intended for use by non-programmers. It dates to the mid 1960s.
It later became popular because it was easy to learn and small interpreters could be written for early personal computers. It's popularity grew because of the established user base and the lack of an alternative: Pascal never caught on, C was meant to be a harder to use low-level language. What else was left?
My first 20 years in computers were all DEC mini's - PDP-11's and VAX'es.
I have never seen any application code ever written on any of these hardware systems that was not either BASIC of COBOL.
All consultants and employees came in one or both of those areas...
The blue cross/blue shield health insurance type companies still use those machines with code written in COBOL.
So I meant BASIC vs COBOL just as a point in my own employment history...
You have now. :D Back when I was working for Turbitrol (early '80's) we were writing FORTRAN IV and DEC Assembly on the PDP 11/44 under RSX/11M. We also had a few mini VAX systems around but I never got 'round to working with those. Some of our field machines were smaller PDP11's.Quote:
Originally Posted by szlamany
-Max
That RSX was realtime stuff - right?
I never went there - only did applications for student and financial administration.
Same old DB app's I'm still doing today - in Javascript with jQuery.
jQuery is so cool - and interestingly enough the book I read to get in deep with the inner workings was written by Yehuda Katz who worked for DEC from 1979 to 1993 and was part of the team that built DECforms.
Small world...
Yup. I was working on a water/wastewater treatment system at the time. Pretty cool stuff. We would hang an RTU (Remote Telemetry Unit) on just about anything you wouldn't want to stick your hand into. My part of the system was called SIG (Signal Definition Subsystem) which defined the RTU points to the central system.Quote:
Originally Posted by szlamany
-Max
Fo' shizzle! I'm totally down with that.Quote:
Originally Posted by Nightwalker83
Strangely worked on a banking application that utilised GOTO due to it being quicker for transaction process than GOSUB .... RETURN. A lot of top down coding involved :) Wasn't a vb app btw.Quote:
Originally Posted by Shaggy Hiker