Bug #78692 [Com]: define() and defined() not behaving correctly on Windows 10

From: Date: Sat, 19 Oct 2019 21:43:07 +0000
Subject: Bug #78692 [Com]: define() and defined() not behaving correctly on Windows 10
References: 1  Groups: php.bugs 
Request: Send a blank email to php-bugs+get-223311@lists.php.net to get a copy of this message
Edit report at https://bugs.php.net/bug.php?id=78692&edit=1

 ID:                 78692
 Comment by:         bugreportsxxy at gmail dot com
 Reported by:        security at paragonie dot com
 Summary:            define() and defined() not behaving correctly on
                     Windows 10
 Status:             Assigned
 Type:               Bug
 Package:            *General Issues
 Operating System:   Windows
 PHP Version:        7.2.15
 Assigned To:        cmb
 Block user comment: N
 Private report:     N

 New Comment:

Dan Ackroyd

any activity at the PHP project in the last 3 years was from my personal accounts so please stop
drinking while think "appropriate authorities" are any company contact


Previous Comments:
------------------------------------------------------------------------
[2019-10-19 21:13:17] bugreportsxxx at gmail dot com

and you f**r have no point for "Future attempts to evade the ban may result in your abuse being
reported to the appropriate authorities" -

if you have something to say about what i do from my home network in my free time at 1:00 AM with no
context to any company account or network grow up, grab your balls and sort it out with me
personally

come on, sue me!

https://bugs.php.net/bug.php?id=78501

------------------------------------------------------------------------
[2019-10-19 16:56:18] danack@php.net

Harald,

You are still banned from this project. 

https://bugs.php.net/bug.php?id=78098


Dan

------------------------------------------------------------------------
[2019-10-19 15:46:10] security at paragonie dot com

> and here we are now instead doing your homework by just try the latest version and if that
> donät fix the problem and you correctly report for 5.2.23 from the begin 4 upstream actions could
> have been saved or probably the problem is gone away at all in the meantime

You aren't doing my homework.

I literally reported this out of due diligence. You don't have to do anything with this
information.

If you still consider this a "waste" of YOUR time, stop participating in this thread and
let someone with more {patience, capacity to understand human communication and context} handle this
instead.

I'm sorry you don't see the value in communicating information. It's not even
assigned to you anyway.

------------------------------------------------------------------------
[2019-10-19 15:30:19] bugreports at gmail dot com

> Making sure that upstream projects have a ticket onhand 
> for behavior reported in downstream projects

in case when you simply can try if the problem still exists for sure because if it no longer exists
there likely was already a ticket long ago which was solved 

* you startet even with the wrong major version
* pointed out
* fixed
* Did upgrading to any more recent PHP 7.2 solve the issue?

and here we are now instead doing your homework by just try the latest version and if that donät
fix the problem and you correctly report for 5.2.23 from the begin 4 upstream actions could have
been saved or probably the problem is gone away at all in the meantime

------------------------------------------------------------------------
[2019-10-19 15:24:18] security at paragonie dot com

> bugrports at gmail dot com:
>
> people *really* should refrain from wasting others time by reporting bugs for versions like
> 7.2.15 when 7.2.23 is out for weeks

Making sure that upstream projects have a ticket onhand for behavior reported in downstream projects
(and taking care to make this clear in my bug report) is considered a "wasting others
time" now? TIL.

------------------------------------------------------------------------


The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at

    https://bugs.php.net/bug.php?id=78692


--
Edit this bug report at https://bugs.php.net/bug.php?id=78692&edit=1


Thread (15 messages)

« previous php.bugs (#223311) next »