This is the mail archive of the cygwin mailing list for the Cygwin project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: bc version has issue with \r when run from cmd

Andrew Schulman wrote:
Does whoever made the windows port e.g. for the gow one or for the
cygwin one, make their windows ports open source, and  if so, then
does anybody have a link to those?

The Cygwin bc package uses the bc 1.06.95 source that I linked to, plus some
patches. You can download them all by checking the "Src" box for bc in setup,
then looking in /usr/src/bc-1.06.95-2.src/.

I doubt that anyone here knows about the Gow bc package.
	I was going to ask: what is 'gow'?
	It seems like it is a program compiled to run
in the windows subsystem?  If that's the case, they likely
created a version of 'bc' to run under the windows subsystem.

	As may be obvious now, you need to use a command
shell that is compatible with whatever subsystem you compile
'bc' under.
	What line ending 'bc' uses is dependent on what
subsystem it was compiled for.  The one in cygwin is designed
for use in cygwin and apparently the one included with 'gow'
(whatever that is), is compiled for use from windows.  "bc",
and most utilities ported from *nix or open-source systems,
don't care and don't look at line endings -- they expect
"\n" to be the "end-of-line" indicator.  On *unix* and *mac*
systems it is 1 character long, but on windows, it's 2 characters
(<CR>+<LF>).  The utilities would get alot more confused if they
had to accommodate both, so in general they only look at "\n" and
rely on however they were built to indicate what that translates
to in the surrounding environment.


Problem reports:
Unsubscribe info:

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]