Anyone Here With Turbo Pascal Experience?


Recommended Posts

Turbo Pascal

Original authorAnders Hejlsberg (at Borland)

DeveloperBorland

Release20 November 1983; 42 years ago[1][2]

Operating systemCP/M, CP/M-86, MS-DOS, Windows 3.x, Classic Mac OS

PlatformZ80, x86, 68000, PC-98

https://en.wikipedia.org/wiki/Turbo_Pascal

It was the one language I actually learned to program in.   I wasn't very good at it and never used it at work.   

If anyone has any personal Turbo Pascal stories or personal accomplishments using it, please take a moment to share.   Thanks. Peace

i-img1200x1200-1711132105cihbfj170226.jpg

Turbo Pascal was my first real programming experience more than 30 years ago at university. I mostly taught myself from the included examples and help documentation, because the university only taught the basic syntax and philosophy of Pascal, without going deeply into Turbo Pascal’s advanced features.

I still remember when I discovered that I could embed assembly language directly into Pascal code, call BIOS functions, manipulate screen memory, use mouse interrupts, and control peripherals from my programs. That opened huge doors for me. Programming back then felt really fun, direct, and close to the machine.

What I loved about Pascal was its readability and the almost instant compile time. Turbo Pascal was an amazing environment, but unfortunately Turbo Pascal for Windows 3 did not feel like it fully carried that legacy forward. Later, Delphi got things back on the right track after the messy transition to TP for Windows.

Sadly, Delphi suffered from years of uncertainty as it moved from Borland to CodeGear and then to Embarcadero. That instability made many developers lose confidence in it, even though Delphi itself remained a powerful and productive tool.

I still work with Delphi from time to time, but I definitely miss the old days of Turbo Pascal.

  • Like 3

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • In the boot options in the UEFI is set to legacy or CMS? It needs to be set to UEFI if it's not already.
    • Researchers claim Microsoft's quantum breakthrough is flawed by basic Python errors by Karthik Mudaliar Microsoft's aggressive roadmap to deliver a commercial quantum supercomputer by 2029 has now hit a bit of a snag, and it's not because of a complex sub-zero dilution refrigerator, but rather because of a few lines of basic Python code. A new critique published in the scientific journal Nature argues that simple software errors effectively manufactured the breakthrough that Microsoft's foundational research claimed back in 2025 into Majorana-based topological qubits. Topological quantum computing, the path that Microsoft chose for its research, relies on creating and controlling "Majorana zero modes." These are exotic quasiparticles that theoretically offer vastly superior error resistance compared to the highly sensitive superconducting qubits currently being championed by rivals like Google and IBM. However, physically proving you have created these particles requires sifting through massive amounts of complex electrical conductance data to isolate a specific "topological gap." Because of the sheer volume of data, physicists rely heavily on custom software pipelines to process the results. This is where the Python scripts come in. Now, according to the critique, Microsoft’s data processing software contained fundamental programming errors that ultimately skewed the published results. By mishandling data arrays or deploying incorrect logic within the Python script, the software supposedly discarded "noisy" or contradictory data. Which is why it only highlighted the specific electrical measurements that supported the topological-gap claim. The researchers behind the critique argued that this makes the findings invalid, suggesting the heralded "quantum leap" was actually a false positive generated by bad code and not a product of groundbreaking physics. However, Microsoft is pushing back hard against these allegations. The Redmond giant has formally rejected the criticism, saying that it's just a minor anomaly rather than a fatal flaw. According to the company, while there may have been a minor oversight in the data parsing scripts, it does not alter the fundamental reality of their physical experiment. Just weeks ago, Microsoft unveiled the Majorana 2 quantum processor, a milestone so significant that the company boldly accelerated its timeline for a commercial quantum supercomputer from 2035 down to 2029. But the new software allegations reopen an old wound. Microsoft's quantum division faced a remarkably similar crisis when a landmark 2018 paper on Majorana particles was famously retracted in 2021 after independent physicists discovered the data had been inappropriately cropped. That historical baggage makes the current Python-related allegations particularly sensitive. If the foundational math and data processing for the 2025 breakthrough are genuinely flawed, the highly anticipated 2029 commercial timeline could easily be delayed or, worse, cancelled.
    • Because of what they have done to VMware I will never buy anything Broadcom again.
  • Recent Achievements

    • Dedicated
      Scoobystu earned a badge
      Dedicated
    • First Post
      Tom Schmidt earned a badge
      First Post
    • One Month Later
      D0nn13 earned a badge
      One Month Later
    • Rookie
      +ChiefOfNeo went up a rank
      Rookie
    • One Year In
      Tom Schmidt earned a badge
      One Year In
  • Popular Contributors

    1. 1
      +primortal
      465
    2. 2
      +Edouard
      177
    3. 3
      PsYcHoKiLLa
      123
    4. 4
      Michael Scrip
      82
    5. 5
      Xenon
      76
  • Tell a friend

    Love Neowin? Tell a friend!