Introducing Kitto
nandod
Wanderlan Santos dos Anjos
Very interesting project!
Kitto is compilable in Free Pascal 2.4.x and 2.6 ??
It is Linux compatible?
Att,
Wanderlan
--Nando--
You received this message because you are subscribed to the Google Groups "ExtPascal" group.
To view this discussion on the web visit https://groups.google.com/d/msg/extpascal/-/szVnp92qed8J.
To post to this group, send email to extp...@googlegroups.com.
To unsubscribe from this group, send email to extpascal+...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/extpascal?hl=en.
--
Att,
Wanderlan Santos dos Anjos
(061) (r)3345-5496; (c)9133-3804, (t)3038-1906
Nando Dessena
at my company we only work in Windows and Delphi (2010+), so I can't
say. With appropriate patches, it might.
--
--
Nando Dessena
Marcos Douglas
Without see Kitto's sources I ask:
What did you changed in ExtPascal? These changes could be implemented
in ExtPascal to serve in both projects?
Don't you have problems with memory leaks?
Marcos Douglas
Marcos Douglas
<wanderl...@gmail.com> wrote:
> Wow, Nando!!
>
> Very interesting project!
>
> Kitto is compilable in Free Pascal 2.4.x and 2.6 ??
> It is Linux compatible?
+1
Marcos Douglas
Nando Dessena
> Without see Kitto's sources
well maybe you should. ;-) That's why they were published after all.
> I ask:
> What did you changed in ExtPascal? These changes could be implemented
> in ExtPascal to serve in both projects?
I have sent several posts and opened several issues (some of them with
patches) in the past that deal with that. You can find most things
there. Most changes are probably for general good, but as I said
elsewhere I only use Delphi 2010+ and plus there are parts of
ExtPascal that I didn't get around to, such as the embedded Indy
server (well, I tried but I couldn't make it work reliably). All Kitto
changes can of course be adapted/integrated back into ExtPascal, and I
am available to discuss and explain things as needed.
> Don't you have problems with memory leaks?
I do. Some I have fixed, some I have worked around, some I have fixed
in the generated code only, while a better solution requires changes
to the code generator (which I haven't touched yet, mainly because
it's been under rework by Wanderlan as far as I understand). Finally,
some have yet to be tackled.
Ciao
--
Nando Dessena
Marcos Douglas
> Marcos,
>
>> Without see Kitto's sources
>
> well maybe you should. ;-) That's why they were published after all.
Of course I will ;-)
I just want advance the talk.
>> I ask:
>> What did you changed in ExtPascal? These changes could be implemented
>> in ExtPascal to serve in both projects?
>
> I have sent several posts and opened several issues (some of them with
> patches) in the past that deal with that. You can find most things
> there. Most changes are probably for general good, but as I said
> elsewhere I only use Delphi 2010+ and plus there are parts of
> ExtPascal that I didn't get around to, such as the embedded Indy
> server (well, I tried but I couldn't make it work reliably). All Kitto
> changes can of course be adapted/integrated back into ExtPascal, and I
> am available to discuss and explain things as needed.
OK. Well, maybe we can run the code in both compilers.
If you fixed some memory leaks, such codes will be apreciated.
>> Don't you have problems with memory leaks?
>
> I do. Some I have fixed, some I have worked around, some I have fixed
> in the generated code only, while a better solution requires changes
> to the code generator (which I haven't touched yet, mainly because
> it's been under rework by Wanderlan as far as I understand). Finally,
> some have yet to be tackled.
For me, perhaps for others as well, finish with the memory leaks is
the more important at this moment. Maybe you can pinpoint where
problems were.
Marcos Douglas