On Tuesday 07 January 2014 09:18:47 Linuxfan wrote:
[...]
>
> This is a very very strong point. In fact, when I first saw php, I was
> stunned by those variables always referenced with "$", but later I
> understood. So, we are condamned to be verbose? No, with my colon
> trick. But even sticking to WITH, the way something else does, there is
> no problem:
>
> with form1 do
> .caption = caption
> .left = left
> ...
>
> Why the freepascal team did not change the semantic of WITH? For
> compatibility? Will you change it?
>
Yes, as showed in the Wiki. MSElang "with" statement is
"
with r: rec1 do
r.field1:= 123;
end;
with r: rec2, s: r.field1 do
r.field1.field1:= 123; //or
s.field1:= 123;
end;
"
> > > 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?
>
> This is not clear to me: "overloading works for function resul types
> also". If you can overload something else than arguments, let me know
> how do you do it - I am interested (of course, in making it
> automatic :-) ).
The type of the function result must match the destination.
> Apart from this, I think it is no good to "assume print() uses utf8",
It is your print() function, you wrote it uses utf-8 IIRC. ;-)
It is not decided up to now if MSElang will have writeln() like procedure or
if that functionality will be moved into the RTL. At the moment I prefer the
latter. Most likely there will be no file functions in the language (reset,
read, write...).
> because often a program sets captions in GTK, or fields in SQL, or uses
> external libraries written by someone else. In fact, you say MSELang
> will support several types of strings, why?
> To interface with the world,
> or to burden the language with unnecessary things? I assume all those
> types are for interfacing with the world, so who know if
> "external function xx" uses utf8 or EBCDIC.
>
For example Lazarus uses utf-8, MSEgui uses utf-16 for GUI and utf-8 for all
external text, often it is necessary to convert to UCS4 for fast code point
access in string manipulation, combining binary data and 8 bit characters in
bytestring is useful too.
> We are criticing each other, but I think this can be useful. I have a
> question: does MSEIDE support automatic completion? I didn't tried the
> last version (because of dependency issues);
What dependency issues? MSEgui solely needs libc and the X11 libraries on
Linux and user32 and gdi32 on Windows.
> in 2.8.6 a quick try was
> unsuccessful: if it is there, I don't see it.
>
There is code completion for classes. There is no Lazarus-style code
completion. That is the first thing I switch off in any IDE. ;-)
What works is code navigation by Ctrl+LeftClick, procedure parameter listing
by Shift+Ctrl+Space after the "(" and header-implementation switch by
Ctrl+Up, Ctrl+Down.
Many years ago I promised to make some efforts for Lazarus-style code
completion in MSEide if the MSE community shows some substantial work on
documentation of MSEide+MSEgui. Nothing happened. Now I don't feel obligated
to keep that promise anymore. :-)
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
