Sign Up
All NU.DE helps you connect and share with the people in your life.

I was asked today, did I make Modern Pascal to help evolve the Pascal language, or was I writing it to revolt on the direction others had taken their products; like Delphi and GNU Pascal for example?

The answer is honestly so simple, I had developed a JavaScript interpreter for Delphi in 2000. It was not originally written to be a plugin to David Baldwin's PBear THTML components - however, its design would have allowed it to snap-in without too much headache. Instead, it was written to support modification at the host level, just like the original JavaScript language was written to provide modification at the client (web browser) level.

Now, when I say Host, obviously I am using a vague and more encompassing word than the Delphi Application. As DXJavaScript was also designed to be an ISAPI and Apache Module, so you could leverage Microsoft's IIS Web Server and the Apache Web Server as the host, and DXJavaScript as the language - much the same way as PHP works. This to me was obvious, single source, two ends of the connection - Client and Server.

The company I was working for during the day did embrace it, CODY Computer Systems, Inc. in Pottstown Pennsylvania. A law enforcement software development company, saw we could use it to hide fields based upon security, change the labels of fields to make our product support other industry phrases, even change screen colors for night and day mode. We built a curriculum and certified IT/Dev/Ops people how to use and implement, or even share their designs. They were using it to develop rules for Reports, someone even had the imagination to use it so their Report Designer Screens could become as input forms for reports.

I travelled to Houston in 2002 and 2003 to promote both my Socket Suite (DXSock) and my JavaScript Plug-in (DXJavaScript) to Delphi developers. Unfortunately, my Socket Suite stole the show - and the audience down played DXJavaScript as "of a script engine". My personal software company at the time, Brain Patchwork DX, LLC. was struggling, as my partners in Italy had been bought up by Siemens and they were not too focused on marketing the product.

By 2004, I was ready to announce and share DXJavaScript's sibling Modern Pascal, originally called DXPascalWebScript as I was coding it any time I was sitting at my house - which wasn't a lot, as I worked 80 to 120 hours a week for CODY (literally working around the clock for days, which later in life I am physically paying for). January 2005, I quit my job, for many personal reasons, but this gave light to new opportunities. I was able to develop a commercial Academia search engine entirely in my Pascal Compiler - As I could shave off 30ms to 50ms of run-time by using the p-code instead of parsing the source every execution. The p-code concept made my compiler much more like JavaC, the compiler for Java.

During the first 4 years of developing what becomes known as Modern Pascal, I had focused on backward compatibility. I had added a few minor extensions, even the next 2 years, I focused on 64bit support. It wasn't until 2007 when I started adding GUI support to the RTL Framework that I realized the more C frameworks I worked with the more I had to reformat C to Pascal - the languages are much alike, it is the syntax the separates the Red from the Black, and I decided my Pascal dialect would support it without me really promoting it - as I knew the "Gods of old" would fight me on saying this was still Pascal.

Early 2007, I released my first GUI Application built using my Pascal compiler. A simple Checkbook/Invoicing application - much like Quickbooks. The source was 98% true Turbo Pascal compliant, however, all of the GUI code was a hybrid of C and Pascal. This was the first time, I was delighted in what I had been coding for 7 years, enough to release the app and started telling everyone it was written in "My hybrid pascal compiler".

I would spend the next 2 years writing applications to see what else does my product need before I start getting customers. This was the period where the RTL Framework (what used to be a clone of TURBO.TPL from Turbo Pascal), started to grow and become more like .net's robust Framework.

So, by 2009 my hybrid Pascal Compiler was like a growing version of Java and .Net, however, instead of making a C parser vs a Pascal parser, I would extend my Pascal to incorporate what I considered logic extensions/improvements to the Pascal language. The product would not become known as Modern Pascal until 2014, when it hit me - my Pascal syntax versus what others refer to as "PASCAL", was more Modern. So, I bought the domain Modern Pascal, and started building ground-up tutorials. I was not of the mindset to simply release "Here is what I do different", I felt like Modern Pascal needs full documentation, tutorials and demonstrations as if no one had ever seen the language before.

Personally, I think of Modern Pascal as the next step in the evolutionary chain for Pascal. I am not worried about chasing C# or Delphi, instead producing a MOP to clean-up the mess between Turbo Pascal and Delphi. The industry lost a great many amazing Pascal developers that either did not want to learn a new paradigm or did not have anyone to help bridge the gap from DOS/Turbo Pascal and GUI/Delphi. So my focus will be, making Modern Pascal bridge that gap on as many platforms and environments as one man can do.

Ozz
Captcha Challenge
Reload Image
Type in the verification code above