Alexander Klenin wrote:
I would ask to implement modern delphi language features like:
- anonymous methods
- for-in loop
- class constructors and destructors
- support for strict private and strict protected sections
- abstract and sealed classes
- class const, class var, class type, class property
Anyway, sooner or later delphi developers will use them more and more and
there will be a need to port that code to fpc.
These are obvious candidates for me too, but although they are good projects,
they are rather hard -- for advanced students only.
I certainly hope to get at least one such student.
But I am also interested in a simpler ideas,
perhaps for Lazarus instead of FPC.
Generally form the replies I get the impression that the need for FPC
is much more acute than for Lazarus ones ;-)
One thing to implement which is needed and easy at the same time is
support for turning paticular warnings and hints on/off in the code:
{$WARN identifier ON} / {$WARN identifier OFF} where identifier can be:
SYMBOL_PLATFORM, SYMBOL_DEPRECATED, UNIT_DEPRECATED, UNIT_PLATFORM,
UNSAFE_CODE OFF, UNSAFE_TYPE OFF, UNSAFE_CAST OFF, IMPLICIT_STRING_CAST, ...
I suggest to allow also ON/OFF by warning message ID. For example
{$WARN 5033 OFF} will turn off message "Function result does not seem to
be set".
Same to do with hints {$HINT message_id ON}/{$HINT message_id OFF}
although delphi does not support this.
Why it is easy:
1. fpc understand {$WARN} syntax while it currently do nothing
2. fpc allow to turn off warnings and messages by ID
Therefore your student will just need to complete already existed code.
Best regards,
Paul Ishenin.
--
_______________________________________________
Lazarus mailing list
[email protected]
http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
