Re: [Lazarus] [fpc-pascal] Tests results of several pascal based JSON parsers

2019-08-31 Thread Benjamin Rosseaux via lazarus
Could you include https://github.com/BeRo1985/pasjson in the comparison?

On Fri, Aug 30, 2019 at 4:22 PM Anthony Walter via lazarus <
lazarus@lists.lazarus-ide.org> wrote:

> Alan, oh that's a good idea. I will do that as well as add a few more
> parser libraries as requested by a few people in other non mailing lists
> threads. I will also try to find out what's going on the unicode strings as
> it might be a problem with the compiler.
>
> Michael,
>
> I am on Linux as well, but I will test under Windows and Mac too.
> --
> ___
> lazarus mailing list
> lazarus@lists.lazarus-ide.org
> https://lists.lazarus-ide.org/listinfo/lazarus
>
-- 
___
lazarus mailing list
lazarus@lists.lazarus-ide.org
https://lists.lazarus-ide.org/listinfo/lazarus


Re: [Lazarus] Vulkan Library for FreePascal/Lazarus

2017-05-18 Thread Benjamin Rosseaux via Lazarus
http://www.phoronix.com/scan.php?page=news_item&px=PasVulkan-Vulkan--Pascal-Bind
:-)

On Tue, May 9, 2017 at 4:38 AM, Benjamin Rosseaux 
wrote:

> PasVulkan seems to be have better Platform Support (incl. Support for
> Wayland, Mir, Android, MoltenVK, etc.) and more Vulkan Utils stuff, like
> texture loaders for DDS, KTX, PNG, TGA, etc. and a own working memory
> manager for manage the Vulkan memory (the reason for it, see slide 20 on
> http://32ipi028l5q82yhj72224m8j.wpengine.netdna-cdn.com/wp-
> content/uploads/2016/05/Most-common-mistakes-in-Vulkan-apps.pdf with the
> slide sub-title "PROBLEMATIC AREAS: MEMORY MANAGEMENT" ).
>
> The Vulkan memory management stuff is in very many Vulkan code examples
> and Vulkan frameworks on the web often totally wrong, that there will be
> often worked without sub-allocations and that the maxMemoryAllocationCount
> limit is often ignored by the most Vulkan code examples and Vulkan
> frameworks on the web. In contrast to it, PasVulkan is here in this point
> fully Vulkan specification compliant.
>
>
> On Thu, Apr 13, 2017 at 6:34 PM, Michalis Kamburelis via Lazarus <
> lazarus@lists.lazarus-ide.org> wrote:
>
>> a2017-04-13 11:30 GMT+02:00 Kostas Michalopoulos via Lazarus
>> :
>> > This is nice, although personally i do not like the use of multiple inc
>> > files. I think Benjamin Rosseaux's pasvulkan does it better with
>> creating a
>> > single pas file (he also uses a unit from the vk.xml file):
>> >
>> > https://github.com/BeRo1985/pasvulkan/blob/master/src/Vulkan.pas
>> >
>> >
>> >
>> > On Thu, Apr 13, 2017 at 7:32 AM, James.mcjohnson via Lazarus
>> >  wrote:
>> >>
>> >> This is both an announcement and request for help for an open source
>> >> FreePascal project which strives to provide:
>> >> 1) a low level access to Vulkan API created directly from the vk.xml
>> >> specification
>> >> 2) high level wrapper classes for ease of integration in an FP/Lazarus
>> >> project
>> >>
>> >> The project is located at
>> >> https://github.com/james-mcjohnson/VulkanLibraryForFreePascal and I
>> would
>> >> appreciate any constructive feedback.
>> >>
>> >> It is my hope that a better programmer than I am will take an interest
>> and
>> >> help create a truly useful Vulkan Library for FreePascal.
>> >>
>>
>> I want to add Vulkan renderer to Castle Game Engine later this year.
>> Now I don't know which project to choose:) Both approaches
>> (https://github.com/james-mcjohnson/VulkanLibraryForFreePascal and
>> https://github.com/BeRo1985/pasvulkan ) seem very fine to me,
>>
>> - in both cases you generate the Pascal code automatically from vk.xml,
>> - in both cases you provide a nicely-looking OOP API,
>> - both projects have suitable open-source licenses (MIT or zlib).
>>
>> I don't mind a couple of include files, they actually include
>> readability for me. (I know, it's a matter of taste -- do you prefer
>> to navigate multiple smaller files, or navigate one big file.)
>>
>> @James, would you mind removing the "Public Service Announcement" from
>> https://github.com/james-mcjohnson/VulkanLibraryForFreePasca
>> l/blob/master/LICENSE.md
>> ? Don't get me wrong, I understand that you want to promote your faith
>> and I respect that. Having this in README files, and Pascal sources,
>> is absolutely OK. But I'm not a lawyer, and I'm unsure how it affects
>> the legal text of the license. Having just an "unmodified MIT license"
>> would feel safer for me.
>>
>> Regards,
>> Michalis
>> --
>> ___
>> Lazarus mailing list
>> Lazarus@lists.lazarus-ide.org
>> http://lists.lazarus-ide.org/listinfo/lazarus
>>
>
>
-- 
___
Lazarus mailing list
Lazarus@lists.lazarus-ide.org
http://lists.lazarus-ide.org/listinfo/lazarus


Re: [Lazarus] Vulkan Library for FreePascal/Lazarus

2017-05-08 Thread Benjamin Rosseaux via Lazarus
PasVulkan seems to be have better Platform Support (incl. Support for
Wayland, Mir, Android, MoltenVK, etc.) and more Vulkan Utils stuff, like
texture loaders for DDS, KTX, PNG, TGA, etc. and a own working memory
manager for manage the Vulkan memory (the reason for it, see slide 20 on
http://32ipi028l5q82yhj72224m8j.wpengine.netdna-cdn.com/wp-content/uploads/2016/05/Most-common-mistakes-in-Vulkan-apps.pdf
with the slide sub-title "PROBLEMATIC AREAS: MEMORY MANAGEMENT" ).

The Vulkan memory management stuff is in very many Vulkan code examples and
Vulkan frameworks on the web often totally wrong, that there will be often
worked without sub-allocations and that the maxMemoryAllocationCount limit
is often ignored by the most Vulkan code examples and Vulkan frameworks on
the web. In contrast to it, PasVulkan is here in this point fully Vulkan
specification compliant.


On Thu, Apr 13, 2017 at 6:34 PM, Michalis Kamburelis via Lazarus <
lazarus@lists.lazarus-ide.org> wrote:

> a2017-04-13 11:30 GMT+02:00 Kostas Michalopoulos via Lazarus
> :
> > This is nice, although personally i do not like the use of multiple inc
> > files. I think Benjamin Rosseaux's pasvulkan does it better with
> creating a
> > single pas file (he also uses a unit from the vk.xml file):
> >
> > https://github.com/BeRo1985/pasvulkan/blob/master/src/Vulkan.pas
> >
> >
> >
> > On Thu, Apr 13, 2017 at 7:32 AM, James.mcjohnson via Lazarus
> >  wrote:
> >>
> >> This is both an announcement and request for help for an open source
> >> FreePascal project which strives to provide:
> >> 1) a low level access to Vulkan API created directly from the vk.xml
> >> specification
> >> 2) high level wrapper classes for ease of integration in an FP/Lazarus
> >> project
> >>
> >> The project is located at
> >> https://github.com/james-mcjohnson/VulkanLibraryForFreePascal and I
> would
> >> appreciate any constructive feedback.
> >>
> >> It is my hope that a better programmer than I am will take an interest
> and
> >> help create a truly useful Vulkan Library for FreePascal.
> >>
>
> I want to add Vulkan renderer to Castle Game Engine later this year.
> Now I don't know which project to choose:) Both approaches
> (https://github.com/james-mcjohnson/VulkanLibraryForFreePascal and
> https://github.com/BeRo1985/pasvulkan ) seem very fine to me,
>
> - in both cases you generate the Pascal code automatically from vk.xml,
> - in both cases you provide a nicely-looking OOP API,
> - both projects have suitable open-source licenses (MIT or zlib).
>
> I don't mind a couple of include files, they actually include
> readability for me. (I know, it's a matter of taste -- do you prefer
> to navigate multiple smaller files, or navigate one big file.)
>
> @James, would you mind removing the "Public Service Announcement" from
> https://github.com/james-mcjohnson/VulkanLibraryForFreePascal/
> blob/master/LICENSE.md
> ? Don't get me wrong, I understand that you want to promote your faith
> and I respect that. Having this in README files, and Pascal sources,
> is absolutely OK. But I'm not a lawyer, and I'm unsure how it affects
> the legal text of the license. Having just an "unmodified MIT license"
> would feel safer for me.
>
> Regards,
> Michalis
> --
> ___
> Lazarus mailing list
> Lazarus@lists.lazarus-ide.org
> http://lists.lazarus-ide.org/listinfo/lazarus
>
-- 
___
Lazarus mailing list
Lazarus@lists.lazarus-ide.org
http://lists.lazarus-ide.org/listinfo/lazarus