There should be an option phpdoc header for where information on the latest
version of the the package/file can be obtained.
It should only appear in the mail file doc comment (that appears before any
code except for declaration of stict_types) and my when an automated system
makes a call to
I do not use an IDE. I do not like them.
Typically the only comments I put at the end of a bracket is for end of
class and end of function. End of class is not needed when the file only
contains a class, but it provides visual consistency.
I'm not sure why some people care if there is a comment
o mercoledì 16 maggio 2018 09:26:17 UTC+2, Alice Wonder ha scritto:
>>
>> I do not use an IDE. I do not like them.
>> Typically the only comments I put at the end of a bracket is for end of
>> class and end of function. End of class is not needed when the file only
Hi,
I'm working on a project for management of namespaced classes used within
WordPress via a PSR-4 autoloader.
I am not a WordPress developer, just someone sick of waiting for WordPress
to modernize.
What I'll be distribution is just a collection of un-modified interfaces
from the PSR
I prefer the first. I also prefer two spaces over four. When I am working
in a term window, space is an issue. Extra newlines means I can see fewer
lines at a time and extra 4 space tabs quickly forces the end of a line
horizontally out of my view.
I know most people like the second (and 4
I have a personal cache class that would be cake to port to use PSR-16, but
PSR-16 also defines two exception interfaces.
Is it really necessary I extend those two interfaces rather than extend a
different exception interface?
zetacomponents base package has an abstract exceptions class I
Burgess <demon...@gmail.com
> > wrote:
>
>> Purpose of the interfaces is to make those exact exception types
>> *catchable*... that's all.
>>
>> On Feb 24, 2018 13:56, "Alice Wonder" <alicedo...@gmail.com >
>> wrote:
>>
>>> I have
Okay I have a better expression of what I have in mind, I don't think I
communicated it well before, my mind works differently than most and that
results in communication problems, I am sorry.
https://github.com/AliceWonderMiscreations/ResourceManager
That's a github where I am starting to
Is there any desire to bring something like PSR-5 back?
There are two reasons why I think there should be some standards related to
the doc block.
A) For legal reasons, every file needs to have author(s) and license
specified in a way that it can be programmatically retrieved.
File level
to for roundcube to say it needs
jQuery X.
PHP class dependencies can be in separate packages thanks to autoloaders,
but not the JavaScript
On Thursday, March 1, 2018 at 5:29:39 PM UTC-8, Alice Wonder wrote:
>
> Hello,
>
> I have a php class that generates an HTML5 audio player
When one uses
"require": {
"psr/simple-cache": "^1.0"
}
The result when using vimeo/psalm to check the code has errors because of a
bug in the 1.0.0 release that is fixed in master but not fixed in a
released version:
expecting 'null|int|Psr\SimpleCache\DateInterval'
The
and right now that's what has to be done for
both composer and RPM installs.
On Sunday, March 4, 2018 at 3:13:24 PM UTC-8, Alice Wonder wrote:
>
> Yes I am extremely familiar with RPM and have been packaging RPMs since
> the Red Hat 6.0 days (pre Fedora)
>
> But they don't add
Hello,
I have a php class that generates an HTML5 audio player with support for
WebVTT captions and chapters and is very accessible.
It's a personal class, I am not distributing it as FLOSS and I probably
won't, but it uses jQuery and its own JavaScript and it's own CSS (in an
external file,
13 matches
Mail list logo
