Citat:
degojs: Znam i baš zato sam i napisao ceo i taj poslednji pasus. Meni je čudno pošto MSDN jasno govori drugačije.. Ne znam baš da li bi se njemu slučajno omaklo da napiše "može ali i ne mora".. I pazi, nije Jesse jedini koji ima takav stav (npr. vidi
ovde.)
Danas naleteh slučajno na MSovo tumačenje "nepisanih pravila" verzioniranja, možda nekog interesuje:
The version components are used by convention as follows:
Major: Assemblies with the same name but different major versions are not interchangeable. This would be appropriate, for example, for a major rewrite of a product where backward compatibility cannot be assumed.
Minor: If the name and major number on two assemblies are the same, but the minor number is different, this indicates significant enhancement with the intention of backward compatibility. This would be appropriate, for example, on a point release of a product or a fully backward compatible new version of a product.
Build: A difference in build number represents a recompilation of the same source. This would be appropriate because of processor, platform, or compiler changes.
Revision: Assemblies with the same name, major, and minor version numbers but different revisions are intended to be fully interchangeable. This would be appropriate to fix a security hole in a previously released assembly.
Sloba je za 12 godina promenio antropološki kod srpskog naroda. On je od jednog naroda koji je bio veseo, pomalo površan, od jednog naroda koji je bio znatiželjan, koji je voleo da vidi, da putuje, da upozna,
od naroda koji je bio kosmopolitski napravio narod koji je namršten, mrzovoljan, sumnjicav, zaplašen, narod koji se stalno nešto žali, kome je stalno neko kriv… - Z.Đinđić
Re: Pozivanje non-static promenljivih koje cuvaju podatke iz druge klase
