From:	Alain Magloire <alainm AT rcsm DOT ece DOT mcgill DOT ca>
Message-Id:	<199904150205.WAA12168@mccoy2.ECE.McGill.CA>
Subject:	v2.x release: features ?
To:	djgpp-workers AT delorie DOT com
Date:	Wed, 14 Apr 1999 22:05:07 -0400 (EDT)
Cc:	eliz AT is DOT elta DOT co DOT il
In-Reply-To:	<199904121436.KAA18419@envy.delorie.com> from "DJ Delorie" at Apr 12, 99 10:36:11 am
X-Mailer:	ELM [version 2.4 PL25]
MIME-Version:	1.0
Reply-To:	djgpp-workers AT delorie DOT com
X-Mailing-List:	djgpp-workers AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

Bonjour 

It may be premature to talk about life after v2.03 8-)
But I'm curious.  There are 3 absents from the DJGPP env.
That I hope will find their way.

- networking support
- threading support
- internationalisation(i18n)

1) Networking
It is covered by POSIX 1003.1g document.  Two APIs are provided
the well-known Berkeley Sockets and the XTI/TLI.  The good thing
about this is that it doesn't have to be in libc and can be maintain
separately, only a few hooks in libc are necessary.

2) Threading
It is covered by POSIX 1003.{1,1c}.  Very tricky, needs lots of care and
thoughts, not easy to get right.  Fortunately POSIX have separate cleanly
the API from the implemetation so it doesn't matter which thread implementation
its use as long as it has a PThread API.  Some OSs, like AIX, gives two
different sets of libs -lc or -lc_r, Solaris asks to compile with
-D_REENTRANT -lpthread -lthread.  Still it may hurt/penalize single
threaded apps for certain things but may be worth the effort.

3) I18N
ISO C/amd 1, wide chars, multibyte strings.  Boring work not
use widely, the commitees are still fighting for the *right*
set of chars, UTF ? Unicode ? pfff .. !

Is there major projects ahead for the core DJGPP/libc ?
Just curious at the prospects.

-- 
au revoir, alain
----
Aussi haut que l'on soit assis, on est toujours assis que sur son cul !!!

- Raw text -