Xref: news2.mv.net comp.os.msdos.djgpp:7276 From: cziwkga AT ulcc DOT ac DOT uk (Kevin Ashley) Newsgroups: comp.os.msdos.djgpp Subject: Re: Multitasking in DOS (fwd) Date: 12 Aug 1996 12:03:19 GMT Organization: University of London Computer Centre Lines: 30 Distribution: world Message-ID: <4un6i7$hnj@calypso.ulcc.ac.uk> References: Reply-To: k DOT ashley AT ulcc DOT ac DOT uk NNTP-Posting-Host: silver-e.ulcc.ac.uk To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp In article , "Garrido Freire, Fco. Javier ((R)JA.GAR. SOFT)" writes: [snip] |>Whichever ANSI C programs compiled by a modern compiler (vg. |>DJGPP) will be on its best behaviour. But, could DJGPP be fed on |>POSIX programs? |> |>Compatibility is another problem, but, what is Windows compatible |>with? |> |>PS: In order to answer 1st question I reread Faq v2 21.1. It says |>DJGPP is ANSI- and POSIX- complaint... but, try to compile any *IX |>shell. (I have to re-re-read FAQ more often, anyway :) |> No-one has ever claimed that the Unix shells are themselves POSIX-compliant or ANSI-compliant programs. Shells like ksh *provide* a posix-compliant environment, but to do so they often have to interact with the non-POSIX, non-ANSI features of their host system. Shells more than most programs have to be aware of the peculiarities of the OS they are running under, although much of their code (such as the parsers) should be platform-independent. But expecting to compile a shell from one platform on another without problems is to misunderstand what the shell has to do. ------------------------------------------------------------------------------ Kevin Ashley K DOT Ashley AT Ulcc DOT ac DOT uk Systems Development Group Manager http://www.ulcc.ac.uk/staff/Kevin+Ashley University of London Computer Centre. ...ukc!ncdlab!K.Ashley This is not a signature