public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin-apps@cygwin.com
Subject: Re: Zstandard support for setup
Date: Sun, 02 Sep 2018 08:31:00 -0000	[thread overview]
Message-ID: <87r2icl2th.fsf@Rainer.invalid> (raw)
In-Reply-To: <267037c7-7757-25ec-4b80-7ffcbc5768d6@dronecode.org.uk> (Jon	Turney's message of "Wed, 29 Aug 2018 17:42:43 +0100")

Jon Turney writes:
> This should check for ztd in configure.ac using PKG_CHECK_MODULES,
> rather than just assuming -lzstd is going to work.

Sure.  Waiting for your patch to actually use pkg_config to rebase it
onto.

> The setup executables are cross-built on Fedora, so a
> mingw{32,64}-zstd-static package will need to become available.

I don't have any contacts into the Fedora community, so I'd appreciate
if maybe Yaakov could help?  I have not yet found a distro that already
has packages for MinGW.

> compress_zstd.c:
>
> + using namespace std;
>
> Please don't

That's a copy from the compress_xz files and it's used in many files
elsewhere.  Care to explain why you'd want it removed?  If there's a
good reason I'd tend to move this to a clean-up commit that touches all
those files.  We should do that before hauling Zstdandard in.

> compress_zstd.h:
>
> +/* this is the parent class for all compress IO operations.
> + */
>
> Comment is incorrect

Another copy-paste, so that cleanup also needs to be applied to more
files (gz and xz).

> I'd suggest removing all the 'virtual' since this class is final, but
> since all the compress subclasses have it, don't bother.

Same as above, so we should clean up there first as well.

>> The debug output statements are still in the code (although commented),
>> I'll let that sit a while and see if I find something else I want to
>> clean up before I submit it for the upstream repo.
>
> I'd suggest keeping potentially useful ones under #ifdef DEBUG/#endif
> rather than just removing them all.

At the moment I'd rather remove them all as they were just meant for me
to check if things were working as I had assumed.  These produce a lot
more output than the usual debugging statements and you don't really
benefit if I keep just a subset enabled.  If we had a debugging facility
that knew about subsystems it would be a different matter (it's long
been on my TODO list, near the bottom unfortunately).

I'm attending a conference most of next week, so I need to postpone any
real work until the next weekend at the minimum.


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

Factory and User Sound Singles for Waldorf Blofeld:
http://Synth.Stromeko.net/Downloads.html#WaldorfSounds

  reply	other threads:[~2018-09-02  8:31 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-11 19:52 Achim Gratz
2018-08-12 13:28 ` Achim Gratz
2018-08-17 18:49 ` Achim Gratz
2018-08-20 18:11   ` Marco Atzeri
2018-08-20 19:54     ` Achim Gratz
2018-08-22 19:12   ` Achim Gratz
2018-08-23 20:40 ` Achim Gratz
2018-08-29 16:42 ` Jon Turney
2018-09-02  8:31   ` Achim Gratz [this message]
2018-09-02 17:03     ` Achim Gratz
2018-10-07 19:46       ` Jon Turney
2018-10-09 18:04         ` Achim Gratz
2018-10-07 22:09     ` Jon Turney
2018-10-09 18:05       ` Achim Gratz
2018-10-10 18:37   ` Achim Gratz
2018-10-13 17:19     ` Jon Turney
2018-10-14 11:29       ` Achim Gratz

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87r2icl2th.fsf@Rainer.invalid \
    --to=stromeko@nexgo.de \
    --cc=cygwin-apps@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).