Blade Runner has already done Serious work oulining the general macro capabilities in the links at the top of this page. Unless anyone has BIG problems with his general approach I propose we adjourn and look at his Ideas more carefully.

Agree with mca6 above...

The main message from the point of the ongoing java coding is that all the code should use java bean structure.

Is everyone happy? I know JimC is... he just escaped from coding in a dank cell all day

There is two possibilities: to find a Java macro language which is fit for our goal, or develop something ourselves.

1. Which is available:
a) Javascript interpreter (quite easy to use but somehow difficult to read)
b) NetRexx Java extension (difficult to use, the language powerfull and easy to read)
c) Basic interpreter (as is)
d) Java itself

2. What can we produce:
a) C-- or CPascal (the mix of the two language read my language description)
b) Pascal subset (This is my vote: structured, easy to understand, easy to read, etc.) [And I use professionaly 15 years ago...]
c) C subset (Also structured but somehow everybody like to write unchiperabl;e code with this language)
d) ?

I'm quite happy without type declaration. But I think the variable and constant declaration is VERY important. I use BASIC for serious programming for a few times ages ago. My (and my colleges) common mistake was mistype the variable names or outwrite an important variable. I spend more time to debug these kind of problems than the rest of the bugs altogether. My new suggestion:

Variable
One;
Two;
Three;
EndVariable

Constant
XXX = 10;
CCC = 1000;
VVV = "BLABLA";
EndConstant

If the user Mistype the variable the interpreter send a "Not declared variable" or "Not declared constans" error message.

(I need to call my wife. I'll be back about the same time like Mark.)

How about making it an error to use any undefined variable, then (as opposed to an undeclared one), and of course an error to redefine a constant. Consider:

someFunction()
{
const theAnswer = 42;
x = theAnser + 111; // theAnser undefined. This error can be caught at compile time.
theAnswer = 111 + x; // theAnswer is constant and cannot be redefined/assigned to. This error can be caught at compile time.
const theAnswer = 111; // same thing.
}

(No, I don't like to declare constants/variables in specialized blocks either, but that's just a personal preference )

Aha. This is one of the basic of the structured languages: One needs to Define the variables.

Anyway. I have a solution for this problem:

There will be two possibilities:
Opc.1/The user can declare the variables and arrays.
Opc.2/ The user just define the variables and arrays.

In one module they cannot mix the two style.

Damn, I thought I had that defined/declared thing right. Would you please elaborate?

LOL, about myself.

Of course I mean Declare.

Aha!

But I'm still not quite sure what you mean with users can't mix the two styles. Can you give an example?

File 1:

//here start
Variable
One;
Two;
N;
VariableEnd;

SomeRutin(...){
One = 156;
To = 4455; // Error message: non declared variable To
N = One + Two;
}
// End of file

File 2:

//here start
SomeRutin(...){
One = 156;
To = 4455;
N = One + Two; // Error message: non defined variable Two
}
// End of file

I mean: If the system find the Variable keyword than ALL the variables in ALL the rutins inside one modul must Declared before use.

(I think we can enable for the users to mix the modul types (declared, defined) because there will be different people who use the system with different background and ideas. I like to use declared variables, somehow the whole program is more readible for me.)

Blade

Thuesday I'll post my modified version of the macro language. Let say I'll wait a couple of days, and if there will be no comment or ask for modification I'll start to write the tokenizer and parser part of the interpreter probably after the next weekend.

Is that OK?

Blade

To enable the mix use for the users is possible but IMHO wrong way. I understand your point. There are more people who will write one or maybe two not built-in variable in a short and dirty rutin. They neednt any exact declaration. On the other side a pesrson who will write 3-5 Kb source file for his/her scenario will be happy with the automatic variable check from the interpreter. So I think I'll enable both of the style, but not mix in one modul. If somebody just start to typing his/her idea and wouldnt like to use the variable/constant declaration part, OK. IMO mix the two style in one modul will be a complette code mess, so I dont support this.

Thankx for the ideas,

No problem, I'm glad that there will be more than one way to do things. I see your point, too, and I would typically support even type declarations and strong typing for anything but scripting, which tends (and sometimes needs?) to be too quick and dirty to bother with explicit declarations, types, and such.

Glad to be of service,

Yes, your approach sounds good. But you will embarass us by having the macro language done Long before there's anything for it to operate on .

Blade Runner, mca, JimC:

Thanks for coming to the meeting and GREAT Job. We have 'seen the taillights' on one big issue.

Others: If you don't register any objections within the next day or so, say 18:00 EST Sunday Sept. 5th, our decisions from this meeting will be considered Locked In. Speak now or never

For a summary of conclusions look at the post labelled me6 on page 1, and up to about 10 posts thereafter.