Heh... I guess I replicated this poll in the PhpED discussion forum... oh well..... either way it should get looked at.

OFF TOPIC: First of all sorry for delay, I was trying to fix some bugs in my scripts



Thank you very much for your explanation. The first paragraph is clear for me (function name compilation with two parentheses and cursor between them) but the second one no I have tried to enable ACB and do the function name compilation as I did it before but there were no errors. I can not get double closing parentheses at the end. Here is all operations which I am doing:

1) I am typing first letters of function name (str_)
2) I am pressing ctrl+space to see the function list
3) I am choosing appropriate one (in case if it is not first one in the list) and I am hitting enter key
4) I am starting adding function parameters (cursor is already moved to correct place)

So up to this point I can not see any problem, may be I have to do something else or ...

Thank you in advance

Hehe okay. Let me try to explain it.

First, imagine not using the code completion but simply typing the function name with ACB enabled:
substr(|) (the bracket in bold is automatically added by the editor and | is where the cursor is).
Now you type the arguments, as normal
substr("test",1, 2|) (again, same thing with bold and cursor)

Now comes the part what this discussion is all about: You type the closing bracket yourself:
substr("test",1, 2)|
In most editors the behavior is to "remember" that it added the closing bracket, and if you type one yourself, you'll overwrite the editor-added one (or it will be skipped as is asked here in the poll, same result), which yields the correct string.
What PHPed does right now, is add a second bracket, like so:
substr("test",1, 2)|)

So the discussion is if this should be changed to match the default behavior in the other editors out there.

The code completion already adds both opening and closing bracket, but imo if the functionality described above is implemented for the ACB option, it should work the same for snippets of code inserted by the code completion.
Hope that makes everything clear.

Thanks, now everything is clear

I think this feature should be implemented not just because it was requested by several PHP developers but because it is better for PhpED itself. As much PhpED will be flexible (will have the features which other debuggers have and even more) as more users will easier move from other debuggers. So my answer "yes".

p.s. but I will suggest to type both open and close parentheses at the same time, the same to the bracket and other paired signs like: (), "", '', {}. In this case you will never forgot to type closing one

a) there is nothing wrong with parentheses that are inserted by code completion.
b) over-typing (or keep brace-balancing) is another feature requested there and we need volunteers to check if what we're going to release as build 5021 satisfies them. Please submit your applications in pm to me on this forum. Don't forget to include your status (evaluator vs customer) and provide customer info (if any).
Thanks in advance,
Dmitri.

Thanks for fixing this. I am now a satisfied customer.