Re: [Tack-devel] Updates and issues

[David G. <dg...@co...>]

It's probably not worth chasing pure ANSI-compatibility too hard --- ANSI C
is so limited that for many programs it just won't be feasible. The ack
driver is a good candidate. getopt is more interesting; it's completely
standard, defined by Posix. so having our own copy only really benefits
non-Posix systems of which there are very few, and none are supported by
the ACK right now. I'd be inclined to stick with the Posix one until we
actually run into a non-Posix platform in real life.

Re em_opt: is this util/opt? If so, there should already be a build.lua in
there. Build files are only picked up automatically if they're referred to
be another build rule. em_opt's depended on by the plat/*/build-tools.lua
file, but all plats use the same copy, so it's only built once.

On Mon, 6 May 2019 at 19:32, Carl Eric Codere via Tack-devel <
tac...@li...> wrote:

> Greetings,
>                I am slowly moving forward on making the code more ANSI
> compatible, I discovered a few points:
>
> * The current ANSI libc has a lot of non ANSI C functions - but i guess
> this is known.
> * em_ego cannot build using a pure ANSI C compiler because it uses getopt
> - how could this be solved cleanly? Any ideas? Should i put getopt in
> system or any ideas?
> * em_opt library now builds using my build system, but how do i add it to
> the LUA build system, just by adding build.lua in the directory, it will
> automatically be picked up?
> * the ack executable is fully unixish... by looking at it i am a bit
> worried to move it to using only ANSI C without breaking a lot of stuff...
> therefore I am using now acc to build on my side, /fast/driver/ do you
> think it would also be useful to add it to the build system?
>
> Carl
>
>
>
>
>
>
> _______________________________________________
> Tack-devel mailing list
> Tac...@li...
> https://lists.sourceforge.net/lists/listinfo/tack-devel
>


-- 
┌─── http://www.cowlark.com ───
│ "I have always wished for my computer to be as easy to use as my
│ telephone; my wish has come true because I can no longer figure out
│ how to use my telephone." --- Bjarne Stroustrup

On Mon, 6 May 2019 at 19:32, Carl Eric Codere via Tack-devel <
tac...@li...> wrote:

> Greetings,
>                I am slowly moving forward on making the code more ANSI
> compatible, I discovered a few points:
>
> * The current ANSI libc has a lot of non ANSI C functions - but i guess
> this is known.
> * em_ego cannot build using a pure ANSI C compiler because it uses getopt
> - how could this be solved cleanly? Any ideas? Should i put getopt in
> system or any ideas?
> * em_opt library now builds using my build system, but how do i add it to
> the LUA build system, just by adding build.lua in the directory, it will
> automatically be picked up?
> * the ack executable is fully unixish... by looking at it i am a bit
> worried to move it to using only ANSI C without breaking a lot of stuff...
> therefore I am using now acc to build on my side, /fast/driver/ do you
> think it would also be useful to add it to the build system?
>
> Carl
>
>
>
>
>
>
> _______________________________________________
> Tack-devel mailing list
> Tac...@li...
> https://lists.sourceforge.net/lists/listinfo/tack-devel
>


-- 
┌─── http://www.cowlark.com ───
│ "I have always wished for my computer to be as easy to use as my
│ telephone; my wish has come true because I can no longer figure out
│ how to use my telephone." --- Bjarne Stroustrup