|
libpqxx
4.0.1
|
Accessor for large object's contents. More...
#include <largeobject.hxx>
Public Types | |
| typedef long | off_type |
| typedef size_type | pos_type |
| typedef std::ios::openmode | openmode |
Open mode: in , out (can be combined with the "or" operator) | |
| typedef std::ios::seekdir | seekdir |
Seek direction: beg , cur , end . | |
| typedef long | size_type |
Public Member Functions | |
| largeobjectaccess (dbtransaction &T, openmode mode=std::ios::in|std::ios::out) | |
| Create new large object and open it. | |
| largeobjectaccess (dbtransaction &T, oid O, openmode mode=std::ios::in|std::ios::out) | |
| Open large object with given oid. | |
| largeobjectaccess (dbtransaction &T, largeobject O, openmode mode=std::ios::in|std::ios::out) | |
| Open given large object. | |
| largeobjectaccess (dbtransaction &T, const std::string &File, openmode mode=std::ios::in|std::ios::out) | |
| Import large object from a local file and open it. | |
| ~largeobjectaccess () throw () | |
| void | to_file (const std::string &File) const |
| Export large object's contents to a local file. | |
High-level access to object contents | |
| void | write (const char Buf[], size_type Len) |
| Write data to large object. | |
| void | write (const std::string &Buf) |
| Write string to large object. | |
| size_type | read (char Buf[], size_type Len) |
| Read data from large object. | |
| size_type | seek (size_type dest, seekdir dir) |
| Seek in large object's data stream. | |
| size_type | tell () const |
| Report current position in large object's data stream. | |
Low-level access to object contents | |
These functions provide a more "C-like" access interface, returning special values instead of throwing exceptions on error. These functions are generally best avoided in favour of the high-level access functions, which behave more like C++ functions should. | |
| pos_type | cseek (off_type dest, seekdir dir) throw () |
| Seek in large object's data stream. | |
| off_type | cwrite (const char Buf[], size_type Len) throw () |
| Write to large object's data stream. | |
| off_type | cread (char Buf[], size_type Len) throw () |
| Read from large object's data stream. | |
| pos_type | ctell () const throw () |
| Report current position in large object's data stream. | |
Error/warning output | |
| void | process_notice (const std::string &) throw () |
| Issue message to transaction's notice processor. |
Additional Inherited Members | |
| Private Types inherited from pqxx::largeobject | |
| typedef long | size_type |
| Private Member Functions inherited from pqxx::largeobject | |
| largeobject () throw () | |
| Refer to a nonexistent large object (similar to what a null pointer does) | |
| largeobject (dbtransaction &T) | |
| Create new large object. | |
| largeobject (oid O) throw () | |
| Wrap object with given oid. | |
| largeobject (dbtransaction &T, const std::string &File) | |
| Import large object from a local file. | |
| largeobject (const largeobjectaccess &O) throw () | |
| Take identity of an opened large object. | |
| oid | id () const throw () |
| Object identifier. | |
| void | to_file (dbtransaction &T, const std::string &File) const |
| Export large object's contents to a local file. | |
| void | remove (dbtransaction &T) const |
| Delete large object from database. | |
| bool | operator== (const largeobject &other) const |
| Compare object identities. | |
| bool | operator!= (const largeobject &other) const |
| Compare object identities. | |
| bool | operator<= (const largeobject &other) const |
| Compare object identities. | |
| bool | operator>= (const largeobject &other) const |
| Compare object identities. | |
| bool | operator< (const largeobject &other) const |
| Compare object identities. | |
| bool | operator> (const largeobject &other) const |
| Compare object identities. | |
| std::string | Reason (int err) const |
Accessor for large object's contents.
| typedef long pqxx::largeobjectaccess::off_type |
| typedef std::ios::openmode pqxx::largeobjectaccess::openmode |
Open mode: in
, out
(can be combined with the "or" operator)
According to the C++ standard, these should be in std::ios_base
. We take them from std::ios
instead, which should be safe because it inherits the same definition, to accommodate gcc 2.95 & 2.96.
| typedef std::ios::seekdir pqxx::largeobjectaccess::seekdir |
Seek direction: beg
, cur
, end
.
According to the C++ standard, these should be in std::ios_base
. We take them from std::ios
instead, which should be safe because it inherits the same definition, to accommodate gcc 2.95 & 2.96.
| typedef long pqxx::largeobject::size_type |
|
explicit |
Create new large object and open it.
| T | Backend transaction in which the object is to be created |
| mode | Access mode, defaults to ios_base::in | ios_base::out |
References largeobjectaccess().
Referenced by largeobjectaccess().
| pqxx::largeobjectaccess::largeobjectaccess | ( | dbtransaction & | T, |
| oid | O, | ||
| openmode | mode = std::ios::in | std::ios::out |
||
| ) |
Open large object with given oid.
Convert combination of a transaction and object identifier into a large object identity. Does not affect the database.
| T | Transaction in which the object is to be accessed |
| O | Object identifier for the given object |
| mode | Access mode, defaults to ios_base::in | ios_base::out |
References largeobjectaccess().
| pqxx::largeobjectaccess::largeobjectaccess | ( | dbtransaction & | T, |
| largeobject | O, | ||
| openmode | mode = std::ios::in | std::ios::out |
||
| ) |
Open given large object.
Open a large object with the given identity for reading and/or writing
| T | Transaction in which the object is to be accessed |
| O | Identity for the large object to be accessed |
| mode | Access mode, defaults to ios_base::in | ios_base::out |
References largeobjectaccess().
| pqxx::largeobjectaccess::largeobjectaccess | ( | dbtransaction & | T, |
| const std::string & | File, | ||
| openmode | mode = std::ios::in | std::ios::out |
||
| ) |
Import large object from a local file and open it.
Creates a large object containing the data found in the given file.
| T | Backend transaction in which the large object is to be created |
| File | A filename on the client program's filesystem |
| mode | Access mode, defaults to ios_base::in | ios_base::out |
References largeobjectaccess().
| pqxx::largeobjectaccess::~largeobjectaccess | ( | ) | throw () |
| pqxx::largeobjectaccess::pos_type pqxx::largeobjectaccess::cread | ( | char | Buf[], |
| size_type | Len | ||
| ) | throw () |
Read from large object's data stream.
Does not throw exception in case of error; inspect return value and errno
instead.
| Buf | Area where incoming bytes should be stored |
| Len | Number of bytes to read |
| pqxx::largeobjectaccess::pos_type pqxx::largeobjectaccess::cseek | ( | off_type | dest, |
| seekdir | dir | ||
| ) | throw () |
Seek in large object's data stream.
Does not throw exception in case of error; inspect return value and errno
instead.
| dest | Offset to go to |
| dir | Origin to which dest is relative: ios_base::beg (from beginning of the object), ios_base::cur (from current access position), or ios_base;:end (from end of object) |
| pqxx::largeobjectaccess::pos_type pqxx::largeobjectaccess::ctell | ( | ) | const throw () |
Report current position in large object's data stream.
Does not throw exception in case of error; inspect return value and errno
instead.
| pqxx::largeobjectaccess::pos_type pqxx::largeobjectaccess::cwrite | ( | const char | Buf[], |
| size_type | Len | ||
| ) | throw () |
Write to large object's data stream.
Does not throw exception in case of error; inspect return value and errno
instead.
| Buf | Data to write |
| Len | Number of bytes to write |
| void pqxx::largeobjectaccess::process_notice | ( | const std::string & | s | ) | throw () |
Issue message to transaction's notice processor.
| pqxx::largeobjectaccess::size_type pqxx::largeobjectaccess::read | ( | char | Buf[], |
| size_type | Len | ||
| ) |
Read data from large object.
Throws an exception if an error occurs while reading.
| Buf | Location to store the read data in |
| Len | Number of bytes to try and read |
References pqxx::to_string().
| pqxx::largeobjectaccess::size_type pqxx::largeobjectaccess::seek | ( | size_type | dest, |
| seekdir | dir | ||
| ) |
Seek in large object's data stream.
Throws an exception if an error occurs.
| pqxx::largeobjectaccess::size_type pqxx::largeobjectaccess::tell | ( | ) | const |
Report current position in large object's data stream.
Throws an exception if an error occurs.
| void pqxx::largeobjectaccess::to_file | ( | const std::string & | File | ) | const |
Export large object's contents to a local file.
Writes the data stored in the large object to the given file.
| File | A filename on the client's filesystem |
References pqxx::largeobject::to_file().
| void pqxx::largeobjectaccess::write | ( | const char | Buf[], |
| size_type | Len | ||
| ) |
Write data to large object.
If not all bytes could be written, an exception is thrown.
| Buf | Data to write |
| Len | Number of bytes from Buf to write |
References pqxx::to_string().
| void pqxx::largeobjectaccess::write | ( | const std::string & | Buf | ) |


Constructing a stdlib in C
Who is this for?
Coming into this, you should know basic programming, but being a wizard of object-oriented design or dreaming in pure Haskell is of no need. This is C: "C doesn't do that". What you should you have is a [un]healthy desire to peer behind the curtain and see what the rest of your system (assuming you are running Linux or another Unix-like).
On the other side, if you're already proficient in C and/or have a good grasp on the magic that goes on to make your programs work, this is not for you. Feel free to read on and find any mistakes I have made. Suggestions are definitely welcome (open an issue on my github "web" repo).
Motivation
So why would you want to build such a thing? It's certainly not a practical endeavor. I'd never trust Project Paxico with anything important. The point is, as mentioned above, to learn.
And what can you learn from this? First off, if you're unfamiliar with C, this document has a crash course in the basics and little notes and gotchas sprinkled throughout. That was what I intended to learn when I started writing my stdlib. There's also a lot of "peering behind the curtain" to see how common mechanisms, such as memory allocation and program start up, work.
As a last note before this tutorial begins in earnest, this is not a great document from a theoretical perspective. C is not the end-all of languages, and a Unix-like stdlib is most definitely not the best solution out there. However, these are common things in practice and this document is meant to be pragmatic, not perfect.


Day 1: Fez
Arrival at the Saiss Airport. Transfer to the hotel or riad.
Day 2: Fez
Day off to explore the city: medina, tanneries, souks, medersa, …. Overnight stay in a hotel or riad.
Day 3: Fez – Chefchaouen (200km)
Departure after breakfast to the Blue City, Chefchaouen, hidden in the north of Morocco. The highlight of this city is the old medina straight from a fairytal, where almost everything is painted blue. Overnight stay in a riad in the medina.
Day 4: Chefchaouen – Meknes (200km)
After breakfast we will take the road to Meknes. On the way there we'll visit the beautiful archeological site of Volubilis and the city of Moulay Idriss, where we'll climb up the alleys to admire the view of the wide landscape and to see what the mosque looks like from above. Transfer to Meknes, free visit of the city. Overnight stay in a hotel/riad.
Day 5: Meknes – Oulmès – Tarmilate (170km)
We will take the road to Khemisset where we'll turn towards Oulmès (mineral source). Possibility to drive to the Ras el Ma source. Overnight stay in the hotel in Tarmilate.
Day 6: Tarmilate – Bin el Ouidane (250km)
Passing via Khenifra, Kasba-Tadla on our way to the large and beautiful lake of the Barrage Bin el Ouidane. Possibility to take a lakeside walk. Overnight in an auberge on the lakeside.
Day 7: Bin el Ouidane – Marrakech (230km)
On the way to Marrakech we will visit the Ouzoud waterfalls. Overnight stay in a riad in the medina.
Day 8: Marrakech
Our last day is a day off to visit the Red City of Marrakech: Medersa Ben Youssef, the Tombs of the Saadians, the Bahia Palace, the el Badi Palace, the Museum of Marrakech, the Majorelle Gardens,… Overnight stay in a riad in the medina.
Day 9: Marrakech
Got to catch that airplane!


My name is Cordelia Peters and I recently graduated from the Hotchkiss School in Lakeville, CT. I am 18 and am taking a gap year before I head to the University of Virginia next fall. I'm using my gap year to explore my interests in finance and technology. Hopefully my experiences this year will give me context for my studies in college and will help me decide which direction I want to go in. This is my first exposure to computer programming and my first website! I am very excited about DevBootcamp and can't wait to get started.


Keywords
Theme:
Earth Science, Land Surface, Topography, Terrain Elevation, Digital Elevation Model, 3-arc-second DEM, Hydrosphere, Surface Water, Drainage, Hydropattern, Rivers, Streams, Watershed Characteristics, Cartography, Mapping, GIS, EDC, EROS, USGS
Description
Abstract
HydroSHEDS (Hydrological data and maps based on SHuttle Elevation Derivatives at multiple Scales) provides hydrographic information in a consistent and comprehensive format for regional and global-scale applications. HydroSHEDS offers a suite of geo-referenced data sets (vector and raster), including stream networks, watershed boundaries, drainage directions, and ancillary data layers such as flow accumulations, distances, and river topology information. HydroSHEDS is derived from elevation data of the Shuttle Radar Topography Mission (SRTM) at 3 arc-second resolution. Available HydroSHEDS resolutions range from 3 arc-second (approx. 90 meters at the equator) to 5 minute (approx. 10 km at the equator) with seamless near-global extent.
Purpose
The goal of developing HydroSHEDS was to generate key data layers to support regional and global watershed analyses, hydrological modeling, and freshwater conservation planning at a quality, resolution and extent that had previously been unachievable.
Supplementary Information
For more information please refer to the HydroSHEDS Technical Documentation:
Lehner, B., Verdin, K., Jarvis, A. (2006): HydroSHEDS Technical Documentation. World Wildlife Fund US, Washington, DC. Available at http://hydrosheds.cr.usgs.gov.
Please also visit http://www.worldwildlife.org/hydrosheds and http://hydrosheds.cr.usgs.gov for information on data download and status reports.
_________________
Status of the data
Complete
Data update frequency:
As needed
Time period for which the data is relevant
Date and time:
2006
Description:
publication date
Publication Information
Who created the data: World Wildlife Fund (WWF)
Date and time:
2006
Publisher and place:
U.S. Geological Survey, Sioux Falls, SD
_________________
Data storage and access information
File name: n30w100_con
Location of the data:
http://hydrosheds.cr.usgs.gov
http://www.worldwildlife.org/hydrosheds
Data processing environment: Microsoft Windows XP Professional Version 2002 Service Pack 2; ESRI ArcView 3.2a; ESRI ArcGIS 8.2
Accessing the data
Size of the data: 35 MB
Data transfer size: zipped MB
Constraints on accessing and using the data
Access constraints:
None.
Use constraints:
Users may apply HydroSHEDS for non-commercial purposes. We kindly ask users to cite HydroSHEDS in any published material produced using this data. Any modification of the original data by users must be noted. The authors of HydroSHEDS may request reprints of publications and copies of derived materials. The user shall not reproduce, convert, (re)publish, (re)distribute, (re)broadcast, (re)transmit, sell, rent, lease, sublicense, lend, assign, time-share, or transfer, in whole or in part, or provide unlicensed third parties access to the data and related materials without explicit written permission from the authors. For more details see HydroSHEDS Technical Documentation.
Details about this document
Contents last updated: 20090101
Who completed this document
Bernhard Lehner
World Wildlife Fund US
mailing and physical address:
<EMAIL_ADDRESS>Standards used to create this document
Standard name: FGDC Content Standards for Digital Geospatial Metadata
Standard version: FGDC-STD-001-1998
Time convention used in this document: local time
Horizontal coordinate system
Geographic coordinate system name: Geographic
Details
Geographic Coordinate System
Geographic Coordinate Units: Decimal degrees
Geodetic Model
Horizontal Datum Name: D_WGS_1984
Ellipsoid Name: WGS_1984
Semi-major Axis: 6378137.000000
Denominator of Flattening Ratio: 298.257224
Altitude System Definition
Datum Name: EGM96
Distance Units: Meters
_________________
Bounding coordinates
Horizontal
In decimal degrees
West:
-100
East:
-95
North:
35
South:
30
_________________
Spatial data description
Raster dataset information
Raster format: ESRI GRID
SDTS raster type: Grid Cell
Number of raster bands: 1
Raster properties
Origin location: Upper Left
Has colormap: FALSE
Data compression type: Default
Display type: Matrix Values
Cell information
Number of cells on x-axis: 6000
Number of cells on y-axis: 6000
Number of cells on z-axis: 1
Number of bits per cell: 16
Cell Size
X distance: 0.0008333333333333
Y distance: 0.0008333333333333


Bruce Wayne
Home
Profile
Logout
BASIC Authentication Policy Configuration
Authentication Realm
Forward Authenticated Username as HTTP Header
Identity Source
Choose an Identity Source...
Static
JDBC
LDAP
Static Identities
bwayne:bwayne
ckent:ckent123!
dprince:f00b4r#
Clear
Remove
:
Add
JDBC Datasource (JNDI Location)
SQL Query
Password Hash Algorithm
None
SHA1
MD5
LDAP Server URL
LDAP Bind DN


First, you'll need to get a Google Client ID. Follow these steps:
-
Visit https://cloud.google.com/console
-
If necessary, "Create Project"
-
Click "APIs & auth" and "Credentials" on the left, then "Create new client ID"
-
Choose "Web application" as the Application type
-
Set Authorized Javascript origins to
{{absoluteUrl}}
.
-
Set Authorized redirect URI to
{{absoluteUrl}}_oauth/google?close
Now, copy over the details.


The main objective of Hotline is the fight against illegal content on the Internet in relation of child pornography and racism. It gives the opportunity to the public to denounce websites containing illegal content. It also helps the department Anti Cyber Crime in an effort to provide a safer internet for young and old people. Finally provides cooperation with international bodies and other complaints lines for coordination of all countries in the fight against this phenomenon.
The phenomenon of violence in the internet may appear with the following ways:
• Cyberbullying
• Grooming
• CSAM
Child sexual abuse content
• SAM
Content Sexual exploitation
• Racism/Xenophobia
• Sexting
Helpline aims to provide citizens of Cyprus means to speak anonymously to trained professionals who can support them psychologically, to any concern or threat may face over the internet.
It offers the opportunity to the public to answer questions and express their concerns or queries on harmful online behavior, harmful communication and harmful content on the Internet. The line provides psychological and technical support.
Also Helpline collaborate with the Helpline referring cases involving illegal content online..
The Helpline deals with issues such as:
• Cyberbullying
• Change settings
• Commercial risks/threats
• Excessive use
• Grooming
• Hacking
• Identity Thefts
• Other potentially harmful content
• Online reputation
• Phishing
• Privacy
• Sexting
• Sexual harassment
• Spam
• Technical settings
• Unsolicited contact from strangers
Hotline Reports 2016: ***
Helpline Reports 2016: ***
YYYY (Hotline / HelpLine)


Hi I'm Steve!
I'm a software developer with a flair for design looking to infuse both technical and design skills into various projects
that are both useful and fun for the end user.
PS: this website is still under construction so just check out my GITHUB for other stuff! :)
check out my GITHUB


Preface¶
We are presenting an easy interface to robotics while leveraging a number of community tools. All programming we document here is mostly done in python. This also allows us to utilize cloudmesh cmd5 which provides an easy to use command shell. Future versions will be able to be installed via pypi, howevewr, currently we recommend instalation from source.
We integrated some examples to allow students to explore how to use two borads. One is based on the esp8266, the other is based on Raspberry PI 3.
We are actively looking for your contributions so we can integrate them.
Contributors¶
- Gregor von Laszewski<EMAIL_ADDRESS>- Fugang Wang<EMAIL_ADDRESS>- Syed
- Jonathan
Contact¶
- Gregor von Laszewski
-<EMAIL_ADDRESS>Conventions¶
$ > When showing examples of commands, the $ symbol precedes the actual command. So, the other lines are the output obtained after executing the command. An example invoking the ls command follows:
$ ls
Commands on the NodeMCU are typically indicated with >>>
the python
interpreter prompt. Example:
>>> import os
>>> os.listdir()
PORTALNAME > In some examples we refer to your portal name as the PORTALNAME you have on FutureSystems.
USERNAME
In some examples we refer to your local computers name as USERNAME. Your portal name and your local name may be different.
Menu selections
Start ‣ Programs
Man page:
ls(1)


PUL GitHub Issues
2021-12-03
#212 Remove entry for departing staff member
Creator:
Kevin Reiss
Created:
2021-12-03 00:21:32
Status:
Closed
(pull request )
Events:
review_requested
by Kevin Reiss at 2021-12-03 00:21:32.
deployed
by None at 2021-12-03 13:26:17.
head_ref_force_pushed
by Kevin Reiss at 2021-12-03 16:46:38.
referenced
by None at 2021-12-03 20:20:48.
merged
by None at 2021-12-03 20:20:48.
closed
by None at 2021-12-03 20:20:48.
head_ref_deleted
by None at 2021-12-03 20:20:49.
#100 output files for import after applying XQuery routines from migration
Creator:
regineheberlein
Created:
2021-12-02 22:16:26
Status:
Closed
(pull request )
Events:
review_requested
by None at 2021-12-02 22:16:26.
referenced
by Peter Green at 2021-12-02 22:21:21.
merged
by Peter Green at 2021-12-02 22:21:21.
closed
by Peter Green at 2021-12-02 22:21:21.
#102 we need to match components to a vendor spreadsheet
Creator:
regineheberlein
Created:
2021-12-03 19:26:11
Status:
Open
Comments:
Events:
assigned
by None at 2021-12-03 19:26:11.
labeled
by None at 2021-12-03 22:28:37.
referenced
by None at 2021-12-03 22:33:48.
#101 Report ac187
Creator:
regineheberlein
Created:
2021-12-03 14:42:48
Status:
Open
(pull request )
Events:
review_requested
by None at 2021-12-03 22:34:48.
ready_for_review
by None at 2021-12-03 22:34:49.
#103 Report mc147
Creator:
regineheberlein
Created:
2021-12-03 22:36:02
Status:
Open
(pull request )
Events:
review_requested
by None at 2021-12-03 22:36:02.
#85 need a report on AC187
Creator:
regineheberlein
Created:
2021-11-19 21:02:59
Status:
Closed
Events:
referenced
by None at 2021-12-03 22:30:18.
closed
by None at 2021-12-03 22:36:49.
#1741 Add Two New Holding Locations
Creator:
Kevin Reiss
Created:
2021-12-03 22:51:02
Status:
Open
Events:
labeled
by Kevin Reiss at 2021-12-03 22:51:02.
assigned
by Christina Chortaria at 2021-12-03 22:51:03.
unassigned
by Christina Chortaria at 2021-12-03 23:03:00.
#14 Add triaging issues documentation
Creator:
Trey Pendragon
Created:
2021-09-08 20:56:54
Status:
Open
#3 Document usability testing
Creator:
Trey Pendragon
Created:
2021-09-08 20:35:18
Status:
Open
Comments:
Events:
labeled
by None at 2021-12-03 20:25:38.
#27 Explain gandalf
Creator:
hackartisan
Created:
2021-03-05 19:14:40
Status:
Open
#2 Document a "vision" for each application.
Creator:
Trey Pendragon
Created:
2021-09-08 20:34:53
Status:
Open
#1271 Marquand feature page erroring
Creator:
hackartisan
Created:
2021-12-01 15:12:45
Status:
Closed
Comments:
Events:
closed
by None at 2021-12-03 20:20:14.
#724 Is there another way to monitor sneakers?
Creator:
hackartisan
Created:
2020-01-30 15:13:24
Status:
Open
Comments:
Events:
unlabeled
by None at 2021-12-03 20:30:30.
mentioned
by Alicia Cozine at 2021-12-03 20:30:58.
subscribed
by Alicia Cozine at 2021-12-03 20:30:58.
assigned
by Alicia Cozine at 2021-12-03 20:31:03.
#919 Use symbols in polymorphic urls
Creator:
hackartisan
Created:
2021-05-25 16:10:00
Status:
Open
Events:
unlabeled
by None at 2021-12-03 20:36:13.
#964 Determine why we have a test for Resources with no Exhibits, delete if appropriate
Creator:
Trey Pendragon
Created:
2021-09-22 16:28:17
Status:
Open
Comments:
#1188 Deleting an exhibit should delete associated Resources
Creator:
Trey Pendragon
Created:
2021-11-01 20:53:47
Status:
Open
#1272 Spotlight Upgrade Placeholder
Creator:
Thanya Begum
Created:
2021-12-03 21:19:07
Status:
Open
Events:
labeled
by Thanya Begum at 2021-12-03 21:19:07.
#759 Rake task to clean up guest accounts
Creator:
hackartisan
Created:
2020-03-09 13:04:02
Status:
Open
#1264 Duplicate ids for elements referenced with ARIA
Creator:
Zaynab Masood
Created:
2021-11-22 19:32:36
Status:
Open
Comments:
Events:
labeled
by Thanya Begum at 2021-12-03 21:39:31.
#1227 Duplicate ids in pages
Creator:
Zaynab Masood
Created:
2021-11-08 20:41:15
Status:
Open
Comments:
Events:
labeled
by Thanya Begum at 2021-12-03 21:48:10.
#1263 Remove duplicate id in bookmarks page
Creator:
Thanya Begum
Created:
2021-11-19 21:57:27
Status:
Open
(pull request )
Events:
head_ref_force_pushed
by Thanya Begum at 2021-12-03 16:06:38.
renamed
by Thanya Begum at 2021-12-03 21:45:37.
ready_for_review
by Thanya Begum at 2021-12-03 21:50:21.
review_requested
by Thanya Begum at 2021-12-03 21:50:31.
#556 Troubleshoot and reattempt to apply the 5.21 patch upgrade for Elements on cidsr201w
Creator:
James R. Griffin III
Created:
2021-12-01 15:16:37
Status:
Open
Comments:
#4799 Cookie overflow error during index "read-only" context.
Creator:
Shaun Ellis
Created:
2021-11-18 16:20:07
Status:
Open
Events:
assigned
by Shaun Ellis at 2021-12-03 20:22:55.
#4819 Add data tables to child member tables
Creator:
hackartisan
Created:
2021-12-03 21:23:20
Status:
Open
(pull request )
#36 filter by staff for imported records fails
Creator:
carolyncole
Created:
2021-12-02 15:03:56
Status:
Closed
Comments:
Events:
closed
by None at 2021-12-03 14:00:01.
#9 Generate Locker occupancy by department report
Creator:
carolyncole
Created:
2021-10-25 13:57:58
Status:
Open
Events:
assigned
by None at 2021-12-03 14:02:45.
#14 Notify the user when Locker Material are not checked out
Creator:
carolyncole
Created:
2021-10-25 14:27:05
Status:
Closed
Comments:
Events:
closed
by None at 2021-12-03 14:05:19.
#6 Assign a study space
Creator:
carolyncole
Created:
2021-10-25 13:48:18
Status:
Open
#15 Create a Locker agreement form
Creator:
carolyncole
Created:
2021-10-25 14:48:11
Status:
Closed
Comments:
Events:
closed
by None at 2021-12-03 14:07:06.
#13 Make a locker as removed
Creator:
carolyncole
Created:
2021-10-25 14:24:07
Status:
Open
Events:
renamed
by None at 2021-12-03 14:07:20.
#26 Search and filter Assignments
Creator:
carolyncole
Created:
2021-11-19 12:55:27
Status:
Closed
Events:
closed
by None at 2021-12-03 14:07:48.
#38 Adding mass assignment of study spaces
Creator:
carolyncole
Created:
2021-12-02 21:03:23
Status:
Open
(pull request )
Events:
head_ref_force_pushed
by None at 2021-12-03 13:45:54.
deployed
by None at 2021-12-03 13:46:17.
head_ref_force_pushed
by None at 2021-12-03 20:38:29.
ready_for_review
by None at 2021-12-03 20:38:49.
#40 Filter Available Lockers in Assigned Space by Size
Creator:
carolyncole
Created:
2021-12-03 20:40:11
Status:
Open
#41 Send the user an email on study room assignment
Creator:
carolyncole
Created:
2021-12-03 20:41:33
Status:
Open
#42 When max occupancy is zero the locker should be disabled
Creator:
carolyncole
Created:
2021-12-03 21:09:00
Status:
Open
#43 Adding disabled to lockers table and seeding
Creator:
carolyncole
Created:
2021-12-03 21:18:16
Status:
Open
(pull request )
Events:
head_ref_force_pushed
by None at 2021-12-03 21:25:39.
#44 Adding Reporting to the system
Creator:
carolyncole
Created:
2021-12-03 21:29:44
Status:
Open
(pull request )
#37 Staus at Application in form
Creator:
carolyncole
Created:
2021-12-02 15:06:54
Status:
Closed
Events:
assigned
by None at 2021-12-03 14:00:36.
referenced
by None at 2021-12-03 14:03:39.
referenced
by None at 2021-12-03 20:32:21.
closed
by Christina Chortaria at 2021-12-03 23:47:01.
#39 Fixes Staus typo
Creator:
carolyncole
Created:
2021-12-03 14:04:06
Status:
Closed
(pull request )
Comments:
Events:
mentioned
by Christina Chortaria at 2021-12-03 14:04:07.
subscribed
by Christina Chortaria at 2021-12-03 14:04:07.
head_ref_force_pushed
by None at 2021-12-03 20:32:21.
mentioned
by Christina Chortaria at 2021-12-03 20:33:15.
subscribed
by Christina Chortaria at 2021-12-03 20:33:15.
referenced
by Christina Chortaria at 2021-12-03 23:47:01.
merged
by Christina Chortaria at 2021-12-03 23:47:01.
closed
by Christina Chortaria at 2021-12-03 23:47:01.
head_ref_deleted
by Christina Chortaria at 2021-12-03 23:47:02.
#380 Menu-bar in not accessible when type=main-menu
Creator:
Shaun Ellis
Created:
2021-12-03 20:35:25
Status:
Open
Events:
assigned
by Shaun Ellis at 2021-12-03 20:35:34.
#381 Fixes menu bar accessibility
Creator:
Shaun Ellis
Created:
2021-12-03 20:37:23
Status:
Open
(pull request )
#38 OJS- File upload error in Article Submission
Creator:
yuanli80
Created:
2021-12-03 16:44:05
Status:
Open
#2815 2 new locations
Creator:
mzelesky
Created:
2021-12-03 19:04:38
Status:
Closed
Comments:
Events:
closed
by Kevin Reiss at 2021-12-03 22:51:16.
#82 Create an "About" page
Creator:
Bess Sadler
Created:
2021-11-03 20:39:12
Status:
Open
Events:
assigned
by Hector Correa at 2021-12-03 14:22:33.
#109 Added About page with lorem ipsum text
Creator:
Hector Correa
Created:
2021-12-03 16:11:05
Status:
Open
(pull request )
Comments:
Events:
review_requested
by Kate Lynch at 2021-12-03 16:18:39.
review_requested
by Hector Correa at 2021-12-03 16:31:11.
mentioned
by Bess Sadler at 2021-12-03 16:31:33.
subscribed
by Bess Sadler at 2021-12-03 16:31:33.
#97 Bug: When we deploy, the footer sometimes has stale data
Creator:
Bess Sadler
Created:
2021-11-29 16:03:00
Status:
Open
Events:
assigned
by Hector Correa at 2021-12-03 20:14:37.
#49 -staging and -prod should index different dataspace instances
Creator:
Bess Sadler
Created:
2021-08-11 20:05:49
Status:
Open
Events:
assigned
by Hector Correa at 2021-12-03 20:14:56.
#111 Configurable Dataspace URL
Creator:
Hector Correa
Created:
2021-12-03 21:25:35
Status:
Open
(pull request )
#110 Issue 67 version
Creator:
Hector Correa
Created:
2021-12-03 20:11:37
Status:
Open
(pull request )
#2585 Install shibboleth via ansible
Creator:
Bess Sadler
Created:
2021-11-30 15:03:13
Status:
Open
#2591 Load balancer must point to 443 to pick up shib config
Creator:
Bess Sadler
Created:
2021-12-03 14:24:16
Status:
Closed
(pull request )
Events:
referenced
by Hector Correa at 2021-12-03 14:52:38.
merged
by Hector Correa at 2021-12-03 14:52:38.
closed
by Hector Correa at 2021-12-03 14:52:38.
head_ref_deleted
by Hector Correa at 2021-12-03 14:52:39.
#2587 remove port 8080
Creator:
Francis Kayiwa
Created:
2021-11-30 20:04:46
Status:
Closed
(pull request )
#2581 remove vireo prod keys
Creator:
Francis Kayiwa
Created:
2021-11-24 16:01:30
Status:
Closed
(pull request )
#2583 trying again for vireo prod certs
Creator:
Alicia Cozine
Created:
2021-11-29 15:39:21
Status:
Closed
(pull request )
#2586 add a vireo prod config
Creator:
Francis Kayiwa
Created:
2021-11-30 16:56:24
Status:
Closed
(pull request )
#2588 rename files
Creator:
Francis Kayiwa
Created:
2021-12-01 14:34:26
Status:
Closed
(pull request )
#2592 When we use port 443 we also need https
Creator:
Bess Sadler
Created:
2021-12-03 16:23:09
Status:
Closed
(pull request )
Events:
referenced
by Bess Sadler at 2021-12-03 16:54:58.
merged
by Bess Sadler at 2021-12-03 16:54:58.
closed
by Bess Sadler at 2021-12-03 16:54:58.
head_ref_deleted
by Bess Sadler at 2021-12-03 16:54:59.
#2590 migrate additional shakespeare and company project aliases to library
Creator:
Rebecca Sutton Koeser
Created:
2021-12-02 20:34:51
Status:
Open
Comments:
#2589 Repmgr failover
Creator:
Francis Kayiwa
Created:
2021-12-01 21:08:04
Status:
Open
(pull request )
Events:
head_ref_force_pushed
by Francis Kayiwa at 2021-12-03 21:22:44.
#2594 add new aliases for shakespeare
Creator:
Francis Kayiwa
Created:
2021-12-03 21:36:40
Status:
Open
(pull request )
#2593 Shibboleth and Vireo installation
Creator:
Bess Sadler
Created:
2021-12-03 20:40:24
Status:
Open
(pull request )
#1807 Create Form for Makerspace
Creator:
Kevin Reiss
Created:
2021-12-03 01:10:56
Status:
Open
#985 Index metadata from Big10 into Pulmap
Creator:
Eliot Jordan
Created:
2021-10-30 01:36:08
Status:
Open
Comments:
Events:
renamed
by None at 2021-12-03 20:16:30.
#949 [Pulmap/production] ActiveSupport::MessageVerifier::InvalidSignature: ActiveSupport::MessageVerifier::InvalidSignature
Creator:
Eliot Jordan
Created:
2021-06-08 14:37:28
Status:
Open
Events:
unassigned
by Eliot Jordan at 2021-12-03 20:38:27.
#975 [Pulmap/production] RGeo::Error::InvalidGeometry: LinearRing failed ring test
Creator:
Eliot Jordan
Created:
2021-08-11 15:47:41
Status:
Open
#20 Restore and save cache keys are different
Creator:
Eliot Jordan
Created:
2021-11-30 17:25:07
Status:
Open
Events:
labeled
by None at 2021-12-03 20:27:04.
#18 Add example yarn test configuration
Creator:
hackartisan
Created:
2021-11-30 16:38:15
Status:
Open
Events:
labeled
by None at 2021-12-03 20:27:04.
#17 cap [stage] rails:console
Creator:
hackartisan
Created:
2021-09-14 16:51:33
Status:
Open
Events:
labeled
by None at 2021-12-03 20:27:04.
#22 2021 Autumn Samvera Developer Congress
Creator:
James R. Griffin III
Created:
2021-11-29 15:05:51
Status:
Open
#17 Add staging and production environments
Creator:
Eliot Jordan
Created:
2021-12-02 19:02:49
Status:
Closed
(pull request )
Events:
referenced
by Eliot Jordan at 2021-12-02 22:39:51.
merged
by Eliot Jordan at 2021-12-02 22:39:51.
closed
by Eliot Jordan at 2021-12-02 22:39:51.
head_ref_deleted
by Eliot Jordan at 2021-12-02 22:39:51.
#14 Add staging and production deployments
Creator:
Eliot Jordan
Created:
2021-11-30 20:47:06
Status:
Closed
Events:
closed
by Eliot Jordan at 2021-12-02 22:39:51.
#15 Add map-tiles and map-tiles-staging domains
Creator:
Eliot Jordan
Created:
2021-11-30 20:40:45
Status:
Closed
Events:
closed
by None at 2021-12-03 18:31:52.
#18 Add custom domains to TiTiler cloudfront distribution
Creator:
Eliot Jordan
Created:
2021-12-03 17:51:28
Status:
Closed
(pull request )
Events:
referenced
by None at 2021-12-03 18:31:52.
merged
by None at 2021-12-03 18:31:52.
closed
by None at 2021-12-03 18:31:52.
head_ref_deleted
by None at 2021-12-03 18:31:53.


|
DJI Onboard SDK
4.0
|
Files | |
| file | dji_advanced_sensing.hpp [code] |
| file | dji_advanced_sensing_protocol.hpp [code] |
| file | dji_aes.hpp [code] |
| file | dji_camera_stream.hpp [code] |
| The high level APIs to interact with the camera. | |
| file | dji_hard_driver.hpp [code] |
| Serial device driver abstraction. Provided as an abstract class. Please inherit and implement for individual platforms. | |
| file | dji_liveview.hpp [code] |
| Camera liveview API of OSDK. | |
| file | dji_memory.hpp [code] |
| Implement memory management for DJI OSDK . | |
| file | dji_perception.hpp [code] |
| Camera dji perception API of OSDK. | |
| file | dji_protocol_base.hpp [code] |
| Abstract protocol implementation for DJI OSDK. | |
| file | dji_thread_manager.hpp [code] |
| Data protection and thread management abstract classes. | |
| file | linux_usb_device.hpp [code] |
| file | posix_thread_manager.hpp [code] |
| Thread safety and data protection for DJI Onboard SDK on linux platforms. | |


WITNESS LIST State Recreational Resources Committee March 24, 1999-8:00A HB 1828 On: Kennedy, Boyd (Texas Parks & Wildlife Department) Sinclair, David (Texas Parks & Wildlife Department) Registering, but not testifying: For: Powers, Bill (Texas Farm Bureau) HB 1892 For: Glacken, Shawn (Assoc. of Electric Companies of Texas) On: Shinkawa, Paul M. (Texas Parks & Wildlife Department) HB 2526 For: Benavides, Manuel A. (Self) Hale, Jr., Oscar J. (Self and Webb Co. District Attorney's Office) Powers, Bill (Texas Farm Bureau) HB 2731 Registering, but not testifying: For: Powers, Bill (Texas Farm Bureau) On: Cooke, Jerry L. (Texas Parks and Wildlife Department)


Kristina Alfonsine
View your profile
News Feed
Chat with Ellen
Read Articles
Browse Questions
Know your Rights
Report Violence
About this App
Logout


It's a very simple prototype of alternative aproach to datepicker. The goal is to provide easiest way to pick date from very wide range of dates.
Warning - wasn't tested under IE at all. Please use Chrome, Firefox, or Safari


Close
Title of image
Open source image
Search photos
Source
500px
Flickr
Instagram
Feature
Popular
Highest rated
Upcoming
Fresh today
Fresh yesterday
Fresh week
Area
Romania
Europe
Asia
Africa
South America
North America
Australia
Antarctica
Category
Uncategorized
Abstract
Aerial
Animals
Celebrities
City and Architecture
Comercial
Family
Fashion
Film
Fine Art
Food
Landscapes
Nature
Night
Nude
People
Sport
Travel
Wedding
Dimensions
70px x 70px
140px x 140px
280px x 280px
100px x 100px
200px x 200px
440px x 440px
600px x 600px
Camera
Canon
NIKON
DSLR
Focal length
Less than 10
Less than 50
Less than 100
Less than 150
Less than 200
Less than 250
Less than 300
Area
Romania
Europe
Asia
Africa
South America
North America
Australia
Antarctica
Location context
Inside
Outside
Undefined
Taken date
Today
Last week
Last month
Last year
Uploaded date
Today
Last week
Last month
Last year
Dimensions
75px x 75px
150px x 150px
240px longest size
320px longest size
640px longest size
1024px longest size
2048px longest size
Selected Filters:


Sergey Makeev
Gaussian Kernel generator
Expression calculator
Z8 : Fantasy 8-bit system
Z8 : Tech Demo
Simple PBR three.js test
ZX Spectrum Tribute


1: /* 2: * Copyright 2001-2005 Stephen Colebourne 3: * 4: * Licensed under the Apache License, Version 2.0 (the "License"); 5: * you may not use this file except in compliance with the License. 6: * You may obtain a copy of the License at 7: * 8: * http://www.apache.org/licenses/LICENSE-2.0 9: * 10: * Unless required by applicable law or agreed to in writing, software 11: * distributed under the License is distributed on an "AS IS" BASIS, 12: * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. 13: * See the License for the specific language governing permissions and 14: * limitations under the License. 15: */ 16: package org.joda.time.chrono; 17: 18: import java.io.IOException; 19: import java.io.ObjectInputStream; 20: 21: import org.joda.time.Chronology; 22: import org.joda.time.DateTimeField; 23: import org.joda.time.DateTimeZone; 24: import org.joda.time.DurationField; 25: 26: /** 27: * Abstract Chronology that enables chronologies to be assembled from 28: * a container of fields. 29: * <p> 30: * AssembledChronology is thread-safe and immutable. 31: * 32: * @author Brian S O'Neill 33: * @since 1.0 34: */ 35: public abstract class AssembledChronology extends BaseChronology { 36: 37: private static final long serialVersionUID = -6728465968995518215L; 38: 39: private final Chronology iBase; 40: private final Object iParam; 41: 42: private transient DurationField iMillis; 43: private transient DurationField iSeconds; 44: private transient DurationField iMinutes; 45: private transient DurationField iHours; 46: private transient DurationField iHalfdays; 47: 48: private transient DurationField iDays; 49: private transient DurationField iWeeks; 50: private transient DurationField iWeekyears; 51: private transient DurationField iMonths; 52: private transient DurationField iYears; 53: private transient DurationField iCenturies; 54: private transient DurationField iEras; 55: 56: private transient DateTimeField iMillisOfSecond; 57: private transient DateTimeField iMillisOfDay; 58: private transient DateTimeField iSecondOfMinute; 59: private transient DateTimeField iSecondOfDay; 60: private transient DateTimeField iMinuteOfHour; 61: private transient DateTimeField iMinuteOfDay; 62: private transient DateTimeField iHourOfDay; 63: private transient DateTimeField iClockhourOfDay; 64: private transient DateTimeField iHourOfHalfday; 65: private transient DateTimeField iClockhourOfHalfday; 66: private transient DateTimeField iHalfdayOfDay; 67: 68: private transient DateTimeField iDayOfWeek; 69: private transient DateTimeField iDayOfMonth; 70: private transient DateTimeField iDayOfYear; 71: private transient DateTimeField iWeekOfWeekyear; 72: private transient DateTimeField iWeekyear; 73: private transient DateTimeField iWeekyearOfCentury; 74: private transient DateTimeField iMonthOfYear; 75: private transient DateTimeField iYear; 76: private transient DateTimeField iYearOfEra; 77: private transient DateTimeField iYearOfCentury; 78: private transient DateTimeField iCenturyOfEra; 79: private transient DateTimeField iEra; 80: 81: // Bit set determines which base fields are used 82: // bit 1 set: hourOfDay, minuteOfHour, secondOfMinute, and millisOfSecond fields 83: // bit 2 set: millisOfDayField 84: // bit 3 set: year, monthOfYear, and dayOfMonth fields 85: private transient int iBaseFlags; 86: 87: /** 88: * Constructor calls the assemble method, enabling subclasses to define its 89: * supported fields. If a base chronology is supplied, the field set 90: * initially contains references to each base chronology field. 91: * <p> 92: * Other methods in this class will delegate to the base chronology, if it 93: * can be determined that the base chronology will produce the same results 94: * as AbstractChronology. 95: * 96: * @param base optional base chronology to copy initial fields from 97: * @param param optional param object avalable for assemble method 98: */ 99: protected AssembledChronology(Chronology base, Object param) { 100: iBase = base; 101: iParam = param; 102: setFields(); 103: } 104: 105: public DateTimeZone getZone() { 106: Chronology base; 107: if ((base = iBase) != null) { 108: return base.getZone(); 109: } 110: return null; 111: } 112: 113: public long getDateTimeMillis(int year, int monthOfYear, int dayOfMonth, 114: int millisOfDay) 115: throws IllegalArgumentException 116: { 117: Chronology base; 118: if ((base = iBase) != null && (iBaseFlags & 6) == 6) { 119: // Only call specialized implementation if applicable fields are the same. 120: return base.getDateTimeMillis(year, monthOfYear, dayOfMonth, millisOfDay); 121: } 122: return super.getDateTimeMillis(year, monthOfYear, dayOfMonth, millisOfDay); 123: } 124: 125: public long getDateTimeMillis(int year, int monthOfYear, int dayOfMonth, 126: int hourOfDay, int minuteOfHour, 127: int secondOfMinute, int millisOfSecond) 128: throws IllegalArgumentException 129: { 130: Chronology base; 131: if ((base = iBase) != null && (iBaseFlags & 5) == 5) { 132: // Only call specialized implementation if applicable fields are the same. 133: return base.getDateTimeMillis(year, monthOfYear, dayOfMonth, 134: hourOfDay, minuteOfHour, secondOfMinute, millisOfSecond); 135: } 136: return super.getDateTimeMillis(year, monthOfYear, dayOfMonth, 137: hourOfDay, minuteOfHour, secondOfMinute, millisOfSecond); 138: } 139: 140: public long getDateTimeMillis(long instant, 141: int hourOfDay, int minuteOfHour, 142: int secondOfMinute, int millisOfSecond) 143: throws IllegalArgumentException 144: { 145: Chronology base; 146: if ((base = iBase) != null && (iBaseFlags & 1) == 1) { 147: // Only call specialized implementation if applicable fields are the same. 148: return base.getDateTimeMillis 149: (instant, hourOfDay, minuteOfHour, secondOfMinute, millisOfSecond); 150: } 151: return super.getDateTimeMillis 152: (instant, hourOfDay, minuteOfHour, secondOfMinute, millisOfSecond); 153: } 154: 155: public final DurationField millis() { 156: return iMillis; 157: } 158: 159: public final DateTimeField millisOfSecond() { 160: return iMillisOfSecond; 161: } 162: 163: public final DateTimeField millisOfDay() { 164: return iMillisOfDay; 165: } 166: 167: public final DurationField seconds() { 168: return iSeconds; 169: } 170: 171: public final DateTimeField secondOfMinute() { 172: return iSecondOfMinute; 173: } 174: 175: public final DateTimeField secondOfDay() { 176: return iSecondOfDay; 177: } 178: 179: public final DurationField minutes() { 180: return iMinutes; 181: } 182: 183: public final DateTimeField minuteOfHour() { 184: return iMinuteOfHour; 185: } 186: 187: public final DateTimeField minuteOfDay() { 188: return iMinuteOfDay; 189: } 190: 191: public final DurationField hours() { 192: return iHours; 193: } 194: 195: public final DateTimeField hourOfDay() { 196: return iHourOfDay; 197: } 198: 199: public final DateTimeField clockhourOfDay() { 200: return iClockhourOfDay; 201: } 202: 203: public final DurationField halfdays() { 204: return iHalfdays; 205: } 206: 207: public final DateTimeField hourOfHalfday() { 208: return iHourOfHalfday; 209: } 210: 211: public final DateTimeField clockhourOfHalfday() { 212: return iClockhourOfHalfday; 213: } 214: 215: public final DateTimeField halfdayOfDay() { 216: return iHalfdayOfDay; 217: } 218: 219: public final DurationField days() { 220: return iDays; 221: } 222: 223: public final DateTimeField dayOfWeek() { 224: return iDayOfWeek; 225: } 226: 227: public final DateTimeField dayOfMonth() { 228: return iDayOfMonth; 229: } 230: 231: public final DateTimeField dayOfYear() { 232: return iDayOfYear; 233: } 234: 235: public final DurationField weeks() { 236: return iWeeks; 237: } 238: 239: public final DateTimeField weekOfWeekyear() { 240: return iWeekOfWeekyear; 241: } 242: 243: public final DurationField weekyears() { 244: return iWeekyears; 245: } 246: 247: public final DateTimeField weekyear() { 248: return iWeekyear; 249: } 250: 251: public final DateTimeField weekyearOfCentury() { 252: return iWeekyearOfCentury; 253: } 254: 255: public final DurationField months() { 256: return iMonths; 257: } 258: 259: public final DateTimeField monthOfYear() { 260: return iMonthOfYear; 261: } 262: 263: public final DurationField years() { 264: return iYears; 265: } 266: 267: public final DateTimeField year() { 268: return iYear; 269: } 270: 271: public final DateTimeField yearOfEra() { 272: return iYearOfEra; 273: } 274: 275: public final DateTimeField yearOfCentury() { 276: return iYearOfCentury; 277: } 278: 279: public final DurationField centuries() { 280: return iCenturies; 281: } 282: 283: public final DateTimeField centuryOfEra() { 284: return iCenturyOfEra; 285: } 286: 287: public final DurationField eras() { 288: return iEras; 289: } 290: 291: public final DateTimeField era() { 292: return iEra; 293: } 294: 295: /** 296: * Invoked by the constructor and after deserialization to allow subclasses 297: * to define all of its supported fields. All unset fields default to 298: * unsupported instances. 299: * 300: * @param fields container of fields 301: */ 302: protected abstract void assemble(Fields fields); 303: 304: /** 305: * Returns the same base chronology as passed into the constructor. 306: */ 307: protected final Chronology getBase() { 308: return iBase; 309: } 310: 311: /** 312: * Returns the same param object as passed into the constructor. 313: */ 314: protected final Object getParam() { 315: return iParam; 316: } 317: 318: private void setFields() { 319: Fields fields = new Fields(); 320: if (iBase != null) { 321: fields.copyFieldsFrom(iBase); 322: } 323: assemble(fields); 324: 325: { 326: DurationField f; 327: iMillis = (f = fields.millis) != null ? f : super.millis(); 328: iSeconds = (f = fields.seconds) != null ? f : super.seconds(); 329: iMinutes = (f = fields.minutes) != null ? f : super.minutes(); 330: iHours = (f = fields.hours) != null ? f : super.hours(); 331: iHalfdays = (f = fields.halfdays) != null ? f : super.halfdays(); 332: iDays = (f = fields.days) != null ? f : super.days(); 333: iWeeks = (f = fields.weeks) != null ? f : super.weeks(); 334: iWeekyears = (f = fields.weekyears) != null ? f : super.weekyears(); 335: iMonths = (f = fields.months) != null ? f : super.months(); 336: iYears = (f = fields.years) != null ? f : super.years(); 337: iCenturies = (f = fields.centuries) != null ? f : super.centuries(); 338: iEras = (f = fields.eras) != null ? f : super.eras(); 339: } 340: 341: { 342: DateTimeField f; 343: iMillisOfSecond = (f = fields.millisOfSecond) != null ? f : super.millisOfSecond(); 344: iMillisOfDay = (f = fields.millisOfDay) != null ? f : super.millisOfDay(); 345: iSecondOfMinute = (f = fields.secondOfMinute) != null ? f : super.secondOfMinute(); 346: iSecondOfDay = (f = fields.secondOfDay) != null ? f : super.secondOfDay(); 347: iMinuteOfHour = (f = fields.minuteOfHour) != null ? f : super.minuteOfHour(); 348: iMinuteOfDay = (f = fields.minuteOfDay) != null ? f : super.minuteOfDay(); 349: iHourOfDay = (f = fields.hourOfDay) != null ? f : super.hourOfDay(); 350: iClockhourOfDay = (f = fields.clockhourOfDay) != null ? f : super.clockhourOfDay(); 351: iHourOfHalfday = (f = fields.hourOfHalfday) != null ? f : super.hourOfHalfday(); 352: iClockhourOfHalfday = (f = fields.clockhourOfHalfday) != null ? f : super.clockhourOfHalfday(); 353: iHalfdayOfDay = (f = fields.halfdayOfDay) != null ? f : super.halfdayOfDay(); 354: iDayOfWeek = (f = fields.dayOfWeek) != null ? f : super.dayOfWeek(); 355: iDayOfMonth = (f = fields.dayOfMonth) != null ? f : super.dayOfMonth(); 356: iDayOfYear = (f = fields.dayOfYear) != null ? f : super.dayOfYear(); 357: iWeekOfWeekyear = (f = fields.weekOfWeekyear) != null ? f : super.weekOfWeekyear(); 358: iWeekyear = (f = fields.weekyear) != null ? f : super.weekyear(); 359: iWeekyearOfCentury = (f = fields.weekyearOfCentury) != null ? f : super.weekyearOfCentury(); 360: iMonthOfYear = (f = fields.monthOfYear) != null ? f : super.monthOfYear(); 361: iYear = (f = fields.year) != null ? f : super.year(); 362: iYearOfEra = (f = fields.yearOfEra) != null ? f : super.yearOfEra(); 363: iYearOfCentury = (f = fields.yearOfCentury) != null ? f : super.yearOfCentury(); 364: iCenturyOfEra = (f = fields.centuryOfEra) != null ? f : super.centuryOfEra(); 365: iEra = (f = fields.era) != null ? f : super.era(); 366: } 367: 368: int flags; 369: if (iBase == null) { 370: flags = 0; 371: } else { 372: flags = 373: ((iHourOfDay == iBase.hourOfDay() && 374: iMinuteOfHour == iBase.minuteOfHour() && 375: iSecondOfMinute == iBase.secondOfMinute() && 376: iMillisOfSecond == iBase.millisOfSecond() ) ? 1 : 0) | 377: 378: ((iMillisOfDay == iBase.millisOfDay()) ? 2 : 0) | 379: 380: ((iYear == iBase.year() && 381: iMonthOfYear == iBase.monthOfYear() && 382: iDayOfMonth == iBase.dayOfMonth() ) ? 4 : 0); 383: } 384: 385: iBaseFlags = flags; 386: } 387: 388: private void readObject(ObjectInputStream in) throws IOException, ClassNotFoundException { 389: in.defaultReadObject(); 390: setFields(); 391: } 392: 393: /** 394: * A container of fields used for assembling a chronology. 395: */ 396: public static final class Fields { 397: public DurationField millis; 398: public DurationField seconds; 399: public DurationField minutes; 400: public DurationField hours; 401: public DurationField halfdays; 402: 403: public DurationField days; 404: public DurationField weeks; 405: public DurationField weekyears; 406: public DurationField months; 407: public DurationField years; 408: public DurationField centuries; 409: public DurationField eras; 410: 411: public DateTimeField millisOfSecond; 412: public DateTimeField millisOfDay; 413: public DateTimeField secondOfMinute; 414: public DateTimeField secondOfDay; 415: public DateTimeField minuteOfHour; 416: public DateTimeField minuteOfDay; 417: public DateTimeField hourOfDay; 418: public DateTimeField clockhourOfDay; 419: public DateTimeField hourOfHalfday; 420: public DateTimeField clockhourOfHalfday; 421: public DateTimeField halfdayOfDay; 422: 423: public DateTimeField dayOfWeek; 424: public DateTimeField dayOfMonth; 425: public DateTimeField dayOfYear; 426: public DateTimeField weekOfWeekyear; 427: public DateTimeField weekyear; 428: public DateTimeField weekyearOfCentury; 429: public DateTimeField monthOfYear; 430: public DateTimeField year; 431: public DateTimeField yearOfEra; 432: public DateTimeField yearOfCentury; 433: public DateTimeField centuryOfEra; 434: public DateTimeField era; 435: 436: Fields() { 437: } 438: 439: /** 440: * Copy the supported fields from a chronology into this container. 441: */ 442: public void copyFieldsFrom(Chronology chrono) { 443: { 444: DurationField f; 445: if (isSupported(f = chrono.millis())) { 446: millis = f; 447: } 448: if (isSupported(f = chrono.seconds())) { 449: seconds = f; 450: } 451: if (isSupported(f = chrono.minutes())) { 452: minutes = f; 453: } 454: if (isSupported(f = chrono.hours())) { 455: hours = f; 456: } 457: if (isSupported(f = chrono.halfdays())) { 458: halfdays = f; 459: } 460: if (isSupported(f = chrono.days())) { 461: days = f; 462: } 463: if (isSupported(f = chrono.weeks())) { 464: weeks = f; 465: } 466: if (isSupported(f = chrono.weekyears())) { 467: weekyears = f; 468: } 469: if (isSupported(f = chrono.months())) { 470: months = f; 471: } 472: if (isSupported(f = chrono.years())) { 473: years = f; 474: } 475: if (isSupported(f = chrono.centuries())) { 476: centuries = f; 477: } 478: if (isSupported(f = chrono.eras())) { 479: eras = f; 480: } 481: } 482: 483: { 484: DateTimeField f; 485: if (isSupported(f = chrono.millisOfSecond())) { 486: millisOfSecond = f; 487: } 488: if (isSupported(f = chrono.millisOfDay())) { 489: millisOfDay = f; 490: } 491: if (isSupported(f = chrono.secondOfMinute())) { 492: secondOfMinute = f; 493: } 494: if (isSupported(f = chrono.secondOfDay())) { 495: secondOfDay = f; 496: } 497: if (isSupported(f = chrono.minuteOfHour())) { 498: minuteOfHour = f; 499: } 500: if (isSupported(f = chrono.minuteOfDay())) { 501: minuteOfDay = f; 502: } 503: if (isSupported(f = chrono.hourOfDay())) { 504: hourOfDay = f; 505: } 506: if (isSupported(f = chrono.clockhourOfDay())) { 507: clockhourOfDay = f; 508: } 509: if (isSupported(f = chrono.hourOfHalfday())) { 510: hourOfHalfday = f; 511: } 512: if (isSupported(f = chrono.clockhourOfHalfday())) { 513: clockhourOfHalfday = f; 514: } 515: if (isSupported(f = chrono.halfdayOfDay())) { 516: halfdayOfDay = f; 517: } 518: if (isSupported(f = chrono.dayOfWeek())) { 519: dayOfWeek = f; 520: } 521: if (isSupported(f = chrono.dayOfMonth())) { 522: dayOfMonth = f; 523: } 524: if (isSupported(f = chrono.dayOfYear())) { 525: dayOfYear = f; 526: } 527: if (isSupported(f = chrono.weekOfWeekyear())) { 528: weekOfWeekyear = f; 529: } 530: if (isSupported(f = chrono.weekyear())) { 531: weekyear = f; 532: } 533: if (isSupported(f = chrono.weekyearOfCentury())) { 534: weekyearOfCentury = f; 535: } 536: if (isSupported(f = chrono.monthOfYear())) { 537: monthOfYear = f; 538: } 539: if (isSupported(f = chrono.year())) { 540: year = f; 541: } 542: if (isSupported(f = chrono.yearOfEra())) { 543: yearOfEra = f; 544: } 545: if (isSupported(f = chrono.yearOfCentury())) { 546: yearOfCentury = f; 547: } 548: if (isSupported(f = chrono.centuryOfEra())) { 549: centuryOfEra = f; 550: } 551: if (isSupported(f = chrono.era())) { 552: era = f; 553: } 554: } 555: } 556: 557: private static boolean isSupported(DurationField field) { 558: return field == null ? false : field.isSupported(); 559: } 560: 561: private static boolean isSupported(DateTimeField field) { 562: return field == null ? false : field.isSupported(); 563: } 564: } 565: }
| ID | Line | Type | Detected |
|---|---|---|---|
| 56 | 102 | Remove method call | |
| 57 | 107 | Negate jump condition (Replace IFNULL with IFNONNULL) | |
| 58 | 108 | Remove method call | |
| 60 | 118 | Replace a constant (Replace 6 with 0(INT)) | |
| 62 | 118 | Replace a constant (Replace 6 with 5(INT)) | |
| 61 | 118 | Replace a constant (Replace 6 with 7(INT)) | |
| 66 | 118(1) | Replace a constant (Replace 6 with 5(INT)) | |
| 64 | 118(1) | Replace a constant (Replace 6 with 0(INT)) | |
| 65 | 118(1) | Replace a constant (Replace 6 with 7(INT)) | |
| 59 | 118 | Negate jump condition (Replace IFNULL with IFNONNULL) | |
| 67 | 118(1) | Negate jump condition (Replace IF_ICMPNE with IF_ICMPEQ) | |
| 63 | 118 | Replace arithmetic operator (Replace IAND with IOR) | |
| 68 | 120 | Remove method call | |
| 69 | 122 | Remove method call | |
| 71 | 131 | Replace a constant (Replace 5 with 0(INT)) | |
| 73 | 131 | Replace a constant (Replace 5 with 4(INT)) | |
| 72 | 131 | Replace a constant (Replace 5 with 6(INT)) | |
| 76 | 131(1) | Replace a constant (Replace 5 with 6(INT)) | |
| 75 | 131(1) | Replace a constant (Replace 5 with 0(INT)) | |
| 77 | 131(1) | Replace a constant (Replace 5 with 4(INT)) | |
| 70 | 131 | Negate jump condition (Replace IFNULL with IFNONNULL) | |
| 78 | 131(1) | Negate jump condition (Replace IF_ICMPNE with IF_ICMPEQ) | |
| 74 | 131 | Replace arithmetic operator (Replace IAND with IOR) | |
| 79 | 133 | Remove method call | |
| 80 | 136 | Remove method call | |
| 83 | 146 | Replace a constant (Replace 1 with 0(INT)) | |
| 82 | 146 | Replace a constant (Replace 1 with 2(INT)) | |
| 85 | 146(1) | Replace a constant (Replace 1 with 2(INT)) | |
| 86 | 146(1) | Replace a constant (Replace 1 with 0(INT)) | |
| 81 | 146 | Negate jump condition (Replace IFNULL with IFNONNULL) | |
| 87 | 146(1) | Negate jump condition (Replace IF_ICMPNE with IF_ICMPEQ) | |
| 84 | 146 | Replace arithmetic operator (Replace IAND with IOR) | |
| 88 | 148 | Remove method call | |
| 89 | 151 | Remove method call | |
| 90 | 320 | Negate jump condition (Replace IFNULL with IFNONNULL) | |
| 91 | 321 | Remove method call | |
| 92 | 323 | Remove method call | |
| 93 | 327 | Negate jump condition (Replace IFNULL with IFNONNULL) | |
| 94 | 327 | Remove method call | |
| 95 | 328 | Negate jump condition (Replace IFNULL with IFNONNULL) | |
| 96 | 328 | Remove method call | |
| 97 | 329 | Negate jump condition (Replace IFNULL with IFNONNULL) | |
| 98 | 329 | Remove method call | |
| 99 | 330 | Negate jump condition (Replace IFNULL with IFNONNULL) | |
| 100 | 330 | Remove method call | |
| 101 | 331 | Negate jump condition (Replace IFNULL with IFNONNULL) | |
| 102 | 331 | Remove method call | |
| 103 | 332 | Negate jump condition (Replace IFNULL with IFNONNULL) | |
| 104 | 332 | Remove method call | |
| 105 | 333 | Negate jump condition (Replace IFNULL with IFNONNULL) | |
| 106 | 333 | Remove method call | |
| 107 | 334 | Negate jump condition (Replace IFNULL with IFNONNULL) | |
| 108 | 334 | Remove method call | |
| 109 | 335 | Negate jump condition (Replace IFNULL with IFNONNULL) | |
| 110 | 335 | Remove method call | |
| 111 | 336 | Negate jump condition (Replace IFNULL with IFNONNULL) | |
| 112 | 336 | Remove method call | |
| 113 | 337 | Negate jump condition (Replace IFNULL with IFNONNULL) | |
| 114 | 337 | Remove method call | |
| 115 | 338 | Negate jump condition (Replace IFNULL with IFNONNULL) | |
| 116 | 338 | Remove method call | |
| 117 | 343 | Negate jump condition (Replace IFNULL with IFNONNULL) | |
| 118 | 343 | Remove method call | |
| 119 | 344 | Negate jump condition (Replace IFNULL with IFNONNULL) | |
| 120 | 344 | Remove method call | |
| 121 | 345 | Negate jump condition (Replace IFNULL with IFNONNULL) | |
| 122 | 345 | Remove method call | |
| 123 | 346 | Negate jump condition (Replace IFNULL with IFNONNULL) | |
| 124 | 346 | Remove method call | |
| 125 | 347 | Negate jump condition (Replace IFNULL with IFNONNULL) | |
| 126 | 347 | Remove method call | |
| 127 | 348 | Negate jump condition (Replace IFNULL with IFNONNULL) | |
| 128 | 348 | Remove method call | |
| 129 | 349 | Negate jump condition (Replace IFNULL with IFNONNULL) | |
| 130 | 349 | Remove method call | |
| 131 | 350 | Negate jump condition (Replace IFNULL with IFNONNULL) | |
| 132 | 350 | Remove method call | |
| 133 | 351 | Negate jump condition (Replace IFNULL with IFNONNULL) | |
| 134 | 351 | Remove method call | |
| 135 | 352 | Negate jump condition (Replace IFNULL with IFNONNULL) | |
| 136 | 352 | Remove method call | |
| 137 | 353 | Negate jump condition (Replace IFNULL with IFNONNULL) | |
| 138 | 353 | Remove method call | |
| 139 | 354 | Negate jump condition (Replace IFNULL with IFNONNULL) | |
| 140 | 354 | Remove method call | |
| 141 | 355 | Negate jump condition (Replace IFNULL with IFNONNULL) | |
| 142 | 355 | Remove method call | |
| 143 | 356 | Negate jump condition (Replace IFNULL with IFNONNULL) | |
| 144 | 356 | Remove method call | |
| 145 | 357 | Negate jump condition (Replace IFNULL with IFNONNULL) | |
| 146 | 357 | Remove method call | |
| 147 | 358 | Negate jump condition (Replace IFNULL with IFNONNULL) | |
| 148 | 358 | Remove method call | |
| 149 | 359 | Negate jump condition (Replace IFNULL with IFNONNULL) | |
| 150 | 359 | Remove method call | |
| 151 | 360 | Negate jump condition (Replace IFNULL with IFNONNULL) | |
| 152 | 360 | Remove method call | |
| 153 | 361 | Negate jump condition (Replace IFNULL with IFNONNULL) | |
| 154 | 361 | Remove method call | |
| 155 | 362 | Negate jump condition (Replace IFNULL with IFNONNULL) | |
| 156 | 362 | Remove method call | |
| 157 | 363 | Negate jump condition (Replace IFNULL with IFNONNULL) | |
| 158 | 363 | Remove method call | |
| 159 | 364 | Negate jump condition (Replace IFNULL with IFNONNULL) | |
| 160 | 364 | Remove method call | |
| 161 | 365 | Negate jump condition (Replace IFNULL with IFNONNULL) | |
| 162 | 365 | Remove method call | |
| 163 | 369 | Negate jump condition (Replace IFNONNULL with IFNULL) | |
| 164 | 370 | Replace a constant (Replace 0 with 1(INT)) | |
| 165 | 370 | Replace a constant (Replace 0 with -1(INT)) | |
| 174 | 372 | Replace a constant (Replace 1 with 2(INT)) | |
| 175 | 372 | Replace a constant (Replace 1 with 0(INT)) | |
| 177 | 372(1) | Replace a constant (Replace 0 with -1(INT)) | |
| 176 | 372(1) | Replace a constant (Replace 0 with 1(INT)) | |
| 182 | 372(2) | Replace a constant (Replace 2 with 0(INT)) | |
| 180 | 372(2) | Replace a constant (Replace 2 with 3(INT)) | |
| 181 | 372(2) | Replace a constant (Replace 2 with 1(INT)) | |
| 183 | 372(3) | Replace a constant (Replace 0 with 1(INT)) | |
| 184 | 372(3) | Replace a constant (Replace 0 with -1(INT)) | |
| 194 | 372(4) | Replace a constant (Replace 4 with 5(INT)) | |
| 192 | 372(4) | Replace a constant (Replace 4 with 3(INT)) | |
| 193 | 372(4) | Replace a constant (Replace 4 with 0(INT)) | |
| 196 | 372(5) | Replace a constant (Replace 0 with -1(INT)) | |
| 195 | 372(5) | Replace a constant (Replace 0 with 1(INT)) | |
| 167 | 372 | Negate jump condition (Replace IF_ACMPNE with IF_ACMPEQ) | |
| 169 | 372(1) | Negate jump condition (Replace IF_ACMPNE with IF_ACMPEQ) | |
| 171 | 372(2) | Negate jump condition (Replace IF_ACMPNE with IF_ACMPEQ) | |
| 173 | 372(3) | Negate jump condition (Replace IF_ACMPNE with IF_ACMPEQ) | |
| 179 | 372(4) | Negate jump condition (Replace IF_ACMPNE with IF_ACMPEQ) | |
| 187 | 372(5) | Negate jump condition (Replace IF_ACMPNE with IF_ACMPEQ) | |
| 189 | 372(6) | Negate jump condition (Replace IF_ACMPNE with IF_ACMPEQ) | |
| 191 | 372(7) | Negate jump condition (Replace IF_ACMPNE with IF_ACMPEQ) | |
| 185 | 372 | Replace arithmetic operator (Replace IOR with IAND) | |
| 197 | 372(1) | Replace arithmetic operator (Replace IOR with IAND) | |
| 166 | 372 | Remove method call | |
| 168 | 372(1) | Remove method call | |
| 170 | 372(2) | Remove method call | |
| 172 | 372(3) | Remove method call | |
| 178 | 372(4) | Remove method call | |
| 186 | 372(5) | Remove method call | |
| 188 | 372(6) | Remove method call | |
| 190 | 372(7) | Remove method call | |
| 198 | 389 | Remove method call | |
| 199 | 390 | Remove method call | |
| 5593 | 445 | Negate jump condition (Replace IFEQ with IFNE) | |
| 5591 | 445 | Remove method call | |
| 5592 | 445(1) | Remove method call | |
| 5596 | 448 | Negate jump condition (Replace IFEQ with IFNE) | |
| 5594 | 448 | Remove method call | |
| 5595 | 448(1) | Remove method call | |
| 5599 | 451 | Negate jump condition (Replace IFEQ with IFNE) | |
| 5597 | 451 | Remove method call | |
| 5598 | 451(1) | Remove method call | |
| 5602 | 454 | Negate jump condition (Replace IFEQ with IFNE) | |
| 5600 | 454 | Remove method call | |
| 5601 | 454(1) | Remove method call | |
| 5605 | 457 | Negate jump condition (Replace IFEQ with IFNE) | |
| 5603 | 457 | Remove method call | |
| 5604 | 457(1) | Remove method call | |
| 5608 | 460 | Negate jump condition (Replace IFEQ with IFNE) | |
| 5606 | 460 | Remove method call | |
| 5607 | 460(1) | Remove method call | |
| 5611 | 463 | Negate jump condition (Replace IFEQ with IFNE) | |
| 5609 | 463 | Remove method call | |
| 5610 | 463(1) | Remove method call | |
| 5614 | 466 | Negate jump condition (Replace IFEQ with IFNE) | |
| 5612 | 466 | Remove method call | |
| 5613 | 466(1) | Remove method call | |
| 5617 | 469 | Negate jump condition (Replace IFEQ with IFNE) | |
| 5615 | 469 | Remove method call | |
| 5616 | 469(1) | Remove method call | |
| 5620 | 472 | Negate jump condition (Replace IFEQ with IFNE) | |
| 5618 | 472 | Remove method call | |
| 5619 | 472(1) | Remove method call | |
| 5623 | 475 | Negate jump condition (Replace IFEQ with IFNE) | |
| 5621 | 475 | Remove method call | |
| 5622 | 475(1) | Remove method call | |
| 5626 | 478 | Negate jump condition (Replace IFEQ with IFNE) | |
| 5624 | 478 | Remove method call | |
| 5625 | 478(1) | Remove method call | |
| 5629 | 485 | Negate jump condition (Replace IFEQ with IFNE) | |
| 5627 | 485 | Remove method call | |
| 5628 | 485(1) | Remove method call | |
| 5632 | 488 | Negate jump condition (Replace IFEQ with IFNE) | |
| 5630 | 488 | Remove method call | |
| 5631 | 488(1) | Remove method call | |
| 5635 | 491 | Negate jump condition (Replace IFEQ with IFNE) | |
| 5633 | 491 | Remove method call | |
| 5634 | 491(1) | Remove method call | |
| 5638 | 494 | Negate jump condition (Replace IFEQ with IFNE) | |
| 5636 | 494 | Remove method call | |
| 5637 | 494(1) | Remove method call | |
| 5641 | 497 | Negate jump condition (Replace IFEQ with IFNE) | |
| 5639 | 497 | Remove method call | |
| 5640 | 497(1) | Remove method call | |
| 5644 | 500 | Negate jump condition (Replace IFEQ with IFNE) | |
| 5642 | 500 | Remove method call | |
| 5643 | 500(1) | Remove method call | |
| 5647 | 503 | Negate jump condition (Replace IFEQ with IFNE) | |
| 5645 | 503 | Remove method call | |
| 5646 | 503(1) | Remove method call | |
| 5650 | 506 | Negate jump condition (Replace IFEQ with IFNE) | |
| 5648 | 506 | Remove method call | |
| 5649 | 506(1) | Remove method call | |
| 5653 | 509 | Negate jump condition (Replace IFEQ with IFNE) | |
| 5651 | 509 | Remove method call | |
| 5652 | 509(1) | Remove method call | |
| 5656 | 512 | Negate jump condition (Replace IFEQ with IFNE) | |
| 5654 | 512 | Remove method call | |
| 5655 | 512(1) | Remove method call | |
| 5659 | 515 | Negate jump condition (Replace IFEQ with IFNE) | |
| 5657 | 515 | Remove method call | |
| 5658 | 515(1) | Remove method call | |
| 5662 | 518 | Negate jump condition (Replace IFEQ with IFNE) | |
| 5660 | 518 | Remove method call | |
| 5661 | 518(1) | Remove method call | |
| 5665 | 521 | Negate jump condition (Replace IFEQ with IFNE) | |
| 5663 | 521 | Remove method call | |
| 5664 | 521(1) | Remove method call | |
| 5668 | 524 | Negate jump condition (Replace IFEQ with IFNE) | |
| 5666 | 524 | Remove method call | |
| 5667 | 524(1) | Remove method call | |
| 5671 | 527 | Negate jump condition (Replace IFEQ with IFNE) | |
| 5669 | 527 | Remove method call | |
| 5670 | 527(1) | Remove method call | |
| 5674 | 530 | Negate jump condition (Replace IFEQ with IFNE) | |
| 5672 | 530 | Remove method call | |
| 5673 | 530(1) | Remove method call | |
| 5677 | 533 | Negate jump condition (Replace IFEQ with IFNE) | |
| 5675 | 533 | Remove method call | |
| 5676 | 533(1) | Remove method call | |
| 5680 | 536 | Negate jump condition (Replace IFEQ with IFNE) | |
| 5678 | 536 | Remove method call | |
| 5679 | 536(1) | Remove method call | |
| 5683 | 539 | Negate jump condition (Replace IFEQ with IFNE) | |
| 5681 | 539 | Remove method call | |
| 5682 | 539(1) | Remove method call | |
| 5686 | 542 | Negate jump condition (Replace IFEQ with IFNE) | |
| 5684 | 542 | Remove method call | |
| 5685 | 542(1) | Remove method call | |
| 5689 | 545 | Negate jump condition (Replace IFEQ with IFNE) | |
| 5687 | 545 | Remove method call | |
| 5688 | 545(1) | Remove method call | |
| 5692 | 548 | Negate jump condition (Replace IFEQ with IFNE) | |
| 5690 | 548 | Remove method call | |
| 5691 | 548(1) | Remove method call | |
| 5695 | 551 | Negate jump condition (Replace IFEQ with IFNE) | |
| 5693 | 551 | Remove method call | |
| 5694 | 551(1) | Remove method call | |
| 5697 | 558 | Replace a constant (Replace 0 with 1(INT)) | |
| 5698 | 558 | Replace a constant (Replace 0 with -1(INT)) | |
| 5696 | 558 | Negate jump condition (Replace IFNONNULL with IFNULL) | |
| 5699 | 558 | Remove method call | |
| 5702 | 562 | Replace a constant (Replace 0 with -1(INT)) | |
| 5701 | 562 | Replace a constant (Replace 0 with 1(INT)) | |
| 5700 | 562 | Negate jump condition (Replace IFNONNULL with IFNULL) | |
| 5703 | 562 | Remove method call |


--- layout: post status: publish published: true title: Localizable date controls author: display_name: Tomas Restrepo login: tomasr email<EMAIL_ADDRESS>url: http://winterdom.com/ author_login: tomasr author_email<EMAIL_ADDRESS>author_url: http://winterdom.com/ wordpress_id: 271 wordpress_url: http://winterdom.com/2005/12/localizabledatecontrols date: '2005-12-06 19:42:56 +0000' date_gmt: '2005-12-06 19:42:56 +0000' categories: - ".NET" tags: [] comments: - id: 199 author: Carmai Constant author_email<EMAIL_ADDRESS>author_url: '' date: '2007-07-03 10:58:08 +0000' date_gmt: '2007-07-03 10:58:08 +0000' content: | Hi Thomas, Do you have a code sample for these controls? Thanks - id: 200 author: Tomas Restrepo author_email<EMAIL_ADDRESS>author_url: http://www.winterdom.com/weblog/ date: '2007-07-03 11:11:02 +0000' date_gmt: '2007-07-03 11:11:02 +0000' content: | Carmai, Unfortunately, no; the code belonged to a client of my former employer. That said, I believe some commercial companies offer localizable datetime controls now... ---
A few weeks ago I mentioned (if not here, somewhere els) I had been working on a replacement DateTimePicker control for one of our projects, because the base DateTimePicker control in Windows Forms did not really support the .NET style of globalization, as it is based on the native OS control which is only aware of the currently selected regional settings. The problem is that our application needed to be controled explicitly only by the culture selected in the Windows Application itself (CurrentCulture/CurrentUICulture), and not have a mixed bag of controls in incompatible formats/languages.
However, I never did write about what the end result looked liked :)
I'm not much of a control designer/developer, but I must admit that writing windows forms controls can be very entertaining at times (and quite frustrating, others), but, if I may say so myself, I was quite pleased by the end result: A control that looked fairly similar to the original native MonthCalendar and DateTimePicker controls. Granted, they are simpler (they don't support a lot of the extra stuff the native ones support, which we didn't need, like multi-month display, or selection of date ranges), but they could certainly be extended if needed.
And, of course, they actually do work based on the date formats selected in the current culture :). Here's a small screenshot of what they look like:
While working with these, I did get a chance to explore a few very nifty new features in Windows Forms 2.0, like the new visual styles support in System.Windows.Forms.VisualStyles, the ToolStripControlHost class (for a cool example see here), and all the cool stuff in the System.Globalization namespace.


Seasoned Delphi Developer and Microsoft Certified Professional desktop developer and programmer, with strong practical experience in project requirements gathering, business analysis and programming; devoted to functional programming and information architecture.
Application Developer - Web Developer - Microsoft Certified Professional


The Brain: Gee, Pinky, what do you want to do tonight? Pinky: The same thing we do every night, Brain, Try to take over the world
The Brain: Gee, Pinky, what do you want to do tonight? Pinky: The same thing we do every night, Brain, Try to take over the world


--- layout: jsdoc title: "Class: CacheableResponsePlugin" jsdocNav: - Modules: - workbox-background-sync - workbox-broadcast-cache-update - workbox-build - workbox-cache-expiration - workbox-cacheable-response - workbox-google-analytics - workbox-precaching - workbox-routing - workbox-runtime-caching - workbox-sw ---
Use this plugin to cache responses with certain HTTP status codes or header values.
Defining both status codes and headers will cache requests with a matching status code and a matching header.
This class is meant to be automatically invoked as a plugin to a
RequestWrapper, which
is used by the workbox-sw
and workbox-runtime-caching
modules.
If you would like to use this functionality outside of the RequestWrapper
context, please use the CacheableResponse
class directly.
new goog.cacheableResponse.CacheableResponsePlugin({
statuses: [0, 200, 404],
headers: {
'Example-Header-1': 'Header-Value-1'
'Example-Header-2': 'Header-Value-2'
}
});


HI there my name is Vishal Gupta. This is a Sample for Jumbotron. Please Appreciate it.
* Ignore the grammar. :)


@* * Copyright 2021 HM Revenue & Customs * * Licensed under the Apache License, Version 2.0 (the "License"); * you may not use this file except in compliance with the License. * You may obtain a copy of the License at * * http://www.apache.org/licenses/LICENSE-2.0 * * Unless required by applicable law or agreed to in writing, software * distributed under the License is distributed on an "AS IS" BASIS, * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. * See the License for the specific language governing permissions and * limitations under the License. *@ @import config.ApplicationConfig @import play.twirl.api.HtmlFormat @this(atedMain: atedMain) @(editContactDetailsEmailForm: Form[models.EditContactDetailsEmail], serviceInfoContent: Html = HtmlFormat.empty, backLink:Option[String])(implicit authContext: StandardAuthRetrievals, messages: Messages, request: Request[AnyContent], appConfig: ApplicationConfig) @import uk.gov.hmrc.play.views.html.helpers._ @import views.html.helpers._ @implicitFormInstance = @{ Some(editContactDetailsEmailForm) } @pageScripts = { } @atedMain(title = messages("ated.contact-details-edit-email.header"), serviceInfoContent = serviceInfoContent, pageScripts = Some(pageScripts)) { @pageHeadersAndError(backLink, "pre-heading", messages("ated.contact-details-edit-email.subheader"), "contact-details-email-header", messages("ated.contact-details-edit-email.header"))
@messages("ated.contact-details-email-lede")
@Html(messages("ated.contact-details.email.risk.help.answer"))


UPDATE: My colleague Fausto recently had a great article around the relationship between data systems and DevOps - my favorite quote was, “If you are on the path to being a data-driven company, you have to be on the path to being a development-enabled company.”
##Getting Started
Understanding the relationship between software development and data science is important: it helps ensure that solutions are scalable, responsive, and accurate; it also helps ensure that one is hiring and nurturing complementary talent for putting algorithms and data products into production. Thinking about this, I put together a list of books that have helped me get a sense of modern innovations: from database types to continuous delivery practices to test-driven or behavior-driven development. We benefit from these innovations every day:
- Evolutions in distributed computing form the basis of cloud services (thanks Gmail!)
- Key-Value Store databases are great for storing shopping cart information (thanks Amazon!)
- Continuous Delivery is one thing that allows Facebook to “Move Fast and Break Things.”
So, getting a sense of how these things work is a good start for being able to understand where the trends are going and how they might be useful for a business undergoing a digital transformation. For each book, I include a small description and, at the end, give some suggestions for staying fresh with architectural development.
- NoSQL Distilled: Martin Fowler and Pramod Sadalage
- Continuous Delivery: Jez Humble and David Farley
- Specification by Example: Gojko Adzic
##NoSQL Distilled
This book is a great read for being introduced to the many different types of databases that have emerged as the use of distributed computing has grown. The book also walks through concepts present in distributed computing (e.g., ACID vs. BASE, the CAP Theorem , types of sharding, and read-write availability).
NoSQL is a broad-based term that refers to schemaless databases. Some schema/structure is required to make sense of the data, but this can be provided de facto by the application language (implicit schema). Traditional RDBMS have a lot of utility; NoSQL databases (e.g., Key-Value, Document, Column-Family, Graph) have led to a rise of polyglot persistence - which refers to combining different database models when appropriate to serve an application’s needs. UPDATE: A few examples of when (and when not) to use different databases can be found at this link.
The book describes two key reasons to use NoSQL technology as being:
- To improve programmer productivity by using a database that better matches an application’s needs
- To improve data access performance via some combination of handling larger data volumes, reducing latency, and improving throughput
Service encapsulation supports changing data storage technologies as needs and technology evolve. This book may be a good start to considering microservices architectures; turning parts of applications into services also allows an architect to introduce NoSQL into an existing application. Considering the bullet points above, it’s also important to note that testing expectations about programmer productivity and/or performance should be done before committing to using these technologies.
##Continuous Delivery
Continuous Delivery refers to a software development discipline in which software is built in such a way that it can be deployed at any time. This book popularized the term “bring the pain forward” - which refers to the practice of trying to create a testing environment in which small changes are pushed to production, the developer knows if the push was successful almost immediately, and that developer becomes responsible for fixing the code if there is a break. Microsoft recently shared their engineering journey to Continuous Delivery, noting that “Engineers begin to riot if we deploy less than 10x per week.”
The book is divided into three sections:
- Foundations: This section outlines principles any organization should follow in setting up a Continuous Delivery infrastructure.
- Deployment Pipeline: This walks through different stages of the pipeline, with a focus on scripting, the commit stage, and testing.
- Delivery Ecosystem: This details the ongoing management of delivery, including compliance, version control, components, dependencies, data, etc.
One key principle of continuous delivery is automation. This should be the only way in which the software is ever deployed. The remedy is to integrate the testing, deployment, and release activities into the development process. Make them a normal and ongoing part of development so that by the time you are ready to release your system into production there is little to no risk, because you have rehearsed it on many different occasions in a progressively more production-like sequence of test environments.
Another is frequent release of software to production. If releases are frequent, the delta between releases will be small. This significantly reduces the risk associated with releasing and makes it much easier to roll back. Frequent releases also lead to faster feedback—indeed, they require it. Much of the book concentrates on getting feedback on changes to your application and its associated configuration (including its environment, deployment process, and data) as quickly as possible. Anything that changes between environments should be captured as configuration information.
Finally, a third principle is continuous collaboration. It is essential that everybody involved in the process of delivering software is involved in the feedback process. That includes developers, testers, operations staff, database administrators, infrastructure specialists, and managers. When something needs doing, it is the responsibility of the whole team to stop what they are doing and decide on a course of action. Only once this is done should the team carry on with their work.
##Specification by Example
Specification by Example is a reference to a practice very similar to Test-Driven Development (TDD) or Behavior-Driven Development (BDD). It walks through a process for articulating clear software product specifications that are easily understood by both the business side and engineers. These principles are important because: (1) they allow for precise testing, and (2) as such, they shorten the time between idea-generation and deployment. This, with process automation, is a key component of Continuous Delivery.
The book reminds me of one of my favorite books on product management: Bob Cooper’s Winning at New Products. Both have a focus on managing the risk inherent in cross-functional / interdisciplinary teams and ask, “How can I develop the right common language to foster communication and improve decision making?” Specification by Example can be long at times, especially if you already accept the benefits of design thinking. It spends a lot of time focusing on how companies can make the transition to adopting Specification by Example practices and highlighting case studies of how it has been done by others. For me, I got a huge value from learning about living documentation.
Living documentation is a process by which the tests in the deployment pipeline are synonymous with the product specifications - the product specifications are executable. An automated Specification with Examples that is comprehensible and accessible to all team members becomes an executable specification. This can be used as a target for development and easily check if the system does what was agreed on, and the same documentation provides clarification for business users. If a specification needs changed, it changes is only one place.
When a software system is continuously validated against a set of executable specifications, a team can be certain that the system will do what the specifications say—or, to put it differently, that the specifications will continue to describe what the system does. Those specifications live with the system, and they’re always consistent.
Living documentation also fosters collaboration. It allows teams to join together and analyze the impact of proposed changes and discuss potential solutions. It also allows them to make use of existing documentation by extending it for new requirements. Instead of relying on a single person to get the specifications right in isolation, successful delivery teams collaborate with the business users to specify the solution. Pretty cool!
##How to stay up to date?
Again, these are books that have been pointed in my direction to understand some of the recent innovations in building robust, scalable systems. The best way to know what is useful, though, is to study what is being done in practice. Fortunately, the engineering teams of many large technology companies write about these frequently on their own blogs, for example:
- Data Infrastructure at AirBnb
- Uber’s Schemaless Datastore with MySQL
- Netflix - A Microscope on Microservices
- A Beginner’s Guide to Scaling to 11M users on AWS
To stay up to date on what these companies are trying (and “why”), you can add these sites to an RSS feed. They are also frequently shared on Hacker News.


Tarzan A film review by Marty Mapes Copyright 1999 Marty Mapes
** (out of 4) I went to TARZAN hoping to hate it. I am generally cynical about Disney movies, and I hoped I could pull a "Mr. Cranky."
I still won't say I liked TARZAN, but I liked parts of it, and on the whole I couldn't really fault it, given the genre. But it never wowed me and won me over. I never felt sheepish for having doubted Disney, as I did with A BUG'S LIFE.
Plotwise, TARZAN is a fairly traditional retelling. A shipwrecked couple are killed and their infant son is adopted by gorillas. The boy grows up never knowing why he looks different from his friends, never knowing about human beings.
One day, after Tarzan (voiced by Tony Goldwyn) has grown, he hears a loud bang in the distance. It is a party of people. A ridiculous-looking naturalist (Nigel Hawthorne), his daughter Jane (Minnie Driver), and their trophy-hunting bodyguard Clayton (Brian Blessed) are looking for gorillas.
After their first encounter, Tarzan and Jane start hanging around together (ouch, sorry). Meanwhile, the goofy professor Porter and the slippery villain try to get Tarzan to say where the gorilla nesting site is, the prof so he can study them, the bodyguard so he can cage them and sell them.
As with other recent Disney cartoons, this one is a musical. Phil Collins belts out the pop hits over montages of Tarzan "skating" down tree branches. (The music is always over a montage because the cast members don't perform their own songs. For example, Tarzan's "mother" starts the first few bars of a lullaby, then Collins takes over the soundtrack and the visuals shift into MTV mode.) None of the songs are too saccharine, and there's even one that's fairly catchy -- "Trashing the Camp."
Another trademark of Disney cartoons is that they always manage to top themselves when it comes to technical innovation. First it was the spinning ballroom shot in BEAUTY AND THE BEAST. Then it was the focus pulls on THE LION KING. In TARZAN, the trick is "hand-held" camera.
Early in the film a leopard is chasing Tarzan's adoptive mother. The scene happens very quickly anyway, and the "camera" hops around trying to follow the action as though the virtual camera operator had legs. (The same technique is repeated later in the movie.) So why create this effect? Because they can? Because it hasn't been done before? To get film nerds like me to say "whoa"? Whatever the reason, it's a neat gimmick, even if it's gratuitous.
That brings me to a fairly big complaint about the movie. Because of the animators' acute technophilia, TARZAN is stylistically incoherent. Technical innovation may be neat, but that alone shouldn't be reason enough to include it in a movie.
The characters in TARZAN are all traditional-looking animated creatures. They could have been drawn for THE JUNGLE BOOK forty years ago. But the setting they inhabit has become hyperrealistic. With computer-modeled jungles, rivers, sunlight and shadows, it has become hard to tell for sure where the cartoon ends and "reality" begins -- until you change your focus to the cartoon apes in the foreground.
This inconsistency is a stylistic mistake. It keeps the audience from understanding and getting into the animated world. The characters and settings ARE animated separately, but they shouldn't look that way. Even assuming there were a good reason to mix two such disparate styles, Professor Porter's character introduces a third style that's even further out of place.
Set in the "real" jungle, Tarzan was animated with sharp, heroic lines, as was Jane. Clayton's figure was a bit more exaggerated, but as the villain, it was excusable. But professor Porter's form was neither realistic nor heroic. He was so flat, round, silly, and, well, cartoonish, that he would have fit in better with Mickey Mouse and Donald Duck. Each style might work on its own, but to ignore how they integrate is a mistake.
I have one more complaint, and to discuss it, I'll have to give away the ending. (That's okay, though. If you're familiar with the Disney formula, you already know what the ending is.)
The kid-movie justice system is insane.
My sister said it best: her daughter was telling her about a movie that had a happy ending because the bad guy died at the end. Later, to me, my sister was incredulous. "It's a HAPPY ending because someone you don't like is DEAD? What kind of message is that?"
Having observed this childish system of justice in movies ranging from TARZAN and A BUG'S LIFE (rated G) to CON AIR and THE HAND THAT ROCKS THE CRADLE (rated R), I've discovered a few other "rules." The good guys never do their own dirty work. The bad guy always dies because of his fatal flaw, usually greed, rabid perseverence, and/or pure, inhuman evilness. The more gruesome, sudden, and irreversible the death, the better. The Greeks had DEUS EX MACHINA endings. We have MORTIS EX FORMULA endings.
Ideally, we'd be teaching our kids to outwit their oppressors, not to hope for luck to bring their deaths. Unfortunately, that doesn't happen very often in movies. (A noteworthy exception is last year's "Ever After," which I strongly recommend.)
Back to TARZAN, I'm probably being too hard on this movie, when my real complaint is with the formula. Still, I wouldn't say I liked it, and I'd even go so far as to say that it doesn't quite measure up to other Disney offerings. I'm sure those of you with younger kids would enjoy an afternoon at TARZAN. But the rest of us could probably skip it.
Check out more current movie reviews at http://www.moviehabit.com
-- Marty Mapes<EMAIL_ADDRESS>Movie Habit http://www.moviehabit.com
The review above was posted to the
rec.arts.movies.reviews newsgroup (de.rec.film.kritiken for German reviews).
The Internet Movie Database accepts no responsibility for the contents of the
review and has no editorial control. Unless stated otherwise, the copyright
belongs to the author.
Please direct comments/criticisms of the review to relevant newsgroups.
Broken URLs inthe reviews are the responsibility of the author.
The formatting of the review is likely to differ from the original due
to ASCII to HTML conversion.
Related links: index of all rec.arts.movies.reviews reviews


We are running logistic regression analysis in the backend to generate probabilistic insights in order to match donors with homeless shelters based on their location and the amount they are donating.
You have been successfully matched with a shelter!


Contains: value+, database+, dataSet, mapping+, import+
| Attribute | Description |
|---|---|
| key | The name of the variable. |
| value | The value of the variable. |
| name | Descriptive name that describes the value. Mainly used in mappings to provide explanation to numerical values. |
<database> tag
Defines a database connections that can be used as source or target for the import.
| Attribute | Description |
|---|---|
| id | Id of database connection. Used by other parts of the import configuration. |
| vendor | Type of database. Values are: |
| connection | Connection string to database. Vendor specific. |
| Attribute | Description |
|---|---|
| name | Name of context. |
<mapping> tag
Defines a mapping of values. This can be used to bridge the use of different codes in the target and source database (e. g. 'male' vs 'M').
| Attribute | Description |
|---|---|
| id | Unique id of mapping. This can be then used as "id(...)" expression to perform the look-up. |
| Attribute | Description |
|---|---|
| keyColumn | Name of column that contains the key of mapping. For single query, just the column name. For two queries [databaseId].[column] |
| valueColumn | Name of column that contains the value of mapping. For single query, just the column name. For two queries [databaseId].[column] |
| nameColumn | Name of column that contains the option name of the mapping. |
| join | Join condition (only when using two queries). Format is [databaseId].[column] = [databaseId].[column] |
Contains: sql{1,2}
<sql> tag
Defines an SQL query to run on one of the database connections.
| Attribute | Description |
|---|---|
| db | Database id. Referring to database connections defined in a database tag. |
| query | SQL statement to execute. |
| name | Name to use in error messages. |
The import tag contains an sql tag to query the source data and then one or more insert tags to define in which tables new data is added. Note that by having multiple insert tags, it is possible to add data into more than one table.
| Attribute | Description |
|---|---|
| name | Name of import rule. This is used in the user interface to allow partial imports and display errors. |
Contains: sql, insert+
By using the expandRow tag multiple rows can be inserted into the target table for each row read.
The use of multiple insert tags allow insertion of values into multiple tables.
<insert> tag
For each row of the contained inserts data into the specified table.
| Attribute | Description |
|---|---|
| db | Reference to database connection defined in a database tag. |
| table | Table into which to insert the new data. |
Contains: expandRow?, column+
<column> tag
Specifies the value to use when inserting new rows into the target database.
| Attribute | Description |
|---|---|
| name | Column name in the target table (as specified in the insert tag). |
| value | Value to insert. The value can be a column name or a variable reference (e. g. "$year"). The value can also use mappings to transform the value by using the id of the mapping as function. I. e. "genderMap(GENDER)" uses the mapping with id 'genderMap' to transform the value found in the 'GENDER' column in the read row. |
| missing | Specifies how to handle rows that don't have a value (esp. after applying mappings).
'allowNull': allows NULL value. |
For example, the source table might contain the columns "MaleCount" and "FemaleCount", while the target table has "Gender" and "Count". For each read row, we need to create two rows: One row where Gender = "male", Count = MaleCount and the other where Gender = "female", Count = FemaleCount.
The expandRow tag provides this functionality by specifying a set of new columns that define fixed values for the columns containing data (i. e. in this case the Gender column) and one column to hold the actual value of each of the columns (in this case Count).
| Attribute | Description |
|---|---|
| headers | New columns that contain constant values describing the data. |
| valueHeader | Column that contains the value of the column we expand.
| Attribute | Description |
|---|---|
| column | Column that contains the value. This value will be placed under the column specified in the 'valueHeader' attribute of the parent expandRow tag. |
| values | Values that describe this column. The values are placed under the columns specified in the 'headers' attribute of the parent expandRow tag. |


Check if you want the job to prefer parameter values from failed builds.
This can be useful for circumstances where there is a long running build that would refresh an environment.
Failed builds are termed any build that was not successful or unstable.
This plugin takes the view that unstable builds still were for the most part functional.


Sliding UK health service performance sparks pre-election war of words
LONDON (Reuters) - Britain’s National Health Service recorded its worst ever performance in treating patients on emergency wards last month, a blow to Prime Minister Boris Johnson’s claim that only his Conservatives can safeguard the cherished institution.
The state-run NHS has provided free at the point of use healthcare for more than 70 years and is a highly emotive issue before the Dec. 12 election, with voters rating it as the second most important subject after Brexit.
NHS England said on Thursday the percentage of patients seen within four hours in all accident and emergency departments stood at 83.6% in October, down from the 85.2% the month before and 89.1% a year ago.
This was the worst performance since records began in 2004. The overall target of 95% was last met in July 2015.
The news sparked an immediate war of words.
Health Minister Matt Hancock said the figures showed Britain could not afford to have a Labour government run by Jeremy Corbyn.
“We are giving the biggest cash boost ever to our NHS, but Corbyn’s chaotic policies will put that at risk,” he said in a statement. The Conservatives have been in power since 2010.
Labour’s health spokesman, Jonathan Ashworth, said the Conservatives had “ushered in the worst NHS crisis on record”.
The four-hour target was first introduced by Labour’s Tony Blair in 2004 in a bid to stop patients being left to languish on trolleys in corridors.
Johnson has toured a string of hospitals since he took office in July, arguing that he will be able to invest more in the health service once he has resolved Brexit.
But the deteriorating performance shows the perils of holding a winter election. Polls show the left-leaning Labour Party is favored by voters to oversee the health service.
Providing care from the cradle to the grave, the NHS is struggling with record demand from a growing and ageing population, as well as cutbacks to social care services.
Labour lawmaker Yvette Cooper noted that 97% of patients were treated within four hours when the Conservatives came into office in 2010.
John Appleby, head of independent think-tank the Nuffield Trust, said the figures showed the next government would face one of the bleakest winters in the NHS’s history.
“As the election promises roll in, we should be under no illusion about the money, staff and time it will take to turn this situation around,” he said.