Hallo Martin,
Du schriebst am Wed, 14 Jun 2017 06:56:33 +0200:
> What is wrong with "method" instead of "object function"?
It's a new keyword, and it forgoes any distinction between real functions
and procedures. With an "object function", you can also have an "object
procedure". With "method",
On Tuesday 13 June 2017 22:29:21 Sieghard wrote:
> Using this as a reference, a syntax like
>
> MethodType = object function ( or
> MethodVariable: object function (
> might be considered. Yes, this is more typing.
> (Perhaps abbreviate it with just
On Tuesday 13 June 2017 17:27:41 Edson H wrote:
> Ok. I understand what Martin does. I have implemented this syntax too, in
> my compiler.
>
>
> I just was asking for the keyword ELSIF, to avoid nested IF, for several
> comparisons, but Martin prefers to have a lot of THEN ... END, nested. I
>
Hallo Martin,
Du schriebst am Tue, 13 Jun 2017 06:47:58 +0200:
> > [functions & procedures]
> IIRC you proposed to use "function" for both? Sometimes I have the
No. I did propose to use "function" _only_ if you _insisted_ to use the
same keyword for both uses. If you kept the Pascal convention,
nviado: domingo, 11 de junio de 2017 08:11 p.m.
Para: General list for MSEide+MSEgui
Asunto: Re: [MSEide-MSEgui-talk] MSElang Objects
On Sun, Jun 11, 2017 at 4:58 PM, Edson H
<dev_nul...@hotmail.com<mailto:dev_nul...@hotmail.com>> wrote:
No so much, but In Pascal you need to do:
i
On Monday 12 June 2017 22:13:32 Sieghard wrote:
> Hallo Martin,
>
> [functions & procedures]
>
> > "function" in C always has a type identifier. As you write, a
> > mathematical function returns something. So "procedure" like in Wirth's
> > Modula2.
>
> Or so. In any case, you lose the ability to
On Sunday 11 June 2017 02:36:46 Sieghard wrote:
> Hallo Martin,
>
> Du schriebst am Sat, 10 Jun 2017 06:54:15 +0200:
> > I don't like "sub" much but found nothing better up to now. I think that
>
> "sub" seems to me to imply you're about to create a new BASIC variant.
> Why not use "function" for
On Sunday 11 June 2017 16:58:23 Marcos Douglas B. Santos wrote:
> On Sun, Jun 11, 2017 at 1:29 AM, Martin Schreiber
wrote:
> >> You need to have a return. If you have a object with a method "exec",
> >> eg, why not return the object itself? Just return something.
> >
> > Why?
On Sunday 11 June 2017 17:31:33 Edson H wrote:
> It's strange. Do you prefer to write?
>
>
> if ... then
>
> ...
>
> else
>
> if ... then
>
> ...
>
> else
>
> if ... then
>
> ...
>
> else
>
> ...
>
> end;
>
> end;
>
> end;
>
>
> Instead of?
>
>
> if ... then
>
>
On Sun, Jun 11, 2017 at 4:58 PM, Edson H wrote:
> No so much, but In Pascal you need to do:
>
>
> if ... then
> begin //WARNING: If use more than a sentence, you need BEGIN-END
> ...
> end //DANGER: Don't put semicolon!
> else if ... then
> begin
semicolon!
else
begin //WARNING: the same before.
//some code
end; //DANGER: Put semicolon!
De: Marcos Douglas B. Santos <m...@delfire.net>
Enviado: domingo, 11 de junio de 2017 03:51 p.m.
Para: General list for MSEide+MSEgui
Asunto: Re: [MSEide-
Hallo Martin,
Du schriebst am Sat, 10 Jun 2017 06:54:15 +0200:
> I don't like "sub" much but found nothing better up to now. I think that
"sub" seems to me to imply you're about to create a new BASIC variant.
Why not use "function" for all such things, if you don't like to
explicitely state
On Sun, Jun 11, 2017 at 12:31 PM, Edson H wrote:
>
> Instead of?
>
> if ... then
> ...
> elsif ... then
> ...
> elsif ... then
> ...
> else
> ...
> end;
>
>
> Don't see this like nested IF. It's just a multiple conditional. More at the
> style of Modula-2 and the
IF. It's just a multiple conditional. More at the
style of Modula-2 and the new language syntax.
De: Martin Schreiber <mse00...@gmail.com>
Enviado: domingo, 11 de junio de 2017 07:21 a.m.
Para: mseide-msegui-talk@lists.sourceforge.net
Asunto: Re: [MSEide-
On Sun, Jun 11, 2017 at 1:29 AM, Martin Schreiber wrote:
>> You need to have a return. If you have a object with a method "exec",
>> eg, why not return the object itself? Just return something.
>
> Why?
Because you could write a more elegant code.
If you return "self" even in
On Saturday 10 June 2017 17:39:14 Edson H wrote:
>
> By the way, I haven't seen the keyword ELSIF in your IF syntax.
>
MSElang has no "elsif". I think nested structures should be written so that
the nested character is visible.
Martin
On Sat, Jun 10, 2017 at 1:54 AM, Martin Schreiber wrote:
>
> I don't like "sub" much but found nothing better up to now. I think that
> object methods deserve an own token "method" because of the implicit "self"
> parameter. Comming from a Pascal background "procedure" implies
.
De: Martin Schreiber <mse00...@gmail.com>
Enviado: sábado, 10 de junio de 2017 10:59 a.m.
Para: mseide-msegui-talk@lists.sourceforge.net
Asunto: Re: [MSEide-MSEgui-talk] MSElang Objects
On Saturday 10 June 2017 06:54:15 Martin Schreiber wrote:
> "
> pr
ah , i didn't knew this
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
mseide-msegui-talk
On Saturday 10 June 2017 14:21:45 code dz wrote:
> i think (method) is good abridgement for both function & procedure .
> why another keyword!
>
Because a method has an implicit "self" parameter which "procedure"
and "function" don't have.
Martin
i think (method) is good abridgement for both function & procedure .
why another keyword!
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
On Saturday 10 June 2017 06:54:15 Martin Schreiber wrote:
> "
> proc test1(a: int32): flo64;
> proc test2(const a: string8);
> meth objty.test3(a: int32): flo64;
> meth objty.test4(const a: string8);
> meth ctest.test3(a: int32): flo64;
> meth ctest.test4(const a: string8);
> "
> It has the
On Saturday 10 June 2017 07:52:31 Edson H wrote:
> I was thinking in using the two forms:
>
>
> "proc" (short word) and "procedure" (long word).
>
> "meth" (short word) and "method" (long word).
>
>
> I would like to keep the PROCEDURE, in the honor of Pascal/Modula-2.
>
That contradicts the
patible syntax, the most possible.
De: Martin Schreiber <mse00...@gmail.com>
Enviado: sábado, 10 de junio de 2017 04:54 a.m.
Para: mseide-msegui-talk@lists.sourceforge.net
Asunto: Re: [MSEide-MSEgui-talk] MSElang Objects
On Saturday 10 June 2017 06:15:09 E
On Saturday 10 June 2017 06:15:09 Edson H wrote:
> Hi Martin,
>
>
> I have seen you use "sub" for procedures or functions, and "method" for
> object. Is it?
>
Yes.
> I think you can use only PROCEDURE keyword, for procedures and functions
> (and probably for objects), like Modula-2, do.
>
I
I think, it's better to use
"sub" too, but in the other hand, I don't want to break to much the Pascal
compatibility.
De: Martin Schreiber <mse00...@gmail.com>
Enviado: domingo, 07 de mayo de 2017 09:41 a.m.
Para: mseide-msegui-talk@lists.sourceforge
On Monday 22 May 2017 11:39:28 Fred van Stappen wrote:
> > Make a feature request?
>
> Hello Martin.
>
> OK, I try to do my best. --->
> http://free-pascal-general.1045716.n5.nabble.com/Size-of-program-vs-library
>-td5718200i40.html
>
> But to accept the request, the fpc team ask to -->
>
> >>
> Make a feature request?
Hello Martin.
OK, I try to do my best. --->
http://free-pascal-general.1045716.n5.nabble.com/Size-of-program-vs-library-td5718200i40.html
But to accept the request, the fpc team ask to -->
>> Before filing a request, you can already check yourself what happens
>>
> using Graeme's code proved that FPC has a *HUGE* weakness in the floating
> point arena.
Aaaargh, ..., today's decent audio program/library uses quasi only float 32 bit
resolution, all DSPs convert first the integers into float 32 before to apply
calculs (then result is rounded/converted if
On Friday 19 May 2017 18:06:18 Jon Foster wrote:
[...]
> If MSElang is far enough along it would be interesting to see what it can
> do with with Graeme's ray-caster. I've dumbed it down to <300 lines and
> removed the external SDL dependency so it can be run as a raw computational
> benchmark.
>
On 05/07/2017 03:05 AM, Graeme Geldenhuys wrote:
> On 2017-05-07 08:20, Martin Schreiber wrote:
>> MSElang has been designed as a high performance language so it can't be so
>> simple.
> Huh? Java is an excellent performance language. Please ignore all statements
> on the Internet older than say
Hallo Martin,
Du schriebst am Tue, 9 May 2017 07:49:01 +0200:
...
> > > >> 2. In this case:
> > > >> obj2: ^objty; //on heap
> > > >>
> > > >> Is it possible to remove the "^"?
> > > >> obj2.f1:= 123;
> > > >
> > > > No, obj2 is a pointer.
> > > >
> > > >> I think this distinction exists
i-talk@lists.sourceforge.net
Objet : Re: [MSEide-MSEgui-talk] MSElang Objects
On Monday 15 May 2017 10:32:01 Fred van Stappen wrote:
> Pff, no answers (as usual).
>
>
> I begin to be lazy of fpc.
>
Make a feature request?
"
-XX should work for l
On Monday 15 May 2017 10:32:01 Fred van Stappen wrote:
> Pff, no answers (as usual).
>
>
> I begin to be lazy of fpc.
>
Make a feature request?
"
-XX should work for libraries.
"
or so.
Martin
--
Check out the
Pff, no answers (as usual).
I begin to be lazy of fpc.
Fre;D
De : Fred van Stappen <fi...@hotmail.com>
Envoyé : samedi 13 mai 2017 11:49
À : General list for MSEide+MSEgui
Objet : Re: [MSEide-MSEgui-talk] MSElang Objects
OK >
http://fr
On Friday 12 May 2017 20:28:54 Fred van Stappen wrote:
>
> > accidentally not working -XX, with active smartlinking it was reduced to
> > 26072 bytes.
>
> Do you mean that you have a trick to do smartlinking working for libraries
> ?
>
No, the first time I presented the benchmark results in the
On Friday 12 May 2017 13:52:36 Fred van Stappen wrote:
> > BTW, the mergesort benchmark binary also was 177576 bytes with
> > accidentally not working -XX, with active smartlinking it was reduced to
> > 26072 bytes.
>
> Hello Martin.
>
> In a other topic, they talk about to use : -k--gc-sections.
.
De: Martin Schreiber <mse00...@gmail.com>
Enviado: viernes, 12 de mayo de 2017 07:11 a.m.
Para: mseide-msegui-talk@lists.sourceforge.net
Asunto: Re: [MSEide-MSEgui-talk] MSElang Objects
On Friday 12 May 2017 03:44:30 Edson H wrote:
>
> I'm currently developing a Pascal
On Friday 12 May 2017 13:52:36 Fred van Stappen wrote:
> > BTW, the mergesort benchmark binary also was 177576 bytes with
> > accidentally not working -XX, with active smartlinking it was reduced to
> > 26072 bytes.
>
> Hello Martin.
>
> In a other topic, they talk about to use : -k--gc-sections.
> BTW, the mergesort benchmark binary also was 177576 bytes with accidentally
> not working -XX, with active smartlinking it was reduced to 26072 bytes.
Hello Martin.
In a other topic, they talk about to use : -k--gc-sections.
Fre;D
On Friday 12 May 2017 06:06:41 Martin Schreiber wrote:
> On Friday 12 May 2017 00:07:09 Fred van Stappen wrote:
> > > It is logical that the libraries are bigger because the libraries
> > > contain all named code
> >
> > Huh, :
> >
> >
> > program prognude ;
> > begin
> > end.
> > => 26.9 k
> >
>
On Friday 12 May 2017 03:44:30 Edson H wrote:
>
> I'm currently developing a Pascal Compiler
Do you refer to
https://github.com/t-edson/PicPas
? Looks good! Does the IDE have integrated debug capabilities?
I worked many years with PIC16xxx. Programming always was done in assembler.
Martin
On Friday 12 May 2017 03:44:30 Edson H wrote:
>
> In order to avoid confusion I would suggest to use some standard or
> recommendation on names, something like "All class names must be preceded
> by the letter C"
>
In MSEgui I use "T" as prefix for class types. All other custom types have no
On Friday 12 May 2017 00:07:09 Fred van Stappen wrote:
> > It is logical that the libraries are bigger because the libraries contain
> > all named code
>
> Huh, :
>
>
> program prognude ;
> begin
> end.
> => 26.9 k
>
> library libnude ;
> begin
> end.
> => 196.3 k
Have you checked with objdump
eide-msegui-talk@lists.sourceforge.net
Asunto: Re: [MSEide-MSEgui-talk] MSElang Objects
On Tuesday 09 May 2017 15:26:24 Marcos Douglas B. Santos wrote:
>
> It is not about if these languages are better, but if they are easy to
> do the work.
>
Thats the reason why I proposed the additional and pos
> It is logical that the libraries are bigger because the libraries contain all
> named code
Huh, :
program prognude ;
begin
end.
=> 26.9 k
library libnude ;
begin
end.
=> 196.3 k
--
Check out the vibrant tech
On Thursday 11 May 2017 14:27:51 Fred van Stappen wrote:
> Hello Martin
>
> >> It is sad that still a fpc library with same code is 5 times bigger than
> >> a fpc executable ( and montain times bigger than same C code compiled
> >> with gcc or clang).
> >
> > Do you know why?
>
> Huh, the answers
Hello Martin
>> It is sad that still a fpc library with same code is 5 times bigger than a
>> fpc executable ( and montain times bigger than same C code compiled with
>> gcc or clang).
> Do you know why?
Huh, the answers in fpc forum are nebulous:
- One said it is because parameter -fPIC is
On Tue, May 9, 2017 at 10:52 AM, Martin Schreiber wrote:
> On Tuesday 09 May 2017 15:26:24 Marcos Douglas B. Santos wrote:
>>
>> It is not about if these languages are better, but if they are easy to
>> do the work.
>>
> Thats the reason why I proposed the additional and
On Tuesday 09 May 2017 15:26:24 Marcos Douglas B. Santos wrote:
>
> It is not about if these languages are better, but if they are easy to
> do the work.
>
Thats the reason why I proposed the additional and possibly redundant "class".
You are against the "class" which eliminates the explicit "^"
On Tue, May 9, 2017 at 10:00 AM, Martin Schreiber wrote:
> On Tuesday 09 May 2017 14:08:39 Marcos Douglas B. Santos wrote:
>>
>> I understand your point of view but I think this could be confusing...
>> Well, first of all we should understand the proposal this new language:
>>
On Tuesday 09 May 2017 14:08:39 Marcos Douglas B. Santos wrote:
>
> I understand your point of view but I think this could be confusing...
> Well, first of all we should understand the proposal this new language:
>
> 1. Is it a low level language that will works like C to make libs, OS and
> so
On Tue, May 9, 2017 at 3:24 AM, Martin Schreiber wrote:
> On Monday 08 May 2017 22:44:39 Marcos Douglas B. Santos wrote:
>> On Mon, May 8, 2017 at 4:05 PM, Sieghard wrote:
>> > Hallo Marcos,
>> >
>> > Du schriebst am Mon, 8 May 2017 13:12:19 -0300:
>> >> >>
On Tuesday 09 May 2017 10:41:00 Fred van Stappen wrote:
> Hello.
>
>
> If I may give my HO, I see more future for libraries than for executables
> for Pascal.
>
>
> So I hope that mselang will take (much more) care for the size and speed of
> libraries than fpc does.
>
MSElang uses LLVM to produce
Hello.
If I may give my HO, I see more future for libraries than for executables for
Pascal.
So I hope that mselang will take (much more) care for the size and speed of
libraries than fpc does.
It is sad that still a fpc library with same code is 5 times bigger than a fpc
executable ( and
On Monday 08 May 2017 22:44:39 Marcos Douglas B. Santos wrote:
> On Mon, May 8, 2017 at 4:05 PM, Sieghard wrote:
> > Hallo Marcos,
> >
> > Du schriebst am Mon, 8 May 2017 13:12:19 -0300:
> >> >> 2. In this case:
> >> >> obj2: ^objty; //on heap
> >> >>
> >> >> Is it possible to
On Monday 08 May 2017 21:05:33 Sieghard wrote:
> Hallo Marcos,
>
> Du schriebst am Mon, 8 May 2017 13:12:19 -0300:
> > >> 2. In this case:
> > >> obj2: ^objty; //on heap
> > >>
> > >> Is it possible to remove the "^"?
> > >> obj2.f1:= 123;
> > >
> > > No, obj2 is a pointer.
> > >
> > >> I think
On Mon, May 8, 2017 at 4:05 PM, Sieghard wrote:
> Hallo Marcos,
>
> Du schriebst am Mon, 8 May 2017 13:12:19 -0300:
>
>> >> 2. In this case:
>> >> obj2: ^objty; //on heap
>> >>
>> >> Is it possible to remove the "^"?
>> >> obj2.f1:= 123;
>> >>
>> > No, obj2 is a pointer.
>> >
Hallo Marcos,
Du schriebst am Mon, 8 May 2017 13:12:19 -0300:
> >> 2. In this case:
> >> obj2: ^objty; //on heap
> >>
> >> Is it possible to remove the "^"?
> >> obj2.f1:= 123;
> >>
> > No, obj2 is a pointer.
> >
> >> I think this distinction exists because "class" exists, right?
How
On Monday 08 May 2017 18:12:19 Marcos Douglas B. Santos wrote:
> On Mon, May 8, 2017 at 12:40 PM, Martin Schreiber
wrote:
> > "
> > "ini" and "fini" work for stack and heap.
>
> In fact, this is a good idea. But why don't use [initialization] and
> [finalization]?
> The IDE
On Mon, May 8, 2017 at 12:40 PM, Martin Schreiber wrote:
> [...]
>
> No. Call it "manually":
> "
> obj1.create();
> obj1.destroy();
> "
> or use "ini", "fini" methods:
> "
> objty = object
> method theinimethod() [ini]; //called after object initialization
> method
On Monday 08 May 2017 16:49:40 Marcos Douglas B. Santos wrote:
>
> Some questions:
>
> 1. In this case:
> obj1: objty; //an instance on stack, needs no create() or destroy()
>
> if my object has create() or destroy() they will be executed automatically?
>
No. Call it "manually":
"
obj1.create();
On Mon, May 8, 2017 at 10:06 AM, Martin Schreiber wrote:
> On Monday 08 May 2017 14:11:28 Marcos Douglas B. Santos wrote:
>> On Mon, May 8, 2017 at 2:39 AM, Martin Schreiber wrote:
>> >> > One does not need to use "class", it can be removed. I thought that
On Monday 08 May 2017 14:11:28 Marcos Douglas B. Santos wrote:
> On Mon, May 8, 2017 at 2:39 AM, Martin Schreiber wrote:
> >> > One does not need to use "class", it can be removed. I thought that
> >> > people comming from Free Pascal will like it. ;-)
> >>
> >> You could be
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
>>
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
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
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.
>
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
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
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
> >
>>
> 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
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.
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
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 ;)
--
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 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.
hint:
Java makes this simple. One string type (class), one character type and 8
other primitive data types. Much simpler and
On Saturday 06 May 2017 15:13:45 Marcos Douglas B. Santos wrote:
> On Sat, May 6, 2017 at 6:20 AM, Martin Schreiber wrote:
> > Hi,
> > I implemented objects and classes in MSElang:
> > https://gitlab.com/mseide-msegui/mselang/wikis/home/Mselang_objects
> >
> > Thoughts?
>
> In
On Sat, May 6, 2017 at 6:20 AM, Martin Schreiber wrote:
> Hi,
> I implemented objects and classes in MSElang:
> https://gitlab.com/mseide-msegui/mselang/wikis/home/Mselang_objects
>
> Thoughts?
In wiki home you wrote: "records, objects and classes could be unified
in a single
On Saturday 06 May 2017 11:29:42 Fred van Stappen wrote:
>
> By the way, what can we do already with mselang ?
>
It is not ready for public use.
> Do you have some examples ?
>
Testcases for the Free Pascal dialect:
https://gitlab.com/mseide-msegui/mselang/tree/master/mselang/test
> Is it
De : Martin Schreiber
Envoyé : samedi 6 mai 2017 11:20
À : mseide-msegui-talk@lists.sourceforge.net
Objet : [MSEide-MSEgui-talk] MSElang Objects
Hi,
I implemented objects and classes in MSElang:
https://gitlab.com/mseide-msegui/mselang/wikis/home/Mselang_objects
Thoughts?
On Monday 25 November 2013 09:30:36 Michael Schnell wrote:
On 11/22/2013 06:55 PM, Martin Schreiber wrote:
{$rtti on}
property prop1: int32 read fprop1 write fprop1; //streamed
{$rtti off}
To me this looks worse than just published (it does not make much
sense to allow for rtti
While I think, private, protected and public are enough visibility
complexity (omitting published and all the new fancy stuff invented by
Embarcadero), I supposed abstract is one of the concepts that should
be added to the description.
-Michael
On 11/22/2013 09:09 AM, Michael Schnell wrote:
I supposed abstract is one of the concepts that should
be added to the description.
+ reintroduce
(will non-heap objects have virtual methods ?)
BTW.:
IMO method is a more appropriate new combined name for
procedure/function than sub. It is
On Friday 22 November 2013 09:13:49 Michael Schnell wrote:
(will non-heap objects have virtual methods ?)
Yes.
BTW.:
IMO method is a more appropriate new combined name for
procedure/function than sub. It is commonly understood in the
Object-world, and it's less likely that a program to
On Friday 22 November 2013 09:09:21 Michael Schnell wrote:
While I think, private, protected and public are enough visibility
complexity (omitting published and all the new fancy stuff invented by
Embarcadero), I supposed abstract is one of the concepts that should
be added to the description.
On Friday 22 November 2013 09:34:06 Michael Schnell wrote:
On 11/22/2013 09:26 AM, Martin Schreiber wrote:
Use 'method' instead of 'sub' everywhere or introduce a new keyword?
Everywhere.
Doesn't 'method' imply that there is an instace pointer additional to the code
address?
Martin
On 11/22/2013 10:54 AM, Martin Schreiber wrote:
Doesn't 'method' imply that there is an instace pointer additional to the code
address?
For me this would be a method of object.
(But of course this is a matter of taste.)
-Michael
On Fri, Nov 22, 2013 at 5:26 AM, Martin Schreiber mse00...@gmail.com wrote:
On Friday 22 November 2013 09:13:49 Michael Schnell wrote:
(will non-heap objects have virtual methods ?)
Yes.
BTW.:
IMO method is a more appropriate new combined name for
procedure/function than sub. It is
On Fri, Nov 22, 2013 at 5:34 AM, Michael Schnell mschn...@lumino.de wrote:
On 11/22/2013 09:26 AM, Martin Schreiber wrote:
Use 'method' instead of 'sub' everywhere or introduce a new keyword?
Everywhere.
Experimente um novo navegador com tradução automática.Faça Download do
Google
On Fri, Nov 22, 2013 at 6:54 AM, Martin Schreiber mse00...@gmail.com wrote:
On Friday 22 November 2013 09:34:06 Michael Schnell wrote:
On 11/22/2013 09:26 AM, Martin Schreiber wrote:
Use 'method' instead of 'sub' everywhere or introduce a new keyword?
Everywhere.
Doesn't 'method' imply
On Fri, Nov 22, 2013 at 5:34 AM, Michael Schnell mschn...@lumino.de wrote:
On 11/22/2013 09:26 AM, Martin Schreiber wrote:
Use 'method' instead of 'sub' everywhere or introduce a new keyword?
Everywhere.
But here are two different worlds: Procedural vs. OO.
IMHO we should not combine the two
On Friday 22 November 2013 13:03:08 Marcos Douglas wrote:
On Fri, Nov 22, 2013 at 5:33 AM, Martin Schreiber mse00...@gmail.com
wrote:
On Friday 22 November 2013 09:09:21 Michael Schnell wrote:
While I think, private, protected and public are enough visibility
complexity (omitting published
On Fri, Nov 22, 2013 at 9:26 AM, Martin Schreiber mse00...@gmail.com wrote:
On Friday 22 November 2013 13:03:08 Marcos Douglas wrote:
On Fri, Nov 22, 2013 at 5:33 AM, Martin Schreiber mse00...@gmail.com
wrote:
On Friday 22 November 2013 09:09:21 Michael Schnell wrote:
While I think,
On Friday 22 November 2013 13:42:32 Marcos Douglas wrote:
On Fri, Nov 22, 2013 at 9:26 AM, Martin Schreiber mse00...@gmail.com
wrote:
tfoo = class
private
fprop1: int32;
fprop2: int32;
protected
{$rtti streaming}
property prop1: int32 read fprop1 write fprop1;
public
On Friday 22 November 2013 13:15:07 Marcos Douglas wrote:
On Fri, Nov 22, 2013 at 5:34 AM, Michael Schnell mschn...@lumino.de wrote:
On 11/22/2013 09:26 AM, Martin Schreiber wrote:
Use 'method' instead of 'sub' everywhere or introduce a new keyword?
Everywhere.
But here are two
On Friday 22 November 2013 13:00:22 Marcos Douglas wrote:
On Fri, Nov 22, 2013 at 5:26 AM, Martin Schreiber mse00...@gmail.com
wrote:
On Friday 22 November 2013 09:13:49 Michael Schnell wrote:
(will non-heap objects have virtual methods ?)
Yes.
BTW.:
IMO method is a more
On Fri, Nov 22, 2013 at 9:57 AM, Martin Schreiber mse00...@gmail.com wrote:
On Friday 22 November 2013 13:42:32 Marcos Douglas wrote:
On Fri, Nov 22, 2013 at 9:26 AM, Martin Schreiber mse00...@gmail.com
wrote:
tfoo = class
private
fprop1: int32;
fprop2: int32;
protected
{$rtti on}
==
Why not simply a new keyword :
nortti property prop1: boiolean read boolvar1; ...;
or
rttiproperty prop1: boiolean read boolvar1; ...;
which in turn can override {$rtti on}.
It looks finer granular :) It's
1 - 100 of 105 matches
Mail list logo