On Monday 06 January 2014 20:41:48 Linuxfan wrote: > On Mon, 6 Jan 2014 18:55:42 +0100 > > > > 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. > Maybe there is a misunderstanding, I mean pattern recognition by reading the code by a human. :-)
I don't know if you read the MSElang Wiki, it is here: https://gitorious.org/mseide-msegui/pages/Mselang The design goals of MSElang: " The design goals Ultimate goal is to build the most productive universal programming environment, usable from programming of microcontrollers to MSEgui projects. I like pragmatic solutions but hate compromises. 1. Simple. Reduce the language concepts one has to learn to the minimum, make them as orthogonal as possible. 2. Readable. MSElang programs should be read like a letter. 3. Easy to learn. Because of 1. and 2. it should be suitable for pupils as first programming language. 4. Powerful Allow to go down to the bare metal, it has pointers and pointer arithmetic. Object orientated high level programming. 5. Fast running State of the art optimizations. 6. Fast compiling While defining the language keep in mind how it can be implemented efficiently. " I don't want to make the language a "fascinating intellectual puzzle" there is enough challenge in finding of best algorithms and architecture of the programs one has to develop... > > 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. How with Pascal "with" can one be sure that a *newly* added field to a record will not hide a already used variable in an *existing* "with" statement? [...] > > > > ... 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()? > If there are no implicit conversions function overloading works for function result types also. I assume the "print()" function uses utf-8? Martin ------------------------------------------------------------------------------ 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
