>> 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;  
Pardon, I made a stupid question not remembering this.
You can 
bet that this seems to me too verbose, compared to:

with rec1 do .left 
= 10 end;




>> > 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".
>
>The type of 
the function result must match the destination.
Uhm, this sounds like 
an imposition instead of an overloading. What am I missing?


>
>> 
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. ;-)
I 
expressed badly. I intended that you can not assume all functions your 
program needs expect utf-8. Of course, the self-made ones will do.



>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...).
This is another 
point we could share. In an old version of Simple, I even put real 
numbers in a library outside the language itself. Then I discovered 
that support for real numbers must be present from the lexer level up. 
The same could happen for other things too, for example file 
management. Unless you choose the C strategy, which does not have file 
support. And in fact it has a horrible file management. Now I think 
that external libraries should enrich the language at several levels, 
in order to add functionalities in elegant and consistent manner. This 
conflicts with a rigid language. It is too easy for a compiler to turn 
everything into its own paradigms. File operations? There are functions 
for that. Closures? Functions for that. Events? Functions. This is 
rigid and consistent, of course, but little productive. Think at the 
classic button on a form to close the form. Tcl does that with a single 
line of code (there are even IDEs for tcl, you do that with a simple 
field in object inspector). In pascal, you must declare a function, 
then write again the declaration, then write the body ("close") , and 
finally bind that method to the onlick event. All this, only to say 
"close". Not that Tcl is perfect, but surely it is *more* powerful. And 
this example is not difficult to understand for a pupil, either.


>> 
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.
I use a package manager. The latest MSE 
needs freepascal 2.6.2, the package manager says. I have fp 2.6.0. To 
upgrade fp, I need to upgrade: libc, kernel, nvidia drivers and tons of 
other programs. Dependency problems!
May be I can download a tarred 
binary instead of using the package manager, though, if it is not true 
the MSE needs fp 2.6.2.


>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.
Completions for 
classes (and records?) is enough. After 30 years of programming, I'm 
getting old and I can't sharply remember what I wrote 2 hours ago. The 
problem is when writing big chunks of code, with many references to 
many things in other units.
I must hurry up, if I want to write a 
functional Simple before getting too old!

Regards,
linuxfan

 

------------------------------------------------------------------------------
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

Reply via email to