Should the copyright date from "emcc --version" be updated?

[John Dallman]

Currently it still says 2014,as of the emcc and em++ I'm using 3.1.71.

John

[Sam Clegg]

The copyright dates in our headers only mention the creation date rather than a date range.  e.g 2014 rather than 2014-2025.  This avoids the tedious task and churn of updating all files every year.

I think we just apply the same policy here in our `--version` output.   I'm not sure if it's worth updating this date every year? 

cheers

sam 

On Wed, Feb 12, 2025 at 7:04 AM John Dallman <jgdats...@gmail.com> wrote:

Currently it still says 2014,as of the emcc and em++ I'm using 3.1.71.

John

--
You received this message because you are subscribed to the Google Groups "emscripten-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to emscripten-disc...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/emscripten-discuss/CAH1xqgn3KRZDcOVJKkYgwNSokh0DrdRhWy%3D5pa7KCXQ6sWpi-Q%40mail.gmail.com.

[Sam Clegg]

I created a PR to update the year reported by --version: https://github.com/emscripten-core/emscripten/pull/23662

[John Dallman]

Thanks! The product I'm working on is extremely careful about compiler version changes, and there would be endless questions about "have we got an old version?" 

When I say "extremely careful", the build system for it refuses to build if the compiler version has changed and the new version hasn't been registered as the correct one. The product is very sensitive to changes in floating point expression optimization, so new compiler versions have to be validated. We have done compiler upgrades without finding new problems, but even in the present day, those are quite rare. 

John 

To view this discussion visit https://groups.google.com/d/msgid/emscripten-discuss/CAL_va298KbQ7mLJ8xQRdxhqZ500E%3Do-ZcUXHPE8hhne91tbrpA%40mail.gmail.com.