On 25.12.2011 22:53, ik wrote:
2011/12/25 Jiří Pavlovský mailto:j...@getnet.cz>>
Hello,
how can I create two level map where value is array of records?
These records are constant - I don't need to compute them or
anything.
I'm quite new to pascal and for gods sake cannot f
2011/12/25 Jiří Pavlovský
> Hello,
>
> how can I create two level map where value is array of records? These
> records are constant - I don't need to compute them or anything.
> I'm quite new to pascal and for gods sake cannot figure it out. I tried to
> use TFPGMap for that.
>
> I mean somewhe
Hello,
how can I create two level map where value is array of records? These
records are constant - I don't need to compute them or anything.
I'm quite new to pascal and for gods sake cannot figure it out. I tried
to use TFPGMap for that.
I mean somewhere in the code I get two values and ba
Here is my work on going work for it:
https://github.com/ik5/iptables.fpc
I'm trying to add both libiptc and libxtables as binding.
They allow to query and create rules in your source code, for IPTables
(netfilter) while you are in userspace.
I hope more people will find it useful
Ido
On Sun,
Hello,
Have anyone know of any open source iptables based rule generators written
in FPC or any other Pascal compiler ?
Thanks and marry Christmastime/Hanukkah ,
Ido
___
fpc-pascal maillist - fpc-pascal@lists.freepascal.org
http://lists.freepascal.org
On 12/25/2011 09:22 AM, ik wrote:
>
> Even without the modified LGPL, you are wrong afaik. LGPL is about keeping
> the original code open, while allow you to do commercial work without
> releasing your own source. GPL is all about viral licensing. AFAIK the
> modified LGPL, claims that there will
On Sun, Dec 25, 2011 at 10:09, wrote:
> I wrote
> >
> > If you statically link the lgpl code into your EXE, your exe is the
> module
> > under lgpl now. Therefore all code must be released. Statically linked
> > lgpl code in an exe is not a dll that can be shipped separately.
>
> Nevermind, I see
nore...@z505.com wrote:
I think all freepascal people have a misunderstanding of LGPL.
If you statically link the lgpl code into your EXE, your exe is the module
under lgpl now. Therefore all code must be released. Statically linked
lgpl code in an exe is not a dll that can be shipped separately
I wrote
>
> If you statically link the lgpl code into your EXE, your exe is the module
> under lgpl now. Therefore all code must be released. Statically linked
> lgpl code in an exe is not a dll that can be shipped separately.
Nevermind, I see this has been discussed:
http://free-pascal-general.1
