Author Topic: ScriptO2  (Read 245 times)

0 Members and 1 Guest are viewing this topic.

John

  • Hero Member
  • *****
  • Posts: 3150
ScriptO2
« on: May 30, 2018, 08:54:33 PM »
I've decided to get the ball rolling and get ScriptO2 version 1.0 assembled. The first version will use existing O2 / DLLC resources and will be a name change / repackaging job. I will setup a public BitBucket repository for the project. My hope is Mike will find this interesting and contribute.

I plan to use libscriba (SB in a DLL) which should make version 1.0 of ScriptO2 about 50 KB.
« Last Edit: May 30, 2018, 10:08:31 PM by John »

John

  • Hero Member
  • *****
  • Posts: 3150
Re: ScriptO2
« Reply #1 on: June 02, 2018, 11:25:05 AM »
Update

It looks like I'm going alone on this effort to merge Script BASIC with O2. The good news is ScriptO2 already exists, just has too much junk in the trunk in it's current form.

I'm unfortunately extremely busy with real life projects so this will be a labor of love when I find a moment.

John

  • Hero Member
  • *****
  • Posts: 3150
Re: ScriptO2
« Reply #2 on: June 12, 2018, 12:45:25 AM »
ScriptO2 offers everything that Script BASIC does plus the following O2 features.
  • JIT virtual DLL functions and subs that are multi-line strings in your program.
  • FFI with dynamic definitions with low level COM support.
  • BSTR, WIDE with ASCII conversation.
  • Define / access C structures In memory via a pointer. (peek/poke too)
  • Access to the interpreters functions/subs and variables from O2 code.

I plan to include the SWIG to DLLC FFI definition utility with SciptO2 1.0.
« Last Edit: June 12, 2018, 12:59:17 PM by John »

Mike Lobanovsky

  • Admin Support Member
  • *****
  • Posts: 1849
Re: ScriptO2
« Reply #3 on: June 12, 2018, 04:45:26 PM »
BSTR, WIDE with ASCII conversation.

Mmm... WCHAR?.. Conversion?..

Quote
... SciptO2 1.0.

Shouldn't there be some ScriptO2 0.1 first just for starters?
Mike
(3.6GHz Intel Core i5 Quad w/ 16GB RAM, 2 x nVidia GTX 650Ti w/ 2GB VRAM, Windows 7 Ultimate Sp1)

John

  • Hero Member
  • *****
  • Posts: 3150
Re: ScriptO2
« Reply #4 on: June 12, 2018, 05:45:28 PM »
That should have been BSTR to SB string conversion.

Going for 1.0 might be slightly aggressive.
« Last Edit: June 12, 2018, 06:10:47 PM by John »

John

  • Hero Member
  • *****
  • Posts: 3150
Re: ScriptO2
« Reply #5 on: June 15, 2018, 11:59:08 PM »
With the speed of today's computers, what type of applications justify using ASM? (via O2)

When I run Scipt BASIC code I'm seeing microsecond execution speeds. Most apps aren't rotating pinecones but doing data entry and reporting. Have we exceeded fast and it's now a moot point?

Personally, I see O2 shinning as an interpretive language booster until it matures and isn't so low level.
« Last Edit: June 16, 2018, 12:10:48 AM by John »

John

  • Hero Member
  • *****
  • Posts: 3150
Re: ScriptO2
« Reply #6 on: June 16, 2018, 10:52:15 AM »
The advantage of using O2 as SB's extension API rather than the existing C API is you can extend your code dynamically at ASM speeds using milti-line O2 code text strings in your SB script.

I'm reserving the C extension API for integrating open source popular libraries.
« Last Edit: June 16, 2018, 11:21:53 AM by John »

John

  • Hero Member
  • *****
  • Posts: 3150
Re: ScriptO2
« Reply #7 on: June 17, 2018, 08:48:47 AM »
Script BASIC is a comfortable set of clothes O2 can wear now until it stops growing and starts wearing its own.
« Last Edit: June 17, 2018, 09:22:12 AM by John »

John

  • Hero Member
  • *****
  • Posts: 3150
Re: ScriptO2
« Reply #8 on: June 17, 2018, 10:05:00 PM »
Quote from: Mike
So how can your SB elaborations help the O2 developer or user's immediate needs?

It lets the user frame out their project in SB and externally enhance it using O2 JIT, dynamic FFI or the SB C extension API.