To confirm guys eC does support C preprocessing.
The C preprocessor is invoked before the eC compiler does its
parsing.
And all native C headers should work fine as well, although there
might be some portability issues on more obscure platforms which
have not yet been tested which would require attention, but as
you can see at https://packages.debian.org/jessie/libecerecom0 it
works fine on most popular platforms.
eC tries to be a superset of C as much possible, with only a few
keyword clashes like 'class' as an exception.
Best regards,
-Jerome
On Thursday, 12 March 2015 at 11:02:11 UTC, ketmar wrote:
On Wed, 11 Mar 2015 19:26:13 -0700, Parke via
Digitalmars-d-learn wrote:
On Wed, 11 Mar 2015 06:22:32 +0000, sclytrack wrote:
- You can include C library headers directly in your .ec
code, without
any special keyword (like extern "C" in C++)
On Wed, Mar 11, 2015 at 1:59 AM, ketmar via Digitalmars-d-learn
<digitalmars-d-learn@puremagic.com> wrote:
either i missed something, misunderstood what he means or he
is simply
wrong. i remember that there is no CPP macro processor in eC,
so...
oops.
why my C header is not working?!
Maybe the eC compiler invokes a C compiler to do the
preprocessing.
and then we have things like `static inline` functions and many
other
quirks. ah, and alot of standard C headers included, which are
platform-
dependent, by the way. so the only way to make this work is to
have full-
featured native C compiler inside.
