On 2013-07-31 20:57, Sven Barth wrote:
On 31.07.2013 20:55, Felipe Monteiro de Carvalho wrote:
On Wed, Jul 31, 2013 at 8:51 PM, Sven Barth
wrote:
The cwstring of Android uses the ICU library libicuuc.so.
Is this available in the NDK for one of the higher API levels? It is
not in the list for
On Thu, Aug 1, 2013 at 9:59 AM, Torsten Bonde Christiansen
wrote:
> I did some research before i sent the mail and found the libucuuc.so using
> adb shell into an emulator.
That's a common mistake. Android is a full Linux inside, so of course
there are tons of native libraries available inside. B
Hi,
> FYI, created wiki page http://wiki.lazarus.freepascal.org/SWIG to bundle
> information.
>It would of course be very welcome if somebody got the current version into
>main SWIG so it is more easily usable
The wiki page is a good idea, things have to be clarified though.
I don't know in how
Am 01.08.2013 11:10, schrieb dev.d...@gmail.com:
And if it's allowed to dream: one time fpc will simply link against C++
directly :)
If you prefer to work in Pascal instead of C++ then you could work on
that dream by improving the cppclass code in the compiler. Linking
against static C++ class
On 2013-07-30 22:42, leledumbo wrote:
>
> People who uses C style short unreadable code approach
> usually state they get more optimized code, yet the compiler is actually
> able to produce the same with optimizations turned on.
No, I simply prefer to use += and -= because it is easier to read th
Am 31.07.2013 11:33, schrieb Sven Barth:
Technically it would be simple to change that as the corresponding
code is already available for the above mentioned situation, but it
would definitely change the semantics if the left side is e.g. an
array with a function as index accessor (as the funct
Hi,
I need to manipulate an ipv6 address. I need to add some value to the
netaddress and replace the hostaddress with another value. E.g. add 2 to
the netaddress and replace the hostaddress by ::1
2001:db8:8500:11f8:6631:50ff:fe9a:640b/62 -> 2001:db8:8500:11fa::1/62
Is there a function in fpc
Am 30.07.2013 18:20, schrieb Mark Morgan Lloyd:
Now specifically to your question - I believe that one of the reasons
may
be the fact that Pascal does not support unary arithmetic operators in
postfix notation. The fact that C allows using them with both prefix and
postfix notation makes them
On Thu, 1 Aug 2013, dev.d...@gmail.com wrote:
Hi,
FYI, created wiki page http://wiki.lazarus.freepascal.org/SWIG to bundle
information.
It would of course be very welcome if somebody got the current version into
main SWIG so it is more easily usable
The wiki page is a good idea, things h
On Thu, 1 Aug 2013, Sven Barth wrote:
Am 01.08.2013 11:10, schrieb dev.d...@gmail.com:
And if it's allowed to dream: one time fpc will simply link against C++
directly :)
If you prefer to work in Pascal instead of C++ then you could work on that
dream by improving the cppclass code in the co
Am 01.08.2013 11:38, schrieb Michael Van Canneyt:
On Thu, 1 Aug 2013, Sven Barth wrote:
Am 01.08.2013 11:10, schrieb dev.d...@gmail.com:
And if it's allowed to dream: one time fpc will simply link against C++
directly :)
If you prefer to work in Pascal instead of C++ then you could work on
On Thu, 1 Aug 2013, Sven Barth wrote:
Am 01.08.2013 11:38, schrieb Michael Van Canneyt:
On Thu, 1 Aug 2013, Sven Barth wrote:
Am 01.08.2013 11:10, schrieb dev.d...@gmail.com:
And if it's allowed to dream: one time fpc will simply link against C++
directly :)
If you prefer to work in Pasc
Semantically, it's not the same, but
a += b
can be replaced by
inc ( a, b ) ;
It's readable, it looks like normal standard Pascal; and it's clear that the
address of a is
calculated only once.
If a,b are not ordinals, inc could be overloaded.
Greetings
Gerhard
- Original Message
Am 01.08.2013 12:11, schrieb Michael Van Canneyt:
On Thu, 1 Aug 2013, Sven Barth wrote:
Am 01.08.2013 11:38, schrieb Michael Van Canneyt:
On Thu, 1 Aug 2013, Sven Barth wrote:
Am 01.08.2013 11:10, schrieb dev.d...@gmail.com:
And if it's allowed to dream: one time fpc will simply link
ag
On 01/08/2013 12:24, Sven Barth wrote:
> Am 01.08.2013 12:11, schrieb Michael Van Canneyt:
>> On Thu, 1 Aug 2013, Sven Barth wrote:
>>> Am 01.08.2013 11:38, schrieb Michael Van Canneyt:
On Thu, 1 Aug 2013, Sven Barth wrote:
> Am 01.08.2013 11:10, schrieb
How do you handle different bi
Am 01.08.2013 12:47, schrieb Reinier Olislagers:
On 01/08/2013 12:24, Sven Barth wrote:
Am 01.08.2013 12:11, schrieb Michael Van Canneyt:
On Thu, 1 Aug 2013, Sven Barth wrote:
Am 01.08.2013 11:38, schrieb Michael Van Canneyt:
On Thu, 1 Aug 2013, Sven Barth wrote:
Am 01.08.2013 11:10, schrieb
> @dliw: wasn't the Object Pascal module based on the Modula 3 module?
> IIRC recent posts on the swig mailing lists did indeed indicate the
> Modula 3 module was buggy in current SWIG.
Sorry, you're right - it was based on Modula - I did mix it up.
Thanks for this correction.
> Important point for variant 2: less overhead.
Right, that's the biggest plus in my eyes.
>Or is this meanwhile standardized ?
Unfortunately not. It starts in different name mangling - as already said here
- and other (small) differences.
So working on a cross-platform project in C++ with differ
On Thu, 1 Aug 2013, Sven Barth wrote:
Of course I understand it's very attractive to have everything in house
and native in FPC, but I suspect the effort needed to develop/maintain
it may outweigh that...
Important point for variant 2: less overhead. Using swig you first flatten
the API and t
On 01/08/2013 13:11, Sven Barth wrote:
> Am 01.08.2013 12:47, schrieb Reinier Olislagers:
>> On 01/08/2013 12:24, Sven Barth wrote:
> Important point for variant 2: less overhead. Using swig you first
> flatten the API and then unflatten it again into Object Pascal classes.
> For callbacks you have
Sven Barth wrote:
We have three windows platforms with MSVC and I don't know how many
platforms where GCC or LLVM is the main compiler. I'm not going for
popularity here, just for the majority of platforms.
Looking at the options
1 use swig architecture to parse the C++ source code/headers and
Hi felow pascaloids,
I know I'm out the discussion, but I don't understand why Pascal should
include stuff from other languages that doesn't fit the "spirit"
of Pascal, as readability (and no, "++" isn't more readable). I mean,
if you like a structure, syntax or behavior from C, then use C. I do i
Somehow relevant, has someone thought of turning Inc()/Dec() into functions
that return the modified value -like the Interlocked ones? I think this
would cover some of the cases discussed in a more "pascalish"
notation.Also, Include()/Exclude() could similarly be turned into
functions.
--
Constant
On 2013-07-31 20:57, Sven Barth wrote:
On 31.07.2013 20:55, Felipe Monteiro de Carvalho wrote:
On Wed, Jul 31, 2013 at 8:51 PM, Sven Barth
wrote:
The cwstring of Android uses the ICU library libicuuc.so.
Is this available in the NDK for one of the higher API levels? It is
not in the list for
On 01.08.2013 20:43, Torsten Bonde Christiansen wrote:
On 2013-07-31 20:57, Sven Barth wrote:
On 31.07.2013 20:55, Felipe Monteiro de Carvalho wrote:
On Wed, Jul 31, 2013 at 8:51 PM, Sven Barth
wrote:
The cwstring of Android uses the ICU library libicuuc.so.
Is this available in the NDK for
On 2013-08-01 21:58, Sven Barth wrote:
On 01.08.2013 20:43, Torsten Bonde Christiansen wrote:
On 2013-07-31 20:57, Sven Barth wrote:
On 31.07.2013 20:55, Felipe Monteiro de Carvalho wrote:
On Wed, Jul 31, 2013 at 8:51 PM, Sven Barth
wrote:
The cwstring of Android uses the ICU library libicuu
On 01 Aug 2013, at 22:22, Torsten Bonde Christiansen wrote:
> On 2013-08-01 21:58, Sven Barth wrote:
>> How exactly did you compile?
>>
>> As described in the wiki with "make crossall OS_TARGET=android
>> CPU_TARGET=arm ..." in the top level directory? In that case it should be
>> compiled and
27 matches
Mail list logo
