Re: [MSEide-MSEgui-talk] MSElang Objects

btw the keyword (method) looks weird , (sub) is much better or typical pascal (procedure , function) . its only my opinion ;) also the attribuates mechanism really looks cool . seems the best dialect will born ;) --

Re: [MSEide-MSEgui-talk] MSElang Objects

On Sunday 07 May 2017 12:05:40 Graeme Geldenhuys wrote: > On 2017-05-07 08:20, Martin Schreiber wrote: > > MSElang and MSEpas (a subset of Free Pascal) have "string8" (utf-8) > > "string16" (utf-16) "string32" (ucs-4) > > That sounds good. > > > and "bytestring" for any 8-bit encoding and > >

Re: [MSEide-MSEgui-talk] MSElang Objects

>> > I plan to use method attributes for operator overloading too: > " > type > complexty = object > real,imm: flo64; > method add(const a,b: complexty): complexty ['+']; > method sub(const a,b: complexty): complexty ['-']; > method mul(const a,b: complexty): complexty ['*']; > method

Re: [MSEide-MSEgui-talk] MSElang Objects

On Sunday 07 May 2017 11:10:48 code dz wrote: > btw the keyword (method) looks weird , (sub) is much better or > typical pascal (procedure , function) . its only my opinion ;) > I wanted to remove the distinction between "procedure" and "function", so "sub". Object procedures and functions have

Re: [MSEide-MSEgui-talk] MSElang Objects

congratulation :) what about the rtl , would you uses fpc one of write your own ? -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot

Re: [MSEide-MSEgui-talk] MSElang Objects

On Sunday 07 May 2017 11:01:40 code dz wrote: > congratulation :) > what about the rtl , would you uses fpc one of write your own ? > MSElang itself will only have a minimal RTL. For "daily business tasks" we have the MSEgui environment already. Martin

Re: [MSEide-MSEgui-talk] MSElang Objects

On 2017-05-07 08:20, Martin Schreiber wrote: > MSElang and MSEpas (a subset of Free Pascal) have "string8" (utf-8) > "string16" > (utf-16) "string32" (ucs-4) That sounds good. > and "bytestring" for any 8-bit encoding and > binary data. Why this? Why not simply Byte or an array of bytes.

Re: [MSEide-MSEgui-talk] MSElang Objects

2017-05-07 12:01 UTC+01:00, Martin Schreiber : > On Sunday 07 May 2017 12:11:06 code dz wrote: >> >> sounds good , but i think it add some complexity to the code >> readability, because the name (add) already indicates the operation , >> so why ['+'] , maybe operator instead

Re: [MSEide-MSEgui-talk] MSElang Objects

On Sat, May 6, 2017 at 11:33 AM, Martin Schreiber wrote: >> Use only objects and change this syntax... >> o1: ^obj5ty; >> ...to this one >> o1: obj5ty; >> > Correct. Plus o1^.f1 <-> c1.f1 for access of heap instance elements and > that "class" instances always are on heap. >

Re: [MSEide-MSEgui-talk] MSElang Objects

On Sun, May 7, 2017 at 1:14 PM, Martin Schreiber wrote: >> Classes should not exists in object-oriented programming. This is a >> mistake. Only objects should exists. > > In MSElang "class" = "^object" on heap. So you mean there should be no object > heap pointers but stack

Re: [MSEide-MSEgui-talk] MSElang Objects

On Sunday 07 May 2017 18:48:13 Marcos Douglas B. Santos wrote: > On Sun, May 7, 2017 at 1:14 PM, Martin Schreiber wrote: > >> Classes should not exists in object-oriented programming. This is a > >> mistake. Only objects should exists. > > > > In MSElang "class" = "^object" on

Re: [MSEide-MSEgui-talk] MSElang Objects

On Sun, May 7, 2017 at 7:05 AM, Graeme Geldenhuys wrote: >> MSElang and MSEpas (a subset of Free Pascal) have "string8" (utf-8) >> "string16" >> (utf-16) "string32" (ucs-4) > > That sounds good. Why? Is not it better to just use a single String type (as a class or

Re: [MSEide-MSEgui-talk] MSElang Objects

On Sun, May 7, 2017 at 4:15 PM, Martin Schreiber wrote: > On Sunday 07 May 2017 18:48:13 Marcos Douglas B. Santos wrote: >> On Sun, May 7, 2017 at 1:14 PM, Martin Schreiber wrote: >> >> Classes should not exists in object-oriented programming. This is a >>