Territory vs ShareFS?
Rick Murray (539) 13422 posts |
Define “base OS”. The way I se It, Territory is part of the base OS. That is certainly a possibility – I rather suspect time was shoved into Territory because of the timezone aspect and also because it was simpler than devising a sensible API such as OS_Time. Problem is, this needs to be a separate module because time related services can be kept together in one place and that place is not within the kernel. There is a whole load of disparate junk in the kernel that should probably be elsewhere and this is nowhere truer than the hideous sprawling mess that is OS_Byte and OS_Word. To my mind, OS_Byte is somebody’s attempt at representing the Kowloon Walled City in binary. |
Chris Mahoney (1684) 2110 posts |
I think we’re talking about different things here :) The Territory Manager is indeed part of the base OS. I simply meant that individual territory definitions should not contain any compiled/interpreted code for defining timezone rules; it should be in a standard format that will be interpreted by the “new” Territory Manager. The current system of compiled territory modules is, in my opinion, not ideal.
I completely agree. |
David Feugey (2125) 2687 posts |
Correct. |
Steve Pampling (1551) 7952 posts |
I think the origin of that is the OS in ROM legacy. Much of what is in there is labelled as the kernel when in fact it has little or nothing to do with the base operation of the system and much or all to do with customisation of the behaviour of the system. It might be interesting to pick apart the whole setup to ascribe each element of the RISC OS build to HARDWARE, HAL, KERNEL/SYSTEM, APPLICATION or even extend the layers.
Legacy again. |
Steve Pampling (1551) 7952 posts |
Lack of clarity in the definition of layers in the OS – as it stands it’s basically “just stuff that’s there”. I’d say Territory, Country, Keyboard layout, Timezone are all Application layer. The kernel/system layer does not, and should not, care where in the world the system is located and what language the user is using. PS. Honestly, when you press the key labeled shift and then the fourth key along on the top row of the basic alpha-numeric group do you get £, #, or 3? In all those possibilities the system saw a specific physical key combination not the character you saw on the keycap |
Steffen Huber (91) 1945 posts |
DD/MM/YYYY date format…
Wikipedia says no such thing. It says that 3.3 billion use the order DMY. Obviously these are very different things. Just look at two DMY countries like India and Russia. DD-MM-YYYY amongst others like YYYYMMDD for India and dd.mm.yy(yy) for Russia. The vast amount of separation characters people have thought of is staggering. Not to mention the slight problem of the format that is defined as the countries’ standard vs. the format the people really use. |
Steve Pampling (1551) 7952 posts |
Wikipedia says many things, some have a basis in fact.(It’s getting better over the years but I still remain sceptical of the content) “The European Committee for Standardization (CEN) and European Committee for Electrotechnical Standardization (CENELEC) adopted ISO 8601 with EN 28601, now EN ISO 8601. As a European Norm, CEN and CENELEC member states are obligated to adopt the standard as national standard without alterations as well.” The salient point being that the format defined by ISO28601 is: Damn, I really dislike doing standard stuff. |
Rick Murray (539) 13422 posts |
Yeah. |
Steve Pampling (1551) 7952 posts |
If it helps you understand my viewpoint – I’m 5 foot 7 and I have no idea what that is in metric. |
Chris Evans (457) 1614 posts |
ISO 8601 is rather lax I feel, it allows for almost any or no separator character, what does seem to be 100% consistent is the order, with larger units (if present) always preceding smaller. |
Rick Murray (539) 13422 posts |
GIYF: http://www.uai.cl/images/sitio/biblioteca/citas/ISO_8601_2004en.pdf |
Rick Murray (539) 13422 posts |
169cm and about 68KG. No idea what that is in old fashioned measurements. ;-)
The internal is standard. UTC offset from …1900?… as a five byte value. Really the kernel only needs to know UTC and the adjustment for the current timezone. While the latter isn’t strictly necessary, it’s going to be more efficient then having to ask for every date operation. |
John Williams (567) 768 posts |
You seem taller in your postings! You (and Rick) need Chris Johnson’s UnitConv to get round these problems. |
Dave Higton (1515) 3409 posts |
I’ve started a topic in Aldershot for the arguments/discussions about units and ISO8601, etc. |
Rick Murray (539) 13422 posts |
Why? Knowing my size in feet/inches is about as useful as knowing that I am seventy three Mars bars tall… |
Chris Mahoney (1684) 2110 posts |
A topical example of what not to do: The game Final Fantasy XV was released today, and it features a tracking system to show the distance to your destination. The number format is tied to language; with the game text set to Japanese, it’s in metric. In English, it’s feet and miles. That’s absolutely not the correct behaviour. |