W3C home > Mailing lists > Public > public-webapps@w3.org > January to March 2015

RE: Defining a constructor for Element and friends

From: Domenic Denicola <d@domenic.me>
Date: Wed, 14 Jan 2015 04:26:03 +0000
To: Bjoern Hoehrmann <derhoermi@gmx.net>
CC: WebApps WG <public-webapps@w3.org>, "www-dom@w3.org" <www-dom@w3.org>
Message-ID: <CY1PR0501MB13691404E3C4EBE8F234F3F0DF410@CY1PR0501MB1369.namprd05.prod.outlook.com>
From: Bjoern Hoehrmann [mailto:derhoermi@gmx.net] 

> I know that this a major concern to you, but my impression is that few if any other people regard that as anything more than "nice to have", especially if you equate "explaining" with having a public API for it.

How do you propose having a private constructor API?

How do you propose instances of the objects even existing at all, if there is no constructor that creates them?

This is one of those "only makes sense to a C++ programmer" things.

Received on Wednesday, 14 January 2015 04:26:35 UTC

This archive was generated by hypermail 2.3.1 : Friday, 27 October 2017 07:27:25 UTC