On Mon, 6 Jan 2014 18:55:42 +0100 Martin Schreiber <[email protected]> wrote:
> On Monday 06 January 2014 16:34:31 Linuxfan wrote: > > > > I think that program sources are text files and always will be. > > ... > I don't agree, sorry. Don't be sorry. It is apparent that we have different concepts, stop. > The purpose is to let a the sub or method call always look the same > because of pattern recognition. ...and later... > A comma in MSElang is a separator, a semicolon is a terminator. And > the same look of definition and call also because of pattern > recognition. Pattern recognition... I don't care about it when I *use* a compiler; moreover, I think the compiler should work much more than today's compiler do. It is true that fast compilation is desirable, also. But computers are getting more and more powerful. > The problem in "with" is if one uses a local variable which is later > also added to the "with'ed" class or record. This is a point where we share the same idea! WITH *can* lead to problems, but if the programmer is careful, no problem. > > Even in my idea they always look the same, if you know the language. > It always should look the same independent if one knows the language > well or not. ;-) Hmmm... > > procedure > > DoSelectDir of TObject Sender > > DoSaveLayout of TObject Sender > > virtual > > ReadConfig > > WriteConfig > > end > > end > > > This is for me the worst possible indention style, sorry. Actually the mail program has messed up the indentation, but I understand. Every person has its own tastes. > > "Error: Fields cannot appear after a method or property definition, > > ... > In MSElang modifiers are probably not separated by ";". And this is a good point. > Why should it if it is not necessary? I don't think it is a too big > burden to write > " > f1:= 1.0 + f2 * 2.0; It can be, when not necessary. Who wants to make things clear, can always do, like you. But those that do not want? > > ... converting thenewtype to str8 ... and integer to str8 ... > You always write "s()" because of function overloading. There are no > ambiguities because MSElang has no implicit type conversions. 80% solved. For str8. Then there are utf8, utf16, mcs-4... so you will have su8(), su16(), smcs4()? > > The expectations are 10 times faster compilation times than FPC 2.6.2. > > MSELang is not enough modern. > I don't care. It is a tool mainly for me. Well, what to say. I hope we both succeed in doing our language. With affect, I hope that one day there will be a debate in internet "MSELAng vs Java vs Python vs C# vs Simple"! (Simple is the name I chose for my language). Have a nice evening, regards, linuxfan ------------------------------------------------------------------------------ Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk _______________________________________________ mseide-msegui-talk mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk
