Re: [Freedos-devel] default (lack of) buffering in Turbo C 2.01 (e.g. Cheap Sed)
On Tue, 2 Apr 2019, Rugxulo wrote: Are you sure you don't mean Borland C? I'm pretty sure he's right and Microsoft C was the original reference compiler, before Turbo C was released for free download in the late 90s. But now, I might be mistaken, hmm hmm hmm... -uso. ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] default (lack of) buffering in Turbo C 2.01 (e.g. Cheap Sed)
Hi,
On Tue, Apr 2, 2019 at 4:51 AM Tom Ehlert wrote:
>
> > I thought you might find this interesting
> not at all ; see below.
Really? You don't find it a bit curious?
> btw: MSC was the reference compiler for freedos, some time ago.
Are you sure you don't mean Borland C?
Anyways, if you have MSC installed, I would appreciate a build of
Cheap Sed. It's quite easy to rebuild. (Then again, Gmail hates binary
.EXE attachments, even inside .ZIP.)
> please do a reality check before your next post
What compiler would you recommend for that?
> > Just for the record, "sed" is probably my favorite *nix util. So I've
> > used it quite a lot over the years (mostly in DOS!).
>
> next time, please add a TLDR section of your post like
>
> TLDR: if you use fread(), fgets() and friends AND care about
> performance, use setvbuf() with sensible parameters
No, I'm talking about default compiles being unbuffered, *unlike* the
("newer") Turbo C++ 1.01, which works fine. (So all these years it was
slower than it should've been.)
Since TC2.01 is freeware (and TC++1.01 less so nowadays), I think this
is worth clarifying, even in spite of your feigned ignorance.
(Actually, "maybe" you can still get TC++ freeware if you download
some modern Windows trialware, but I never bothered. Anyways, the old
.ZIP is mirrored on Wayback Machine, for good or bad.)
BTW, today I wrote a much-simplified sed script for FASM for PSR
Invaders. Want a copy? Probably not much use to benchmark, though.
___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] FreeCOM 0.84-pre6 prerelease
Hi, On Tue, Apr 2, 2019 at 4:51 AM Tom Ehlert wrote: > > > On Fri, Feb 22, 2019 at 5:44 PM Rugxulo wrote: > >> > >> I also did some minor fixes to my (unpublished, prerelease 0.7) MetaDOS. > > > Nobody said anything, so I didn't worry about it. But I did (barely) > > just do minor fixes and finalize 0.7 and upload it to iBiblio for us. > > does it include a fixed freecom? No because "fixed" doesn't exist (yet). It's safe to assume that Bart is busy elsewhere. But anyways, I uploaded what I had, just in case it helps with testing somehow. > does it run all tests? I'm not aware of any broken "tests" in this (0.7) release, with old (2006) FreeCOM, no. So it should work fine (or "better", even, since some external, third-party things regressed since 0.6). Not perfect but hopefully better than nothing. > > Just in case you're interested. (Maybe I should waited until tomorrow > > ... right, Tom? Right?? AM I RIGHT???) > > what am I supposed to do or say? Just laugh. ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] FreeCOM 0.84-pre6 prerelease
> On Fri, Feb 22, 2019 at 5:44 PM Rugxulo wrote: >> >> I also did some minor fixes to my (unpublished, prerelease 0.7) MetaDOS. >> (If anybody cares, I could just upload it, but it's still not perfect, >> obviously. >> FYI, "Newwget" isn't publicly available anymore, so I'm partially preferring >> Curl. >> I haven't rebuilt those, ugh, annoying.) > Nobody said anything, so I didn't worry about it. But I did (barely) > just do minor fixes and finalize 0.7 and upload it to iBiblio for us. does it include a fixed freecom? does it run all tests? > Just in case you're interested. (Maybe I should waited until tomorrow > ... right, Tom? Right?? AM I RIGHT???) what am I supposed to do or say? Tom ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] default (lack of) buffering in Turbo C 2.01 (e.g. Cheap Sed)
Hi Rugxulo, > I thought you might find this interesting not at all ; see below. > since you're always once > raving recommending a trick used by X is not 'raving' > about old C compilers for DOS (e.g. you mentioned MSC 1990 in that > IA16-ELF thread). plural? btw: MSC was the reference compiler for freedos, some time ago. please do a reality check before your next post > I don't think we've personally discussed this issue > before. there is a lot of things we've not personally discussed. and prefer that this remains so. > Just for the record, "sed" is probably my favorite *nix util. So I've > used it quite a lot over the years (mostly in DOS!). next time, please add a TLDR section of your post like TLDR: if you use fread(), fgets() and friends AND care about performance, use setvbuf() with sensible parameters Tom ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
