Req #72768 [Com]: Add ENABLE_VIRTUAL_TERMINAL_PROCESSING flag for php.exe

From: Date: Thu, 24 Sep 2020 11:11:46 +0000
Subject: Req #72768 [Com]: Add ENABLE_VIRTUAL_TERMINAL_PROCESSING flag for php.exe
References: 1  Groups: php.bugs 
Request: Send a blank email to php-bugs+get-229202@lists.php.net to get a copy of this message
Edit report at https://bugs.php.net/bug.php?id=72768&edit=1

 ID:                 72768
 Comment by:         jaguarsoftwareindia at gmail dot com
 Reported by:        mlocati at gmail dot com
 Summary:            Add ENABLE_VIRTUAL_TERMINAL_PROCESSING flag for
                     php.exe
 Status:             Closed
 Type:               Feature/Change Request
 Package:            Output Control
 Operating System:   Windows 10
 PHP Version:        Irrelevant
 Assigned To:        ab
 Block user comment: N
 Private report:     N

 New Comment:

NBFC loan management software: We have multiple Loan Management Software Products to cater to
companies of all sizes, We help you manage your company efficiently 
visit:  https://jaguarsoftwareindia.com/nbfc-loan-management-software/


Previous Comments:
------------------------------------------------------------------------
[2020-09-24 10:42:02] maacbangalore123 at gmail dot com

skin lightening treatment in Bangalore: MAAC offers one of the best skin whitening treatments cost
in Bangalore with excellent and successful cosmetic treatments
visit:  https://www.maac.co.in/maac-face-body-whitenining-treatment.html

------------------------------------------------------------------------
[2020-09-24 09:33:54] digimarkagency at gmail dot com

Digimark is the best SEO Company and SEO experts in Bangalore. As a top SEO agency, We offer the
best SEO Services in Bangalore to help all types of business.

visit: https://digimarkagency.com/seo-company-bangalore.html

------------------------------------------------------------------------
[2016-10-28 18:53:11] ab@php.net

The PR is merged into master.

Thanks.

------------------------------------------------------------------------
[2016-08-30 08:24:23] mlocati at gmail dot com

Here's the PR on GitHub: https://github.com/php/php-src/pull/2103

------------------------------------------------------------------------
[2016-08-29 14:55:57] ab@php.net

@mlocati, thanks for all the work so far.

I made a quick look over your latest patch so far, a couple of comments already.

Please check the coding style doc for function naming conventions, etc.
http://git.php.net/?p=php-src.git;a=blob;f=CODING_STANDARDS;h=5cf70c92b5f5ab06977629ba6fff87255cc80116;hb=HEAD
. Particularly, in most casse the internal APIs should be prefixed with php_*, and Windows specific
with php_win32_*. Also the underscore is used for separation, etc. Please see other sources there.

Also the following regarding the code:

- the Unicode APIs have to be used, where it matters in 7.1+. Fe GetFinalPathNameByHandleW. Please
check the corresponding helper routines in win32/ioutil.h.
- usually we don't use the driver routines, Rtl*, etc. Regarding getting the version,
there's quite some functionality already in the core, please check EG(windows_version_info). It
should suffice as till now the only case is the usage after MINIT is bypassed.
- please don't use static vars in functions, until it's thread safe
- for the streams, particularly main/streams/plain_wrapper.c were relevant for STDIO. Taking some
stream and stepping through it in the debugger might help for better understanding. Basically, a
stream resource needs to be passed, as the fd might be duped but still point to a vt100 term.
- tests are required :)

Indeed, it might be handier to discuss the patch in a github PR, which you already can attach to
this ticket.

Thanks.

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


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=72768


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


Thread (38 messages)

« previous php.bugs (#229202) next »