|
Yes, just one of the many "features" that relegates python to a 'fast food' language. What's not a 'fast food' language - Tcl\Tk
Net: Take a look at Tcl and then you will asking yourself "Why does python even exist?"
|
|
|
|
|
This single feature has held me back from investing time into this language.
Doing some RCA my opinion is that technology like language generators has promoted the creation of marginally different quite a few languages—so called jvm languages —
There was php and Perl. Anyone not intellectually lazy and a bit more egoless would have perfected php instead of whipping up a new language with brain dead features. Not sure python space or dos backslash takes the top spot for an epoch of productivity killer. Backslash inventor now admits that is his worst decision.
|
|
|
|
|
More python indention confusion ???
# Python program to check if the input number is prime or not
num = 15
# take input from the user
# num = int(input("Enter a number: "))
# prime numbers are greater than 1
if num > 1:
for i in range(2,num):
if (num % i) == 0:
print(num,"is not a prime number")
print(i,"times",num
break
else:
#print(num % i)
print(num,"is a prime number")
# if input number is less than
# or equal to 1, it is not prime
else:
print(num,"is not a prime number")
What the heck is that else: statement doing out there, who does it belong to?
|
|
|
|
|
I experienced this when Python 3 was released. Is this a Python 2 throw-back other than the semi-colon Python 3 wants?
"Courtesy is the product of a mature, disciplined mind ... ridicule is lack of the same - DPM"
|
|
|
|
|
Check this out: CODE - Apply for a position Visual FoxPro Dev[^]
Posting says: We have multiple offerings for this position and will consider candidates who seek full-time employment or contracting opportunities.
When I read that, my eyes bugged out of my head.
According to wikipedia[^] :
Final release of Visual FoxPro was
v9.0 SP2[1] / October 16, 2007; 11 years ago
Wow!
|
|
|
|
|
I spent 15+ years doing FoxPro and Visual FoxPro. At one time it was a powerful language. The advent of .Net spelled the beginning of the end of VFP.
If it's not broken, fix it until it is.
Everything makes sense in someone's mind.
Ya can't fix stupid.
|
|
|
|
|
Kevin Marois wrote: I spent 15+ years doing FoxPro and Visual FoxPro.
Would it be interesting to you now? Or is it so old that it'd be terrible?
Just curious.
Also, maybe there is some $$$ for you to make?
|
|
|
|
|
I'm not really interested. There are conversion jobs out there, but I'm plenty busy doing .Net
If it's not broken, fix it until it is.
Everything makes sense in someone's mind.
Ya can't fix stupid.
|
|
|
|
|
I started with VFP and VB6 back in the day. Wow!! I feel so old.
|
|
|
|
|
Slacker007 wrote: I feel so old. Tell me about it. I started with FoxPro before it was "Visual".
v2.0 I think...
The Beer Prayer - Our lager, which art in barrels, hallowed be thy drink. Thy will be drunk, I will be drunk, at home as it is in the tavern. Give us this day our foamy head, and forgive us our spillage as we forgive those who spill against us. And lead us not to incarceration, but deliver us from hangovers. For thine is the beer, the bitter and the lager, for ever and ever. Barmen.
|
|
|
|
|
I wrote a Foxpro for DOS service application - not an app kiddies, for the computer service company I worked for in 1990 ish When Windows 3.0 was hot.
I don't just feel old but am.
|
|
|
|
|
Mike Mullikin wrote: v2.0 I think
Me too!
I started with FoxPro 2.0 and my first computer job was maintaining the Lawn Doctor Business System written in that language in 1994. It was the system that Lawn Doctor franchisees used to run their businesses.
The difficult we do right away...
...the impossible takes slightly longer.
|
|
|
|
|
Me too, started with the DOS version of FoxPro and the fun began when the first Windows version came out, my god what a load of crap !
|
|
|
|
|
The largest liquidation in the world so far used Foxpro for its claim and payments systems. I wrote some of them and maintained existing ones. Used properly it was a great little language. Visual Foxpro was even better but short lived due to DOTNET. Rick Strahl once commented , if someone says it can't be done in Foxpro, there's a good chance he doesn't know what he's talking about.
We can’t stop here, this is bat country - Hunter S Thompson RIP
|
|
|
|
|
There is still a demand for Cobol Developers[^] - and I had hoped that died in the early eighties ...
Well, if I'm honest, I'd hoped it had died before they taught it to us right at the beginning of my CS degree course in 1977.
Sent from my Amstrad PC 1640
Never throw anything away, Griff
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
I must be weird , I enjoyed my COBOL days.
We can’t stop here, this is bat country - Hunter S Thompson RIP
|
|
|
|
|
So did I - until I met a different language (FORTRAN, but anything would have done I suspect) and realised how bad it actually was ...
Sent from my Amstrad PC 1640
Never throw anything away, Griff
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
Bad as in ?
We can’t stop here, this is bat country - Hunter S Thompson RIP
|
|
|
|
|
It's wordy, very wordy. IIRC "Hello World" was about 40 punched cards...
It lacks everything a "modern" language needs: user defined functions for a start!
Sent from my Amstrad PC 1640
Never throw anything away, Griff
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
Ah the joyous
IDENTIFICATION DIVISION.
PROGRAM-ID. HELLO-WORLD.
* simple hello world program
PROCEDURE DIVISION.
DISPLAY 'Hello world!'.
STOP RUN.
You could remove the PROGRAM-ID. HELLO-WORLD. line and shrink it to 39 cards
We can’t stop here, this is bat country - Hunter S Thompson RIP
|
|
|
|
|
From the little I remember...wasn’t it column based too? Like commands had to start in specific columns or the compiler didn’t even see them?
It was so non-REPL too. You had to write an entire program, ship it off to the mainframe, wait and then check the green-lined paper to determine what even went on.
|
|
|
|
|
Ah yes the error report ( regardless of whether there were any errors )
We can’t stop here, this is bat country - Hunter S Thompson RIP
|
|
|
|
|
A friend of mine recently landed a new gig, so I asked about it.
First question, what technologies do they use?
His answer was rather unexpected... "Mainly COBOL.NET[^]"
Apparently, you can compile COBOL to MSIL and even run it in Azure, but why anyone would ever want that is beyond me
In their case they sort of "upgraded" (if you can call it that) some old COBOL applications.
Their new services were all Java (no, not Java.NET or COBOL.jar )
|
|
|
|
|
|
I'm afraid COBOL programmers will roam the earth longer than dinosaurs have, or at least COBOL will
|
|
|
|