specifications

Possible Duplicate: JSON: why are forward slashes escaped? json.org states, that forward slashes (aka solidus, / ) can be escaped: "\/" However, unescaped slashes are valid, too: "/" What's the rational behind this? Does it come from the Javascript roots? (I.e., "</script>" is a problem in browser-based Javascript, see Douglas Crockford's comment ) Or has it any other reason? I've just published a review of this issue on my blog. I think you are right, that's the only reason. Also note that the slash is the only standard character allowed to be escaped. Usually JSON encoders do it wrong and

I have a enum SOME_ENUM : public enum SOME_ENUM { EN_ONE, EN_TWO, EN_THREE; } Will SOME_ENUM.values() always return the enums in the order of enum declarations: EN_ONE, EN_TWO, EN_THREE ? Is it a rule or it is not guaranteed to be not changed in the next JDK releases? GaryF The Java language specification uses this explicit language: @return an array containing the constants of this enum type, in the order they're declared [Source] So, yes, they will be returned in declaration order. It's worth noting that the order might change over time if someone changes the class so be very careful about

I am writing some code to parse MP4 files ... Is there a free source to get documentation on the MP4 File Format Specification. So far I have only found an ISO document which I would need to purchase ISO PDF . Is MP4 Not an open standard ? Here's the specification of the ISO base format , and here is the MP4 file format specification , both defined as part of the ISO/IEC 14496 standard. Also take a look at the QuickTime MP4 specification . It has a very clear explanation. Jaco " ISO 14496-1 Media Format " gives a detailed description of the MP4 layout: Akagi201 The latest ISO doc is ISO/IEC

I have tiny question about ClearCase. Help me please! When does config spec start to work? When I click CHECK OUT or CHECK IN ? I have test.c and I have config spec element * CHECKEDOUT element * .../branch_1/LATEST element * /main/LATEST -mkbranch branch_1 then I modify test.c , then I change config spec: element * CHECKEDOUT element * .../branch_2/LATEST element * /main/LATEST -mkbranch branch_2 Then I Check in test.c and I have: created /main/branch_1/1 . BUT WHY??? VonC The config spec will apply the rules on each update and on checkout, and on checkin (but not as you think it would). On

Why wasn't the java.lang.Object class declared to be abstract ? Surely for an Object to be useful it needs added state or behaviour, an Object class is an abstraction, and as such it should have been declared abstract ... why did they choose not to ? Ande, I think you are approaching this -- pun NOT intended -- with an unnecessary degree of abstraction. I think this (IMHO) unnecessary level of abstraction is what is causing the "problem" here. You are perhaps approaching this from a mathematical theoretical approach, where many of us are approaching this from a "programmer trying to solve

I found some information on the web as follows, but incomplete. http://en.wikipedia.org/wiki/Input/output_base_address http://wiki.osdev.org/I/O_Ports Where to download the specification? A good source for current (and not from 1994) I/O port map is chipset documentation, e.g. Intel® 7 Series Chipset Family PCH Datasheet (see section 9.3, I/O Map). For example, here are some ports which are commonly used in modern PCs and are not mentioned in the old lists: 2E-2F,4E-4F: Low Pin Count (LPC) interface, usually connected to Super I/O 0CF8, 0CFC: PCI configuration space access B2: ACPI and SMI