Post Modern BASIC (Formalization and Interactivity)

[Jacko]

The link is to PDF I wrote. Not brilliant, but covers class modeling, and temporary super class attachment stack for computation inheritance based on re-scoping, and other design ideas.

https://dl.dropbox.com/u/1615413/tidy/PMB.pdf

Always keep imperative and interactivity for most in the discussion, not to mention uniqueness of the grammar.

Not another language, but a more lispy basic maybe...

Are there any primary concepts I'm missing, as I'd like not to have to backtrack to provide for such things.

[James Harris]

It initially looks good but then gets puzzling. It would help a lot if
you included examples of each syntax suggestion. Proc and end proc I'm
OK with but then you say, "Definition of static, non running, data
(variables and constants), is by making variables have the behavior of
self recall (returning the value). This is the purpose of the command
let. This command is often optional in many basics. The difference can
be easily resolved by a variable stacking it's value (in the
implementation), waiting for later information." Could you illustrate
this and other concepts with some (very brief) example code?

James

[Jacko]

https://dl.dropbox.com/u/1615413/tidy/PMB.pdf is now a little updated. The word static behaves like quote in LISP.

[Jacko]

Got enou8gh of the syntax ironed out, and I'm moving on to threading.

[James Harris]

On Feb 10, 3:36 am, Jacko <jackokr...@gmail.com> wrote:
> https://dl.dropbox.com/u/1615413/tidy/PMB.pdf is now a little updated. The word static behaves like quote in LISP.

The document doesn't look much different and certainly doesn't
illustrate concepts by examples, as suggested. From what I can tell,
though, it seems you have some good ideas.

James