On Monday 08 May 2017 04:01:02 Marcos Douglas B. Santos wrote:
> >
> > Currently it can be defined in "var" section
> > "
> > var
> > obj1: TObj; //on stack
> > obj2: ^TObj; //on heap
> > begin
> > //obj1 does not need to be created
> > obj2:= tobj.create();
> > obj2.destroy();
> > "
> > or i
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
>> >> mistake. Only objects should exists.
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 heap. So you mean th
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 allocated objects only?
On Sunday 07 May 2017 16:18:09 Marcos Douglas B. Santos wrote:
>
> I think every language should be as simple as possible.
> So, if you can mix every Pascal concept in just one concept, called
> object, it is better.
>
> But if you care about programmers that came from another language and
> you ca
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.
> "class" is for people
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 not)
as you've said?
>> ...
>
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 of method should be fi
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 of method should be fine ! .
> just thought
>
The method names can be choos
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
> > binar
>>
> 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 to
On 2017-05-07 10:41, Martin Schreiber 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
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. The
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 a
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
---
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 ;)
--
Che
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
_
On Saturday 06 May 2017 20:30:56 Graeme Geldenhuys wrote:
> On 2017-05-06 10:20, Martin Schreiber wrote:
> > Thoughts?
>
> What "string" and "character" types will MSElang support? Hopefully not as
> huge a list as FPC and Delphi.
>
https://gitlab.com/mseide-msegui/mselang/wikis/home
MSElang and M
18 matches
Mail list logo
