may still have data and people may have to
use it)
* http://queryr.wmflabs.org/api/items/Q42/data/occupation returns only
one value, shouldn't it return multiple ones?
--
Stas Malyshev
smalys...@wikimedia.org
___
Wikidata mailing list
Wikidata@lists.wiki
nce
> UUID like this:
I'm not sure I understand - what would doing this earn us? This looks
like just adding one more join to the lookups.
--
Stas Malyshev
smalys...@wikimedia.org
___
Wikidata-tech mailing list
Wikidata-tech@lists.wikimedia.org
https://l
s: Could you have a look?
Yes, looks like there's a large volume of updates, so the service is
several hours behind, but it seems to be catching up now. What's the bot
is doing?
--
Stas Malyshev
smalys...@wikimedia.org
___
Wikidata mailing list
Wikidata@l
ote on Succu's talk
page to discuss it.
--
Stas Malyshev
smalys...@wikimedia.org
___
Wikidata mailing list
Wikidata@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikidata
in Wikidata in about 2 weeks, which seems to be
OK for most tasks. But it is a limitation and as I said, I'll work to
eventually get rid of it.
Thanks,
--
Stas Malyshev
smalys...@wikimedia.org
___
Wikidata mailing list
Wikidata@lists.wikimedia.org
https
o do:
PREFIX wdt: <http://www.wikidata.org/prop/direct/>
SELECT ?book ?isbn WHERE {
VALUES ?isbn { "2-7071-1620-3" "2-7071-1620-4" "2-7071-1620-5" ... }
?book wdt:P957 ?isbn
}
Unless I misunderstand what you mean here.
--
Stas Malyshev
smalys...@wikimedia.o
whose bot
it is please ask that person to seek advice and guidance (which I would
be glad to provide) on how to make it work properly :)
--
Stas Malyshev
smalys...@wikimedia.org
___
Wikidata mailing list
Wikidata@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikidata
his query and browser gets out of memory. Try this query with LIMIT 10
first and see what happens.
As for the bot activities affecting other users, the effect seems to be
negligible, so if this query is slow, it is slow on its own merits :)
--
Stas Malyshev
smalys...@wiki
nts or needs the
> same tooling..
We have export formats - CSV, TSV, JSON, etc. (look for "Download
results" link on the right side). If you would like to see any other
format that is not supported now, please ask (best in the form of
Phabricator ticket but writing on feedback page or m
ble. I don't know yet why, I'll look at it further,
probably next week.
So the problem is not "handling cycles" in general, it is handling some
specific data set, and most probably is a consequence of some bug. I'll
report when I have more data about what exactly triggers the bug.
--
Stas
efinitely an
> error. ;-)
Right. So I think we need to mark properties that should not form cycles
with
https://www.wikidata.org/wiki/Q18647519 (asymmetric property) and have
constraints checking scripts/bots find out such cases and alert about them.
--
Stas Malyshev
smalys...@w
any
instances. So my question is - what is the use of modeling something as
a class if there won't be ever any instances of the class modeled?
--
Stas Malyshev
smalys...@wikimedia.org
___
Wikidata mailing list
Wikidata@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikidata
wikipedia.org/wiki/Getty%20Thesaurus%20of%20Geographic%20Names
Not sure if it's a problem or not.
But the sitelinks should be updated now.
--
Stas Malyshev
smalys...@wikimedia.org
___
Wikidata-tech mailing list
Wikidata-tech@lists.wikimedia.org
https://l
s
then Preferred ones, otherwise Normal ones but never Deprecated ones.
--
Stas Malyshev
smalys...@wikimedia.org
___
Wikidata mailing list
Wikidata@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikidata
ch should be enough to merge it.
Not sure if those one-off things worth bothering with, just putting it
out there to consider.
--
Stas Malyshev
smalys...@wikimedia.org
___
Wikidata mailing list
Wikidata@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikidata
er.
Should probably be https://query.wikidata.org/bigdata/namespace/wdq/sparql
That works for me.
--
Stas Malyshev
smalys...@wikimedia.org
___
Wikidata mailing list
Wikidata@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikidata
es, in theory it should be fast, so I suspect some kind of bug.
--
Stas Malyshev
smalys...@wikimedia.org
___
Wikidata mailing list
Wikidata@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikidata
the engine that would
be supporting that.
--
Stas Malyshev
smalys...@wikimedia.org
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
ou intended to write query that asks for 10 records but accidentally
wrote one that returns 10 million, it's much nicer to discover it with
suitable limit than waiting for the query to time out and then try to
figure out why it happened.
Yes, I realize all this has to go to some page i
people now to main endpoint as it
is much better at handling the load.
--
Stas Malyshev
smalys...@wikimedia.org
___
Wikidata mailing list
Wikidata@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikidata
inging
it to my attention.
--
Stas Malyshev
smalys...@wikimedia.org
___
Wikidata mailing list
Wikidata@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikidata
vice to unbound variables. If you drop ?headLabel
then it works. It is a downside of the label service, not sure yet how
to fix it (feel free to submit the Phabricator issue, maybe myself or
somebody else has an idea later).
--
Stas Malyshev
smalys..
bly would be the way to fix it.
--
Stas Malyshev
smalys...@wikimedia.org
___
Wikidata mailing list
Wikidata@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikidata
it timed out for me (I was using a very common reference
> though ;-). For rarer references, live queries are definitely the better
> approach.
Works for me for Q216047, didn't check others though. For a popular
references, labs one may be too slow, indeed. A faster one is coming
"real
Hi!
>
> Introducing… The Wikidata Query Service dashboard:
> http://searchdata.wmflabs.org/wdqs/ ! Yay! Hopefully this will help the
> WDQS team as they continue their work on that awesome project.
Yay! Thank you Mikhail!
--
Stas Malyshev
smalys...@w
l be no dependency on the current content of Wikidata's Q199.
We already have such dependencies - e.g. in calendars and globes - so it
won't be anything new. But let's see what the Wikidata team thinks about
it :)
--
Stas Malyshev
smalys...@wikimedia.org
___
un queries against quantities with units (and I think we do, don't
we?) then we would need to figure out the common basis at least for
common units. I wonder if it's tracked somewhere?
--
Stas Malyshev
smalys...@wikimedia.org
___
Wikidata mai
gYear to be completely
different types and as such some queries between them would not work.
--
Stas Malyshev
smalys...@wikimedia.org
___
Wikidata-tech mailing list
Wikidata-tech@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikidata-tech
/tree/master/gui may also
be the way to do it ;)
--
Stas Malyshev
smalys...@wikimedia.org
___
Wikidata-tech mailing list
Wikidata-tech@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikidata-tech
Hi!
I uploaded a small HTML page to compare both approaches:
http://cirrus-browser-bot.wmflabs.org/suggest.html
This is very cool! From my very short testing, seems that it works
pretty nicely.
--
Stas Malyshev
smalys...@wikimedia.org
) and it may be more precise indicator
than just name. Not sure which way is the best to search for it though.
--
Stas Malyshev
smalys...@wikimedia.org
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo
to the notes.
--
Stas Malyshev
smalys...@wikimedia.org
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
not to be allowed in the first place) I'd like to merge it in 7.0.0.
Please object if you think this should not be done and explain why.
Otherwise I intend to merge it after a suitable wait and after adding
necessary tests/docs.
Thanks,
--
Stas Malyshev
smalys...@gmail.com
of fear that uneducated
FUD may hurt our reputation does not sound like a winning strategy for me.
--
Stas Malyshev
smalys...@wikimedia.org
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech
of these sites are public-facing (and due
to the nature of wikis, many of them, to some measure, are), running
out-of-support software may not be that good an idea.
--
Stas Malyshev
smalys...@wikimedia.org
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
://tools.wmflabs.org/wdq2sparql/w2s.php)
- once the labs outage ends of course - to convert between WDQ syntax
and SPARQL. Also check out other links on the WDQS beta page for short
intros about how things are done with SPARQL and examples of which
queries you can run.
--
Stas Malyshev
smalys
yet
both operationally and data-model-wise, so please be aware of this, also
it has timeout limits that won't allow you for now to run queries that
are too complex. But if you want to check it out and see if that fits
your use case you are most welcome.
[1] http://wdqs-beta.wmflabs.org/
--
Stas
individual
entity actually is - I'm sure you have one that matches your
application, but some other application may have completely different one.
Generally, this can be solved by better classification I think, but so
far I'm not sure what to base this classification on.
--
Stas Malyshev
smalys
Hi!
The links would point to the standard export URLs:
* https://www.wikidata.org/wiki/Special:EntityData/Q423111.json
* https://www.wikidata.org/wiki/Special:EntityData/Q423111.rdf
Speaking about these, shouldn't we also have link rel=alternate for
export formats in the header?
--
Stas
be raised significantly (and
also performance would be better) once we get it to production.
--
Stas Malyshev
smalys...@wikimedia.org
___
Wikidata mailing list
Wikidata@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikidata
. Some of them are tough to classify or link to
anything, but some are rather obvious.
--
Stas Malyshev
smalys...@wikimedia.org
___
Wikidata mailing list
Wikidata@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikidata
.
--
Stas Malyshev
smalys...@wikimedia.org
___
Wikidata mailing list
Wikidata@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikidata
you'll encounter one of
them. That could also happen with Test plan - nobody guaranteed it
wouldn't say everything fine, and being +2ed, and still break down.
reviewing it promptly, but typing: Test Plan: I didn't test this patch at
That I have no objections to.
--
Stas Malyshev
smalys
sucks and they have to work around it to be effective.
--
Stas Malyshev
smalys...@wikimedia.org
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
WMF nor WMDE maintains. It's one thing to
make new service (which btw I think is an awesome idea, just wanted to
say it so that it would be clear than I am not criticizing the whole
idea, just this aspect of it) and another add subtle changes to an
existing one.
--
Stas Malyshev
smalys
server with only one database and only one
table - why not use separation that already comes for free with another
instance? We still can reuse any code we like.
--
Stas Malyshev
smalys...@wikimedia.org
___
Wikidata-l mailing list
Wikidata-l
structure would produce?
--
Stas Malyshev
smalys...@wikimedia.org
___
Wikidata-l mailing list
Wikidata-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikidata-l
/iconv/iconv_prog.c.html. Again,
that would require custom patch for PHP, not sure about hhvm.
--
Stas Malyshev
smalys...@wikimedia.org
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
some missing parts (see https://phabricator.wikimedia.org/T50143),
though dumpJson should be safe to use if you want JSON. We're actively
working on the RDF part so it will be ready for use soon too.
--
Stas Malyshev
smalys...@wikimedia.org
___
Wikidata-l
Hi!
use ISO standards. One of the reasons is their impartiality (in the
meaning that they are not related to one specific language).
Wikidata labels, however, *are* related to specific language. Every
label is associated with the language.
--
Stas Malyshev
smalys...@wikimedia.org
Hi!
What about people who were born in the 18th-century? We know they are
dead, but their death is not recorded and we only know when they were
last active. How do you set that end date?
That's what somevalue/unknown is for.
--
Stas Malyshev
smalys...@wikimedia.org
there might be cases where it is useful,
still not on references. But I think maybe not forbidding as such but
having the guideline on what is considered the Right Thing and then if
there's an exception than the editors can use their own judgement.
--
Stas Malyshev
smalys...@wikimedia.org
it does make sense.
--
Stas Malyshev
smalys...@wikimedia.org
___
Wikidata-l mailing list
Wikidata-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikidata-l
people, neither experienced nor new.
--
Stas Malyshev
smalys...@wikimedia.org
___
Wikidata-l mailing list
Wikidata-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikidata-l
.
https://www.wikidata.org/wiki/Q16354757 is not Wikibase Data model :)
Which reminds me of https://www.wikidata.org/wiki/Q1061035 ...
--
Stas Malyshev
smalys...@wikimedia.org
___
Wikidata-l mailing list
Wikidata-l@lists.wikimedia.org
https
:
http://esr.ibiblio.org/?p=6737
--
Stas Malyshev
smalys...@wikimedia.org
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Hi!
Hi, there is items about Wikibase data model in Wikidata (created by me,
but not only)
If I understand correctly, they could be cited in the semantic web as
https://www.wikidata.org/entity/Q19798647
What would be the purpose of these items? I.e., what is the intended usage?
--
Stas
://www.wikidata.org/wiki/Q1187613's is Уотсон. And I have no idea
what is the correct romanization of
https://www.wikidata.org/wiki/Q4105300's name.
--
Stas Malyshev
smalys...@wikimedia.org
___
Wikidata-l mailing list
Wikidata-l@lists.wikimedia.org
https
once ranks are used more widely to
mark it.
I think this is solved with preferred ranks and truthy statements
concept pretty nice. So people should start using ranks to separate
current data from historical data.
--
Stas Malyshev
smalys...@wikimedia.org
https://www.wikidata.org/wiki/Property:P1207
Q42 is a treasure trove for these :) Will see if there is more.
--
Stas Malyshev
smalys...@wikimedia.org
___
Wikidata-l mailing list
Wikidata-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman
of encyclopaedic knowledge.
It's indeed important, so I think the idea is not to diminish their
importance somehow but to give them separate space which may lead to
improved workflows for both data properties and external ID properties.
--
Stas Malyshev
smalys...@wikimedia.org
Hi!
I agree this would be a nice idea. I believe it would be relatively easy to
do,
if only properties could have properties of their own.
AFAIK they can, e.g. https://www.wikidata.org/wiki/Property:P35
--
Stas Malyshev
smalys...@wikimedia.org
https://www.wikidata.org/wiki/Property:P1628 with
Freebase full URIs.
I think using https://www.wikidata.org/wiki/Property:P1628 is a good
idea. It may also be useful to add qualifier of (P642) to
https://www.wikidata.org/wiki/Q1453477 (Freebase).
--
Stas Malyshev
smalys...@wikimedia.org
, but Facebook,
Twitter, various chat clients, I think several Wordpress plugins, etc.
https://phabricator.wikimedia.org/T8
I wonder if this can somehow be connected to Wikidata's image attribute
(https://www.wikidata.org/wiki/Property:P18).
--
Stas Malyshev
smalys...@wikimedia.org
me. Other
comments/thoughts/suggestions also welcome.
--
Stas Malyshev
smalys...@wikimedia.org
___
Wikidata-tech mailing list
Wikidata-tech@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikidata-tech
soon and see how it
behaves. Some of the WDQ features - such is wide branching with OR
options - may be quite inefficient in SPARQL, but we can generate it
anyway. I'll update when I have something interesting (probably next week).
--
Stas Malyshev
smalys...@wikimedia.org
to get out of the bad function
without incurring per-function overhead... Not sure how to do it.
--
Stas Malyshev
smalys...@gmail.com
On Mar 11, 2015 7:01 PM, Stas Malyshev smalys...@gmail.com wrote:
Hi!
Instead of throwing zend_error() from signal handler, now we just set
EG(vm_interrupt) and EG(timed_out) flags. PHP VM checks EG(vm_interrupt)
flag on each JMPx instruction (potential loop iteration) and then throws
in
SPARQL which may take some time, since these languages are a bit
different (esp. in tree traversal aspects). But I think WDQ language
support should be on the agenda, I'm just not sure it should be the
first item.
--
Stas Malyshev
smalys...@wikimedia.org
name may have completely different semantics. In Wikidata,
however, properties are generic, so I wonder if it would be possible to
keep context. dbPedia obviously does have context but not sure where it
would be in Wikidata.
--
Stas Malyshev
smalys...@wikimedia.org
.
Saying a problem doesn't exist doesn't make it go away.
Except if it really doesn't exist, so there's nothing to go away :)
--
Stas Malyshev
smalys...@gmail.com
of time :)
--
Stas Malyshev
smalys...@wikimedia.org
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
where to contribute and on which condition is entirely yours, but
I *personally* would view such stance as somewhat counterproductive, if
your goal is to contribute to the world's repository of high quality
software that can be accessed to everyone.
--
Stas Malyshev
smalys...@wikimedia.org
does it. It's in fashion.
You don't have to force people to follow the fashion. So I wonder if
spending time worrying about if the license is strong enough and
defensive enough is something worth doing now.
--
Stas Malyshev
smalys...@wikimedia.org
typing that can be eliminated by stronger types (for scalar
types, conversions and type branches in operators, parameter passing,
etc. can be eliminated).
--
Stas Malyshev
smalys...@wikimedia.org
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
.
--
Stas Malyshev
smalys...@wikimedia.org
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
for capturing internal docs,
discussions, plans, etc.) there may be legal and confidentiality reasons
that do not allow using services crossing the firewall.
--
Stas Malyshev
smalys...@wikimedia.org
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
is not very fast
in PHP, but is pretty strict. Still, there's a chance people could sneak
something past it.
--
Stas Malyshev
smalys...@wikimedia.org
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo
. Of
course, that means some functions would not be available everywhere -
but I don't see a good way to avoid it when the requirements diverge.
--
Stas Malyshev
smalys...@wikimedia.org
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https
the
willing people from the community do it)? Is the $2/month use case
important enough to actually do it?
--
Stas Malyshev
smalys...@wikimedia.org
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo
, or maybe different units with intersecting sets of people.
--
Stas Malyshev
smalys...@wikimedia.org
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
-scale resolution. I'm not sure what coordinates can be even
known with such resolution, let alone be needed for anything practical.
[1]
https://en.wikipedia.org/wiki/Wikipedia:WikiProject_Geographical_coordinates#Precision_guidelines
Thanks,
--
Stas Malyshev
smalys...@wikimedia.org
Hi!
On Sun, Dec 28, 2014 at 10:54 PM, Kalle Sommer Nielsen ka...@php.net
wrote:
Commit:334b9718d578caa9f4c6d3c2f7e2fb9b65696dc3
Author:Kalle Sommer Nielsen ka...@php.net Mon, 29 Dec 2014
07:54:44 +0100
Parents: 3bd96e0735f45359bc3cff2981acbd34c60770c9
Branches: master
Hi!
The best place for this kind of question would be the wikidata-tech mailing
list
wikidata-tech@lists.wikimedia.org. It would probably be a good idea if you
(and whoever else deals with wikidata on the technical level) were subscribed
there. It's pretty low traffic.
Thanks, I've sent
is
not correct.
--
Stas Malyshev
smalys...@gmail.com
Hi!
I don’t like the sound of changing the spec before the implementation.
I agree - whatever are our considerations and limitations on what we can
and can not do in PHP 7, the spec should reflect what is there.
Otherwise we end up releasing an implementation that does not match our
own spec,
Hi!
makes user land code more readily equipped to enable the user to do that
handling. In the same way that it does for POST. This creates some more
Well, for POST PHP actually parses the data - url encoding, form
encoding, files, etc. - and puts it into the data structure. For generic
REST
Hi!
What I want to implement is the ability to allow arbitrary expressions on
the second operand, so instead of having to write something like this:
I'm afraid there's a problem with this. Arbitrary expressions include
constants, right? So what this means:
var_dump($foo instanceof Bar);
is
Hi!
Also one thing not mentioned in the initial letter - this will also allow
you to use expressions for new operator in the same way: `new
(str_replace('/', '\\', $classPath))()` - just an example.
OK, if we apply it consistently - i.e. say anywhere that we allow
literal or
Hi!
This is exactly what I'm doing right now, requiring the expression to
always be enclosed in parenthesis. I think it's way better to be able to
do this instead of creating temporary variables just to assign a class
Why? What's so bad in variables? It doesn't cost that much and makes you
Hi!
- major BC break: major versions only. 5 major BC breaks allowed per major
version.
I'm not sure how such numbers make sense. Why 5 and not 3 or 7 or 17? If
that breaks your code, even one is too much. If your code is not
affected, why would you care if it's 5 or 15 or 150? I'm afraid this
Hi!
Again, I think you're oversimplifying the problem. For one, you don't know
that the payload is JSON unless you check the Content-type header yourself,
and you really shouldn't have to since PHP could easily do this for you.
Sure, PHP could easily do this, or any other one specific use
Hi!
Do we always load the class in the hint? We could perhaps only do it
for inheritance checks?
No, classes are not loaded for type checks, since it would be pointless
- if the class is not loaded, you could not have a value of that type,
so if the class is not present, the answer is no.
--
Hi!
No, classes are not loaded for type checks, since it would be pointless
- if the class is not loaded, you could not have a value of that type,
so if the class is not present, the answer is no.
It's not true anymore, with this proposal.
This is not good. The base premise
Hi!
put types only on the right, or only on the left or mix it. I
followed the return type RFC and thus know that many people think it
has to be on the left hand side. Fair enough, I do not have anything
against such a decision. I also have nothing against putting the type
on the right hand
Hi!
As I do consider personal tastes important, there are times where we should
listen to our users.
It would be nice to take paving the walkways approach, but last time
we tried, IIRC we've got into something very over-engineered. Maybe if
we try again with more restricted scope (i.e. not
Hi!
public Foo function bar() would be so much worse than public function
bar() : Foo
Because when you grep for function bar, in future you'd have to know
the return type too.
Sorry, I do not understand - why to grep for function bar you'd have
to know the type? Just grep for function bar
Hi!
I thought it was inconsistent, but after discussions on
StackOverflow, I don't think it actually is.
If you specify the type once as Foo something and once as something:
Foo then I don't see how there's even a place for discussions that it's
inconsistent.
Return types describe the return
Hi!
In PHP, input types go on the left and output types go on the right.
What is the output type? If I wanted to type a variable - is it input
or output?
--
Stanislav Malyshev, Software Architect
SugarCRM: http://www.sugarcrm.com/
--
PHP Internals - PHP Runtime Development Mailing List
To
Hi!
All projects mentioned in this thread use:
http://doctrine-common.readthedocs.org/en/latest/reference/annotations.html
That makes a pretty good base spec.
Reading it, it looks pretty big - strictly typed values, named
parameters, default constructors linked to properties, support for enum
401 - 500 of 2366 matches
Mail list logo