text:
User:Immanuelle/sandbox/History of Shinto Shrines in Hokkaido

This article provides an overview of Hokkaidō 's Shinto shrine and shrine administration, mainly from a historical perspective.

Like the History of Shinto Shrines in Okinawa it is relatively short compared to the History of Shinto in mainland Japan. So the establishment of shrines is much more recent than in other areas, yet it is firmly established making it a useful case study for the future Overseas Shinto, unlike the more colonial shrines of the Empire of Japan.

Before Shinbutsu bunri in the Meiji era, Shinto and Buddhism were Shinbutsu-shūgō, and it is not possible to clearly distinguish between Buddhist temple and shrines among the older temples and shrines. For example, many of the shrines now called Itsukushima Shrine were originally called Buddhist Benzaiten or Bentensha. The Waniguchi or bell of Wakizawayama Shrine, which will be described later, is engraved with an inscription referring to Pure Land Buddhism.

Here, shrines are those that existed after the separation of Shinto and Buddhism, and those that existed before the separation of Shinto and Buddhism are also referred to as "shrines."

It culminated in the development of the modern History of Shinto shrines in Hokkaido separate from the Association of Shinto Shrines.

Hokkaido, Matsumae and Ezo
From the Sengoku Sengoku period through to Edo period, a territory ruled by Japanese people ( the Matsumae Domain ) was established in southern Hokkaido. From a historical perspective, there is also a view that Hokkaido should be divided into " Matsumae-chi ( Wajin-chi, Kuchi-Ezo, Kyu-kaichi)" and " Ezo-chi (Oku-Ezo, Shin-kaichi)". Although this way of dividing Hokkaido into regions is not widely accepted, it is useful for getting an overview of Hokkaido's history. Because the area controlled by the Matsumae clan changed significantly over time, care must be taken to determine exactly what is meant by "Matsumae territory," but here "Matsumae territory" generally refers to the Wajin area in southern Hokkaido, and the rest of the area is referred to in the narrow sense as "Ezo territory."

Hokkaido's cool climate makes it unsuitable for rice cultivation, so the Matsumae clan based its fiefdom mainly on income from seafood instead of the rice-based kokudaka system. This was done through trade with Ainu people, and trading posts called "basho" were established along the coast of Hokkaido. In the mid-Edo period, the system of monopolizing trade areas was institutionalized, whereby merchants could monopolize a certain location to conduct trade. Through these efforts, Japanese settlements began to appear in Ezo (in the narrow sense), and shrines were established in various places.

In the latter half of the Edo period, the shogunate attempted to take Tenryō in response to Russian Empire 's Territorial evolution of Russia. For this reason, the boundaries of the Matsumae Domain's territories, the Shogunate's territories, and Ezo (in the narrow sense) were frequently changed in the 19th century. During this period, samurai groups were dispatched to various parts of Hokkaido to guard Ezo, and they founded shrines.

During the Meiji period, pioneers began to settle in various parts of Hokkaido and built shrines. In time, these shrines were systematized from the perspective of State Shinto.

overview
It is believed that shrines were established by the Wajin in southern Hokkaido (formerly Wajin territory, formerly Kaichi) at the latest in the Middle Ages.

Many of these shrines were concentrated in fishing bases in southern Hokkaido, and were Shinbutsu-shūgō of Shinto and Vajrayana, with mountain worship and cape worship taking center stage. These shrines had their own unique culture, symbolized by the Matsumae Kagura dance, which distinguished them from the new shrines that were built during the later Hokkaido development period.

The early days
It is not clear when the Japanese first arrived in Ezo, but there are many ancient shrines along the southern coast of Hokkaido whose founding dates are unknown. One older theory is that remnants of Northern Fujiwara traveled to Oshima during Heian period and established a shrine there, but it is now widely believed that the shrine was built during Kamakura period or at the latest Muromachi period.

Below is a list of what are believed to be the oldest shrines in Hokkaido.

 * Ohi Shrine (Ooi) Former Dainichi Hall . A shrine located in Hokuto, Hokkaido in southern Hokkaido. It is known as the site of a fierce battle during the Battle of Hakodate. It has Waniguchi with the inscription " Kōhei Sansai (1060)" from the Heian period. There is a record that it was rebuilt in Meireki, but the exact date of its construction is unknown. If it was founded in 1060, it would be the oldest shrine in Hokkaido. However, some believe that this bell was made later, as its shape matches those of the late Edo period.
 * Funatama Shrine: A shrine located in Hakodate, southern Hokkaido. The Hōen Jichi Kenkoroku, a book written by Ichikawa Jūrō, a Shogunate official who explored Ezo during the late Edo period, reports that the temple was founded in 1135.
 * Katta Shrine in Noboribetsu, central Hokkaido.
 * Ubagami Daijingū is a shrine in Esashi, Hokkaido (Hiyama), southern Hokkaidō . According to the shrine's history, it was founded in 1216. There is a theory that it is of Ainu origin, in which case, although its age is unknown, it would be the oldest shrine in Ezo.
 * Wakumoto Shrine: A shrine in Shiriuchi, Hokkaido, Oshima, southern Hokkaido. It is said to have been in 1239. Gold dust can be found in the nearby Shiriuchi River.
 * Raiko Shrine: A shrine located in Shiriuchi, Hokkaido, Oshima, southern Hokkaido. It is said to have been founded in Kangen . The Toei Dochūki written by Mogami Tokunai states that there was a Waniguchi with an inscription dating from 1405. It is believed to be the oldest shrine in Hokkaido. Although it is not a shrine, there is also Onsen Yakushido in Chiuchi Town, which has a crocodile bell from the same year.
 * Wakizawayama Shrine: A shrine located in Hakodate, southern Hokkaido. It has a bell with the inscription dated Eikyō 11 (1439 or 1440). The village history of the former Ishizaki village states that it was founded in 1429. Wakizawayama Shrine fell into disuse during the Kansei era (late 18th century), but in Bunka 10 (1813 or 1814), the bell was discovered buried underground and donated to (Ishizaki) Hachiman Shrine in Kameo village, where it was displayed in front of the shrine. During Emperor Meiji pilgrimage in 1876, it was displayed as the oldest crocodile bell in Hokkaido. It is considered conclusive evidence that shrines existed in Ezo at least as early as the mid-15th century. It is currently owned by the Hakodate Museum as a cultural property designated by Hokkaido. ( Agency for Cultural Affairs/Cultural Heritage Online )
 * Sunatate Shrine: A shrine in Kaminokuni, Hokkaido, Hiyama, southern Hokkaido. In the summer of 1462, Kanshō Takeda Nobuhiro built a Vaishravana Hall in his castle, and renamed it Sunatate Shrine during the separation of Shinto and Buddhism in the Meiji era. It is mentioned in historical documents from the early modern period, such as " Kan'ei Shoka Keizuden " and " Shinra no Kiroku ."
 * Kaminokuni Hachiman Shrine: A shrine in Kaminokuni Town. In 1473, Takeda Nobuhiro, the founder of the Matsumae clan, established the shrine as a guardian deity at Katsuyama Date (now the site of Katsuyama Date, a nationally designated historic site), and named it Tategami (Tategami Hachiman Shrine). It is one of the Kaminokuni Sansha (along with Iozan Shrine and Sunatate Shrine, known as the Kaminokuni Sansha) The Genroku hall was built in 1699 and is one of the oldest shrine buildings still standing in Hokkaido.
 * Yaburai Tenmangu Shrine: A shrine in Hokuto City. The shrine is located on the site of Shige Bekkan, one of the Twelve Garrisons of Southern Hokkaido . It is said to have been built by Andō Morisue, who was defeated by Nanbu clan in 1443. There are many legends, including that it began as a shrine to the statue of Sugawara no Michizane, the deity who washed up on the Yabuki Coast in the 15th century.
 * Ōta Shrine (Setana): It is said to have been founded during the Kakitsu era (1441-1443). One of the five great sacred sites in southern Hokkaido. Its buildings are scattered over the steep mountainside overlooking the Sea of Japan.
 * Yamanoue Daijingū shrine is a shrine located in Hakodate, southern Hokkaido. It began during Ōan era (1368-1375) when a mountain ascetic named Fujibo enshrined a branch of the Ise Grand Shrine in Kameda Akagawa Village, which is now on the outskirts of Hakodate City.
 * Kameda Hachiman Shrine: A shrine located in Hakodate, southern Hokkaido . It is said that in 1390, Meitoku Kaga no Kami Moriyuki enshrined the Hachiman deity from Kehi Shrine, but there are various theories about the founding year, and it may have been built at the end of the Muromachi period.
 * Hakodate Hachiman Shrine: A shrine located in Hakodate, in southern Hokkaido. It is said that it began in Bun'an, when Kono Masamichi, the lord of Kameda County, built a castle in Motomachi, Hakodate, and enshrined Hachiman as the guardian deity of the castle in the southeastern corner of the castle grounds. It is a Sōja shrine that consolidates the kami of all other Hokkaido Shrines.
 * Ishizaki Hachiman Shrine: A shrine located in Hakodate, southern Hokkaido. The date of construction is unknown. It is said that the village began during Eikyō era (1429-1441) when the village's founder, Taira no Moriami, had deep reverence for the deity enshrined at Hachiman Shrine and performed the rituals there.
 * Sumiyoshi Shrine: A shrine located in Hakodate, southern Hokkaido. The date of its founding is unknown, but oral tradition holds that it was during the Kamakura period. It was rebuilt during An'ei era.
 * Tsukizaki Shrine: A shrine in Fukushima Town. The date of construction is unknown. There is a record that it was rebuilt in Meiō.
 * Tokuyama Daijingu: Shrine in Matsumae Town. The date of construction is unknown. In 1582, the feudal lord Kakizaki Tokihiro moved the shrine to Kuramachi and changed its name from Ise-do to Shinmei-sha.

Yakata Shrine and Hachiman Shrine
In theory, Ezo was under the jurisdiction of Ando clan, but in reality, various powerful clans had settled there and built castles (fortresses) there. They built a shrine in the mansion and called it the mansion god(館神, Tategami). At the castle, the war god Hachiman is enshrined. There are many such shrines in southern Hokkaido.

From the middle of the Edo period, Russian involvement in Ezo became a concern for the shogunate. The shogunate established Ongoku-bugyō as Tenryō, and ordered the various feudal domains in the Tohoku region to guard the area. Thus, the shrines built by the guard samurai who arrived in various remote areas of Hokkaido enshrined Hachiman as a war god, and later became Hachiman Shrines.

Shrine dedicated to Sea gods
Among the Japanese who traveled to Ezo from early on in search of seafood, some set up Watchtower along the coast and some even settled there. In the mid-Edo period, Matsumae domain institutionalized the bashoukeoisei and bashoukeoisei. Along the coast, mainly in southern Hokkaido, there are shrines dedicated to the gods of the sea and water, as well as gods and Buddhas of fishing and commerce. These shrines are thought to have developed from spontaneously growing smaller shrines rather than being the result of the transfer or incorporation of a spirit from another shrine.

The main ones are: Ebisu, Kotohira shrines, Benzaiten, Itsukushima Shrine, and Watatsumi.

Inari Shrine, God of Agriculture
The shogunate, wary of Russia, handed over part of Hokkaido to the shogunate in 1799 and began to Tenryō. At this time, rice cultivation also began to be attempted in Hokkaido. This project fell into disuse due to cool weather and poor harvests, but was resumed during the Ansei era (1854-1859) with some success. From the mid-Meiji period period onwards, rice cultivation was successful in the Ishikari and Iburi regions as well.

Furthermore, there was immigration from the Kansei and Bunka (late 18th century to early 19th century), with a particular increase in immigrants fleeing Tenpō famine during Tenpō (1830-1844).

Inari shrines were built by these agricultural immigrants, and many were built throughout southern and central Hokkaido.

Matsumae Domain
The Matsumae Domain was established in southern Hokkaido by the Kakizaki clan, who rose to prominence among the powerful clans. Founded by Kakizaki Tokihiro in 1582, Shinmei shrines was merged with many smaller shrines in the surrounding area to become Tokuyama Daijingu during the Meiji period. The Matsumae domain established a temple and shrine magistrate office to control religion. During the Edo period, Japanese people began to enter various parts Ezo through the Matsumae domain, and even excluding the area around Matsumae castle, there were 140 shrines and temples in Ezo.

Institutionalization of the Shinto Priesthood and the Shiratori Clan
In the Matsumae region, ascetic monks and other practitioners have been living since the Middle Ages, and the priesthood has been passed down hereditarily. At Fukuyama Castle, a Shinmei Shrine (later known as Matsumae Hachiman Shrine) was built to protect the castle, and its chief priests took the name " Shiratori " for generations. The Shiratori family was appointed as the head shrine priest of the Matsumae domain, and through the, who were the Shinto priests, they obtained an official position in the Imperial Court and became the head of the Shinto priests in the Matsumae region. There are few surviving historical documents related to the Shiratori family, but the Shiratori Family Diary, written by successive chief priests, describes events from 1788 to 1862. The most influential shrines in the Matsumae castle town, including Shinmei Shrine, were collectively known as the "Seven Matsumae Shrines." The Seven Matsumae Shrines are also depicted in the Matsumae Esashi Screen, which was painted during the Horeki era.

In Matsumae, under the leadership of the Shiratori clan, priests and rituals were organized, and a system of rituals, represented by Matsumae Kagura, was institutionalized. On the other hand, shrines to sea and water gods that appeared "spontaneously " in various parts of Ezo were outside of this system.

Matsumae Kagura
Matsumae Kagura is a kind of Kagura dance done in southern Hokkaido. It is customarily performed at the end of rituals at shrines in southern Hokkaido and is essential for the priests of Matsumae. It has more of a religious ritual character than a dengaku dance.

Its origin is unclear, but according to legend it was first performed in 1662 during the Kanbun (era) It was protected by Enpō feudal lords of the Matsumae domain, and in 1681 the Matsumae domain created a set of rules for the great religious rites.

In the Hiyama region it was also called "Esashi Kagura" and in the Shiribeshi region it was called "Oshima Kagura," but today it is generally referred to as "Matsumae Kagura". It has been designated as an intangible cultural property of Hokkaido.

Meiji Period
When Meiji period Higashikuze Michitomi, who was appointed as List of governors of Hokkaido Prefecture in September 1869, traveled to Hokkaido, Emperor Meiji ordered Kunitama, Ōkuninushi, and Sukunabikona to be enshrined there as Kunitama. A Hokkaido shrine ceremony was held, and a three-sided shinto mirror was entrusted to Higashikuze Michiyoshi by Daijō-kan.

It was Shima Yoshitake who was actually appointed to Sapporo as Higashikuze Michitomi's representative, and it was Shima who came up with the plan to establish Kaitaku Shinchosaisha (present-day Hokkaido Shrine). Although Shima was soon dismissed, the construction of the new shrine proceeded largely according to Shima's plan, and the shrine was renamed Hokkaidō Shrine and Sengū in 1871. The Hokkaido Development Commission announced that June 15th would be the annual festival day, and that all residents of Hokkaido were to take time off work on that day to visit and pay homage to the shrine. (For details, see Hokkaidō Shrine#History .)

In 1873, Sapporo Shrine was elevated to the rank of Modern system of ranked Shinto shrines and a branch of the Office of Japanese Classics Research was established there, making it the State Shinto in Hokkaido. This is the first shrine in Hokkaido to be dedicated to the national anthem. Shrines before this time were established by samurai and local residents for their own religious beliefs, and in this respect they are distinguished. The founding of Sapporo Shrine in the new Hokkaido region later served as a model for overseas shrines in Taiwan, Sakhalin, and the Korean Peninsula.

Settler Shrines
During the Meiji period, settlement in various parts of Hokkaido was encouraged, and group settlements of several dozen households, sometimes exceeding a hundred, were actively undertaken from villages all over the country. Many of them built shrines in their hometowns to worship their ancestral spirits and local deities in the places they immigrated to.
 * Ebetsu shrine (Ebetsu) - Settlers from Kumamoto Prefecture enshrined Katō Kiyomasa.
 * Iyahiko Shrine ( Sapporo ) - Settlers from Niigata Prefecture enshrined a branch of Yahiko Shrine.
 * Maeda Shrine ( Kyōwa, Hokkaido ) - Former Kaga samurai who settled here enshrined Maeda Toshiie.

God of the Mines
Gold dust mining has been carried out in Hokkaido since the Middle Ages, and when development began, mines were established in various places. In particular, countless coal mines were developed in the Sorachi region, and shrines were established to worship Ōyamatsumi as the god of these coal mines. Horonai Shrine, founded in 1880, is considered to be the first of these.

Shinmei and the Three Deities of Development
In areas where people from different hometowns gathered together, or when shrines were merged due to the shrine reforms described below, the Shinto god Amaterasu came to be worshiped as the goddess that oversaw all the deities. When Sapporo Shrine began to worship the Three Deities of Development, other shrines seeking new official recognition followed suit and began to worship the Three Deities of Development as their new chief deities. Generally, it was forbidden to send a branch of a deity from a government-sponsored shrine, but in the case of Sapporo Shrine alone, a branch was permitted as a "special deity," and the three pioneering gods came to be enshrined in the newly developed area.

Hokkaido Shrine Reform
When Modern system of ranked Shinto shrines was established in 1871, Hokkaido also began investigating shrines within the prefecture in accordance with this system, and separated Shinto and Buddhism, and carried out consolidation and abolition. This is called the Hokkaido Shrine Reform. At the time, most of Hokkaido was undeveloped, and the shrine reform was mainly carried out in the southern part of the island. In 1875, the Shrine Reform Act began, which led to the official recognition of shrines and determined the status of Modern system of ranked Shinto shrines and Modern system of ranked Shinto shrines.

The number of shrines in Hokkaido was distributed with 370 shrines in Hakodate Prefecture, 150 shrines in Sapporo Prefecture, and 32 shrines in Nemuro Prefecture. This meant that two-thirds of all the shrines in Hokkaido were concentrated in southern Hokkaido. However, out of the 370 shrines in Hakodate Prefecture, 203 were unofficial "miscellaneous shrines," whereas Sapporo Prefecture had 36 unofficial shrines out of its 150. Many of these small shrines in southern Hokkaido were significantly reduced later through consolidation.

The certification of shrine status at that time generally followed the following trend:

 * Gosha - Major shrines built in fishing villages in the early modern period (49 shrines)
 * Village shrines - Central shrines built in various regions from the end of the Edo period to the beginning of the Meiji period (231 shrines)

Shigemasa Kikuchi
A person who played a major role in the reform of Hokkaido Shrine was Kikuchi Shigetaka, who was the de facto first chief priest of Sapporo Shrine.

Kikuchi Shigetaka was originally from the and was adopted as the chief priest of Hakodate Hachiman Shrine. When Hakodate was transferred from the Matsumae Domain to the Tokugawa shogunate, Kikuchi Shigetaka began to claim that Hakodate Hachiman Shrine was the main shrine of Hakodate. During the Battle of Hakodate, he cooperated with the government forces, organized a reserve army, and achieved success. He received a medal and gained a foothold in the new government's shrine policy in Hokkaido. He also succeeded in breaking away from the old system of the Matsumae Domain and the Shiratori family.

Kikuchi Shigetaka became a Shinto priest and a member of the Hokkaido Development Commission, and was also appointed as a priest at Sapporo Shrine. He went to Tokyo and negotiated with the Ministry of Shinto Affairs regarding the overall administration of shrines in Hokkaido, and the reform of Hokkaido shrines in the early Meiji period was carried out under Kikuchi's guidance. Among these, Hakodate Hachiman Shrine was promoted to a prefectural shrine, while many shrines in southern Hokkaido were merged or closed.

Southern Hokkaido
In Matsumae in 1868, shrines that combined Shinto and Buddhist practices, such as Shogun Jizo and Oshima Daimyojin, were disposed of. After 1871, in southern Hokkaido, where there were many old and syncretic temples and shrines, the removal of Buddhist statues and the renaming of shrines and deities was actively carried out based on Shinbutsu bunri. However, this did not lead to the uproar of Haibutsu Kishaku ) that occurred in the mainland. In Esashi, Buddhist statues at shrines were burned and small shrines with unclear origins were abandoned, but no major disturbances occurred.

The southern Hokkaido region, home to many ancient shrines, was the first in Hokkaido to have local shrines and village shrines designated as such. However, as the process of designating shrines across Hokkaido progressed, the consistency of the designation of shrines in the southern Hokkaido region began to become an issue, with village shrines having more parishioners than local shrines. As a result, in 1875, the status classification of local and village shrines under the Hakodate branch office was revised. It was decided that shrines in areas with a branch office of the Hokkaido Prefectural Government, a large port, or well-maintained shrine buildings would be designated as gosha, while all other shrines would be classified as murasha. The status of shrines in southern Hokkaido was finally determined in October 1876. The status of Hakodate Hachiman Shrine, which had called itself the "chief guardian deity" since the Edo period and which the Hokkaido Development Commission had treated as a "venerated shrine," also needed to be reviewed. For the time being, it was made into a prefectural shrine, and in 1877 it was made into a national shrine.

In Hokkaido, the compilation of shrine details was delayed due to geographical reasons. It was not until 1879 that a detailed list of shrines throughout the prefecture was finally completed. However, there were many small Mugan shrines that were not included in this list.

The number of shrines continued to increase throughout Hokkaido, but in southern Hokkaido the number has decreased due to consolidation. For example, in the ten years between 1906 (Meiji 39) and 1916 (Taisho 5), the number of officially recognized shrines in the Hakodate branch office decreased from 167 to 107. During the same period, the number of companies in Hiyama Subprefecture decreased from 141 to 42. Many of these were unranked shrines or village shrines. Outside of southern Hokkaido, for example in the Sorachi region, the number of companies has actually increased from 19 to 33.

The uniqueness of Hokkaido
Nationwide, the total number of shrines was halved between the Meiji and Showa periods, but in Hokkaido, it actually increased.

Pioneer immigrants and the proliferation of Muga Shrines
In 1885, the Shrine and Temple Military Affairs Section was established within the Hokkaido Prefectural Government Office and was put in charge of shrine administration.

Immigrants came to Hokkaido from all over Japan, but in many cases they settled in groups based on their place of origin. They tended to worship the local deities of their hometowns in the newly developed lands, and even today in Hokkaido shrines originating from various regions can be seen all over the country. Furthermore, in areas where people from different regions settled, they established shrines to worship the Shinmei shrines Amaterasu, as well as shrines to worship the three pioneering gods, whose spirits were divided from Sapporo Shrine. When people first settled in the wilderness, they built simple shrines by placing a Shinto altar on the stump of a large felled tree, erecting a pole with the name of the enshrined deity inscribed on it, and setting up a simple Torii. These were sometimes called "Stump Shrines" or "Pole Shrines".

Such unofficial shrines were called " Mugajinja" (Mugan Shrines ). The proliferation of Mugan Shrines was completely contrary to the national policy of merging and abolishing small shrines to build a system of prestigious shrines. However, at the frontier of the settlement, it often took several days to travel to an officially recognized shrine, and settlers who worked with their entire families to settle in the area could not afford to be away for several days to make a visit. As a result, in Hokkaido, rather than reducing the number of small shrines, there was a constant stream of proposals to establish new shrines in various places. Taking these circumstances into consideration, the Hokkaido Prefectural Government did not crack down much on Mugan Shrine.

Hokkaido Prefectural Government's Shrine Administration
In 1891, the authority to officially recognize shrines was transferred from Home Ministry Shrine Bureau to the Hokkaido Prefectural Government. Until then, permission had to be obtained from the Ministry of Home Affairs each time, but now Hokkaido was able to decide how to handle shrines. This was something special that was limited to Hokkaido in the whole country.

In 1897, a new Modern system of ranked Shinto shrines was established below village shrines and the standards for official recognition were relaxed. For this reason, there are many temples and shrines in Hokkaido that were "officially recognized" and "founded" between the 1880s and 1897s. In 1901, the " Principle of one shrine per town and village " was established, and in the following year, in 1902, the "Regulations for Shrines and Temples" were established, laying out the standards for officially recognized shrines.

One shrine in each village
The shrine located in the center of each town or village is designated as an officially recognized shrine. The other shrines were left as unofficial shrines and were to be worshiped by local priests.

Based on the policy of one shrine per town and village, unofficial shrines in various locations also began to appoint priests. By the end of the Meiji period, the number had increased to about 550 shrines and 100 people, and the Hokkaido Association of Shinto Priests was organized.

Temple and shrine regulations
The February 1902 (Meiji 35) regulations for shrines and temples stipulated the following criteria for official recognition :

 * Temple grounds - over 1000m2
 * Shrine - 20 sqm or more
 * Permanent capital - 500 yen
 * Or the actual income from the real estate owned is 75 yen or more per year
 * Number of believers - 100 or more parishioners or 300 or more believers

These standards served as a guideline for the development of new Mugabe shrines across the country in order to make them official shrines. In 1906, the government issued guidelines entitled "Regarding the Abolition and Merger of Shrines, Temples, and Buddhist Halls", instructing areas without officially recognized shrines to reorganize non-recognized shrines and meet the requirements for official recognition. The maintenance of shrine grounds, shrine buildings, and property, as well as the number of parishioners and believers, were required to be at a level appropriate to the shrine's rank, and heads of households, towns, and villages were required to visit shrines in each area to check this.

As a result of these factors, the number of shrines in Hokkaido had decreased by about 30% by the early Taisho period. However, the reductions were mostly in the southern Hokkaido region, with a decrease of 159 shrines in southern Hokkaido alone, compared to a decrease of 161 shrines in Hokkaido as a whole. (There have been new shrines added, so it's not the case that only two shrines have been lost outside of southern Hokkaido.)

The system of offerings to the gods
In 1906, the system of providing sacred offerings was introduced. This is a system whereby public funds are disbursed to shrines designated by the prefectural governor on the occasion of shrine festivals. Funds for official and national shrines came from the national treasury, while funds for prefectural and village shrines came from local governments. In Hokkaido, prefectural shrines received donations from the Hokkaido local budget, while local shrines received contributions from wards and towns and villages. In 1906, 10 yen was paid to prefectural shrines, 7 yen to township shrines, and 5 yen to village shrines. This was not automatically paid to all town and village shrines; even among those ranked as town or village shrines, some received public funds and some did not. For example, in Hokkaido in 1916, the percentage of shrines to which public funds were actually spent was prefectural shrines (100%), local shrines (60%), and village shrines (28%). In the case of Sapporo Shrine (a Kanpei Taisha shrine), the donation in 1925 was 3,283 yen.

Taisho period
As the Taisho era began and development work progressed to a certain extent, it was thought that Hokkaido's unique characteristics had subsided. In response to this, shrine regulations, which previously applied to all prefectures across the country, were revised to include Hokkaido. The Hokkaido Shrine Regulations were established as detailed rules for the shrine.

Strengthening state control
In 1937, the Hokkaido Association of Shinto Priests developed into the Hokkaido Shrine Association (different from the Hokkaido Shrine Association described below). As the wartime system was further strengthened and the Dai-Nippon Shinto Association was established, the temple became its Hokkaido branch in 1942.

The shrine has been used to pray for long-lasting military fortune and to promote national prestige, but in 1943, as the war situation worsened, an air-raid shelter was constructed within the shrine grounds.

National and Imperial Shrines
In 1945, the Hokkaido Prefectural Government established a policy to designate Kamikawa Shrine (Asahikawa City), Sumiyoshi Shrine (Otaru City), and Hachiman Shrine (Muroran City) as national shrines. However, the end of the war meant this was not possible.

Gokoku Shrine
After the Boshin War, Gokoku Shrines were built all over the country to honor those who died in war. In particular, shrines where rituals are held at government expense, such as those held by the Ministry of War, are called Kansai Shokonsha, and in Hokkaido, the Shokonsha in Hakodate, Matsumae, and Esashi are examples of this. On the other hand, shrines where rituals are held at private expense are called private shrines, and the shrines in Asahikawa and Sapporo are examples of this type.

In 1939, all Shokonsha shrines across the country were renamed Gokoku Shrines. Generally, Gokoku shrines are funded with government funds and one shrine is set up for each prefecture, but because Hokkaido is so large, three shrines are designated as an exception. Hokkaido Gokoku Shrine, Sapporo Gokoku Shrine, and Hakodate Gokoku Shrine were designated as Gokoku Shrines equivalent to prefectural shrines. On the other hand, Matsumae (Fukuyama) Gokoku Shrine and Esashi Gokoku Shrine, which are equivalent to village shrines, became non-designated Gokoku Shrines.

When State Shinto was dismantled by the Shinto Directive of Supreme Commander for the Allied Powers, shrines throughout the country organized themselves into a new religious organization, the Association of Shinto Shrines. The Hokkaido Shrine Association was also formed in Hokkaido. Shrines in southern Hokkaido have also organized the Hokkaido Shrine Association.

Postwar
Among the officially recognized shrines, those that do not belong to these groups are called independent shrines. In addition, most of the shrines are unofficial shrines. According to the 1999 Hokkaido Shrine Association Journal, the number of shrines in each area is as follows:

 * Hokkaido Shrine Association 604 shrines
 * Hokkaido Shrine Association 61 companies
 * 69 independent companies
 * Unofficial Shrines 1925
 * *This does not include shrines in the Kuril Islands or Sakhalin.

Hokkaido Jinja-chō
In 1946, following the Shinto Directive, the Dai Nippon Shinto Association was dissolved. As a result, the traditional shrine status was abolished and each shrine was to become an individual religious organization with no hierarchy of superiority or inferiority. However, shrines concerned about the disruption of the traditional order in the Shinto world came together and founded Association of Shinto Shrines. Most of the shrines that had previously belonged to the Dai Nippon Shinto Shrine Association participated in this event. In Hokkaido, the Hokkaido Shrine Association was initially organized by 539 shrines, and currently has approximately 600 affiliated companies, accounting for 80% of the Shinto religious corporations in Hokkaido.

Hokkaido Jinja Kyōkai
The shrines in the southern Hokkaido region, especially on Oshima Island, which were originally different in nature from the shrines in the newly developed areas established by settlers, did not join the Hokkaido Shrine Association. Records from that time gave the following reasons:

 * Even if an organization were created that covered the entire Hokkaido prefecture, it would be difficult to gather everyone together to hold a meeting.
 * It is inconvenient to contact the central government via the Sapporo branch. At the time, travel to and from Tokyo was by boat and train, and it seemed completely illogical to travel from Hakodate, at the southern tip of Hokkaido, to Sapporo, and then via Hakodate again on the way to Tokyo.
 * In any case, it would be necessary to establish a branch in southern Hokkaido as well, which would require a burden on three organizations: the Association of Shinto Shrines, the Hokkaido Shinto Shrine Association, and the Southern Hokkaido Branch of the Association of Shinto Shrines. However, if the southern Hokkaido branch were to become independent, only two would be necessary.

.

Shrines in southern Hokkaido (mainly those in the Oshima region) do not join the Hokkaido Shrine Council, but instead established their own organization, the Hokkaido Shrine Association. As of 2006, 61 shrines are members.

Separation of Church and State
In 1964, Sapporo Shrine was renamed Hokkaido Shrine when Emperor Meiji was enshrined there. The annual festival on June 15th was held as the Sapporo Festival, but in the 1960s, there was a movement to question the donations collected from neighborhood associations in the city for the Hokkaido Shrine festival, as they were considered to be essentially compulsory.

On the annual holiday of June 15th, public schools in Sapporo were closed or only held half-day classes as the Sapporo Festival was held. Some people objected to this from the perspective of separation of church and state. June 15th is still considered Hometown Day, and public schools have a half-day school day today.

In 2010, the ruling in the Sunagawa separation of church and state lawsuit was made, attracting much attention.

Other websites

 * Hokkaido Shrine Association website
 * Hokkaido Shrine | Sapporo Festival


text:
User talk:76.67.81.213

June 2024
MathXplore (discuss • contribs) 14:42, 25 June 2024 (UTC)

license: Creative Commons - Attribution Share-Alike - https://creativecommons.org/licenses/by-sa/4.0/

title: User talk:76.67.81.213


text:
User talk:152.172.1.73

Welcome to Wikibooks!
Hello, and welcome to Wikibooks! Thank you for your contributions so far. I hope you like the place and decide to stay.

You don't have to log in to read or edit articles on Wikibooks, but if you wish to acquire additional privileges, you can simply  [ create a named account] . It's free, requires no personal information, and lets you:
 * Create new pages and rename pages
 * Edit semi-protected pages
 * Upload images
 * Have your own watchlist, which shows when articles you are interested in have changed.

If you edit without using a named account, your (152.172.1.73) is used to identify you instead.

By the way, please make sure to sign and date your talk page comments with four tildes (~~~~).

Happy editing! Cremastra (discuss • contribs) 15:08, 25 June 2024 (UTC)

title: User talk:152.172.1.73


text:
User talk:ToadetteEdit

Welcome!
Welcome, ToadetteEdit!

If you have any questions, you can ask in the assistance reading room or possibly contact me personally. Cremastra (discuss • contribs) 15:10, 25 June 2024 (UTC)

title: User talk:ToadetteEdit


text:
User:Chulumanco Ngceshe

crazy inlove with 14'03. 🥺🥺🥺❤

title: User:Chulumanco Ngceshe


text: Category:Dulce de leche recipes

title: Category:Dulce de leche recipes


text:
User talk:103.246.193.34

June 2024
MathXplore (discuss • contribs) 01:49, 26 June 2024 (UTC)

title: User talk:103.246.193.34


text:
User:Dirk Hünniger/apache

= Introduction =

= Architecture =

= Installation =

= Configuration =

= Virtual hosting =

= SSL =

= .htaccess =

= Security =

= CGI =

title: User:Dirk Hünniger/apache


text:
User:Dirk Hünniger/Computer Science Design Patterns

= Abstract Factory =

= Adapter =

= Bridge =

= Builder =

= Chain of responsibility =

= Command =

= Composite =

= Decorator =

= Facade =

= Factory method =

= Flyweight =

= Interpreter =

= Iterator =

= Mediator =

= Memento =

= Model–view–controller =

= Observer =

= Prototype =

= Proxy =

= Singleton =

= State =

= Strategy =

= Template method =

= Visitor =

= Development stages =


text:
User talk:79.139.141.129

Welcome!
Welcome, 79.139.141.129!

If you have any questions, you can ask in the assistance reading room or possibly contact me personally. Cremastra (discuss • contribs) 17:26, 26 June 2024 (UTC)

title: User talk:79.139.141.129


text:
User talk:71.182.144.226

Your edits are obviously vandalism
Cremastra (discuss • contribs) 20:42, 26 June 2024 (UTC)

title: User talk:71.182.144.226


text:
Template:1.0

background:#ff5555

title: Template:1.0


text:
Template:1.0.1

background:#ff7c57

title: Template:1.0.1


text:
Template:1.1

background:#ffa25a

title: Template:1.1


text:
Template:2.0

background:#ffc65d

title: Template:2.0


text:
Template:2.1

background:#ffea60

title: Template:2.1


text:
Template:3.0

background:#f1ff63

title: Template:3.0


text:
Template:3.1

background:#d0ff66

title: Template:3.1


text:
Template:3.2

background:#b1ff69

title: Template:3.2


text:
Template:4.0

background:#92ff6c

title: Template:4.0


text:
Template:4.1

background:#75ff6f

title: Template:4.1


text:
Template:5.0

background:#72ff8a

title: Template:5.0


text:
Template:5.1

background:#75ffab

title: Template:5.1


text:
Template:5.2

background:#78ffca

title: Template:5.2


text:
Template:6.0

background:#7bffe8

title: Template:6.0


text:
Template:6.1

background:#7ef9ff

title: Template:6.1


text:
Template:6.2

background:#81deff

title: Template:6.2


text:
Template:6.3

background:#84c4ff

title: Template:6.3


text:
Template:7.0

background:#87abff

title: Template:7.0


text:
Template:8.0

background:#8a94ff

title: Template:8.0


text:
Template:9.0

background:#9c8dff

title: Template:9.0


text:
Template:10.0

background:#b690ff

title: Template:10.0


text:
Template:11.0

background:#d093ff

title: Template:11.0


text:
Template:12.0

background:#e896ff

title: Template:12.0


text:
Template:12.1

background:#ff99ff

title: Template:12.1


text:
Template:13.0

background:#ffb0ff

title: Template:13.0


text:
Template:14.0

background:#ffc0e0

title: Template:14.0


text:
Template:15.0

background:#ffc0c0

title: Template:15.0


text:
Template:15.1

background:#ffd0c0

title: Template:15.1


text:
Template:Pua

background:#ffffff

title: Template:Pua


text:
Template:Sur

background:#bbbbbb

title: Template:Sur


text:
Template:Res

background:#777777

title: Template:Res


text:
Template:Nch

background:#000000

title: Template:Nch


text:
User talk:174.240.177.75

June 2024
MathXplore (discuss • contribs) 00:28, 27 June 2024 (UTC)

title: User talk:174.240.177.75


text:
User talk:中文人

June 2024
MathXplore (discuss • contribs) 02:34, 27 June 2024 (UTC)

title: User talk:中文人


text:
Cookbook:Honey Mug Cake

| Desserts

A quick and easy honey mug cake made in the microwave.

Ingredients

 * 2 tbsp honey
 * 4 tbsp all-purpose flour
 * ½ tsp baking powder
 * ½ tsp yeast
 * 1–2 tbsp freshly squeezed lemon juice (optional)
 * Lemon zest (optional)

Optional toppings

 * Whipped cream
 * Berries
 * Ice cream
 * Honey
 * Maple syrup

Equipment

 * Small bowl
 * Mixing spoon
 * Microwave-safe mug
 * Microwave
 * Toothpick

Procedure

 * 1) Combine the flour, yeast, and baking powder in a bowl.
 * 2) Add honey, and mix until incorporated.
 * 3) Add a small amount of water, and until incorporated.
 * 4) Add lemon juice and zest, and mix until the batter is smooth.
 * 5) Pour the batter into a mug, and microwave for 60–90 seconds. To check if it's thoroughly cooked through, stick a toothpick in; if it comes out clean, it is ready.
 * 6) Serve with any of the optional toppings.

Notes,tips and variations

 * You can adjust the batter to your liking—no need to follow the measurements.
 * You do not need to microwave the batter in a mug—any microwave-safe container will do.
 * This recipe is easily adjustable, so feel free to add what you want to the batter.
 * You can add any topping you like.
 * Microwave it for longer if you think it is not thoroughly cooked or for shorter if you think it will be over-done.

title: Cookbook:Honey Mug Cake


text:
User:Soapyduck

Hi! I'm Soapyduck. I mainly edit on English Wikipedia. Here's that user page

Currently working on
• Cookbook:Honey Mug Cake

title: User:Soapyduck


text:
User:Dirk Hünniger/Git

= Obtaining Git =

= Introduction =

= Branching & merging =

= Beyond the basics =

= Interacting with other SCMs =

= Hosting =

= Setting up a Server =

= Git component programs =

= Getting help =

title: User:Dirk Hünniger/Git


text:
Cookbook talk:Honey Mug Cake

Yeast question
I'm curious why yeast is added to this recipe, since no fermentation time is specified to allow the yeast to act. What is the yeast contributing to the recipe? —Kittycataclysm (discuss • contribs) 12:37, 27 June 2024 (UTC)

title: Cookbook talk:Honey Mug Cake


text:
User:Cremastra (JWB)

This is an alternate account of Cremastra (discuss • contribs) used for semi-automated editing with JavaScript Wiki Browser (JWB). It is used here and at enwiki.

title: User:Cremastra (JWB)


text:
User:Lindo Kabini

Testing how this works. I am preparing to make a chess book or a python book.

title: User:Lindo Kabini


text:
User:Cremastra (JWB)/common.js

mw.loader.load('//en.wikipedia.org/w/index.php?title=User:Joeytje50/JWB.js/load.js&action=raw&ctype=text/javascript');

title: User:Cremastra (JWB)/common.js


text:
Template:Appendix

= Appendix =

title: Template:Appendix


text:
Talk:Open Scholarship Press Collections: Policy

Scholarships must open opportunities
Scholarship must obtains achievement at all times

Siyolise Manqunyana (discuss • contribs) 21:00, 27 June 2024 (UTC)


text:
AI Art Generation Handbook/Archive/Settings

This is another examples of generating realistic human figures :

Correlations between settings
The picture shows the correlations between CFG and Sampling Steps.

It is note worthy to look that steps that are too low and with high CFG values will almost caused the images to become distorted.

The CFG that are too low will make the picture appeared washed out.


text:
User talk:41.114.186.186

June 2024
MathXplore (discuss • contribs) 13:24, 28 June 2024 (UTC)

title: User talk:41.114.186.186


text:
User talk:185.106.30.159

June 2024
MathXplore (discuss • contribs) 13:24, 28 June 2024 (UTC)

title: User talk:185.106.30.159


text:
User talk:2405:201:24:28A6:D480:B769:A495:73A7

June 2024
MathXplore (discuss • contribs) 13:25, 28 June 2024 (UTC)


text:
User:Dirk Hünniger/mcs

= Introduction =

= Getting Started =

= Overworld =

Building a Nether Portal
= Nether =

Nether Fortresses
= Exiting Nether =

title: User:Dirk Hünniger/mcs


text:
User:Dom walden/Multivariate Analytic Combinatorics/Cauchy-Hadamard Theorem and Exponential Bounds

Theorem
Let $$\alpha$$ be an n-dimensional vector of natural numbers ($$\alpha = (\alpha_1, \cdots, \alpha_n) \in \N^n$$) with $$||\alpha|| = \alpha_1 + \cdots + \alpha_n$$, then $$f(z)$$ converges with radius of convergence $$\rho = (\rho_1, \cdots, \rho_n) \in \R^n$$ with $$\rho^\alpha = \rho_1^{\alpha_1} \cdots \rho_n^{\alpha_n}$$ if and only if

 * $$\limsup_{||\alpha||\to\infty} \sqrt[||\alpha||]{|c_\alpha|\rho^\alpha}=1$$

where

 * $$f(z) = \sum_{\alpha\geq0}c_\alpha(z-a)^\alpha := \sum_{\alpha_1\geq0,\ldots,\alpha_n\geq0}c_{\alpha_1,\ldots,\alpha_n}(z_1-a_1)^{\alpha_1}\cdots(z_n-a_n)^{\alpha_n}$$

Proof
Set $$z = a + t\rho$$ $$(z_i = a_i + t\rho_i)$$, then

 * $$\sum_{\alpha \geq 0} c_\alpha (z - a)^\alpha = \sum_{\alpha \geq 0} c_\alpha \rho^\alpha t^{||\alpha||} = \sum_{\mu \geq 0} \left( \sum_{||\alpha|| = \mu} |c_\alpha| \rho^\alpha \right) t^\mu$$

This is a power series in one variable $$t$$ which converges for $$|t| < 1$$ and diverges for $$|t| > 1$$. Therefore, by the Cauchy-Hadamard theorem for one variable

 * $$\limsup_{\mu \to \infty} \sqrt[\mu]{\sum_{||\alpha|| = \mu} |c_\alpha| \rho^\alpha} = 1$$

Setting $$|c_m| \rho^m = \max_{||\alpha|| = \mu} |c_\alpha| \rho^\alpha$$ gives us an estimate

 * $$|c_m| \rho^m \leq \sum_{||\alpha|| = \mu} |c_\alpha| \rho^\alpha \leq (\mu + 1)^n |c_m| \rho^m$$

Because $$\sqrt[\mu]{(\mu + 1)^n} \to 1$$ as $$\mu \to \infty$$

 * $$\sqrt[\mu]{|c_m| \rho^m} \leq \sqrt[\mu]{\sum_{||\alpha|| = \mu} |c_\alpha| \rho^\alpha} \leq \sqrt[\mu]{|c_m| \rho^m} \implies \sqrt[\mu]{\sum_{||\alpha|| = \mu} |c_\alpha| \rho^\alpha} = \sqrt[\mu]{|c_m| \rho^m} \qquad (\mu \to \infty)$$

Therefore

 * $$\limsup_{||\alpha||\to\infty} \sqrt[||\alpha||]{|c_\alpha|\rho^\alpha} = \limsup_{\mu \to \infty} \sqrt[\mu]{|c_m| \rho^m} = 1$$

Example
For the central diagonal of our example, $$\Delta \frac{1}{1 - x - y} = \sum_{n \geq 0} f_{n, n} x^n y^n$$:

 * $$\limsup_{n \to \infty} \sqrt[n]{|f_{n,n}| x^n y^n} = 1 \implies \limsup_{n \to \infty} |f_{n,n}| = \frac{1}{(x y)^n}$$

$$x^n y^n$$ is at its largest when $$x = y = \frac{1}{2}$$ so that $$\limsup_{n \to \infty} |f_{n,n}| = 4^n$$.

We know by Stirling's approximation that this is a good estimate.

But what about a diagonal along an arbitrary ray, like the above example $$\Delta^{(2, 1)} \frac{1}{1 - x - y}$$?

 * $$\limsup_{|n\textbf{r}| \to \infty} \sqrt[|n\textbf{r}|]{|f_{2n,n}| x^{2n} y^n} = 1 \implies \limsup_{|n\textbf{r}| \to \infty} |f_{2n,n}| = \frac{1}{(x^2 y)^n}$$

If we keep $$x = y = \frac{1}{2}$$ then $$\limsup_{|n\textbf{r}| \to \infty} |f_{2n,n}| = 8^n$$

This isn't a good estimate.

Better to use $$x = \frac{2}{3}, y = \frac{1}{3}$$ then $$\limsup_{|n\textbf{r}| \to \infty} |f_{2n,n}| = \left(\frac{27}{4}\right)^n = (6.75)^n$$

Convex optimisation
In the below, the function we are interested in is $$F(\textbf{z}) = \frac{G(\textbf{z})}{H(\textbf{z})}$$.

We therefore want to find the $$\textbf{w}$$ on the domain of convergence of $$F(\textbf{z})$$ that minimises $$\textbf{w}^{-\textbf{r}}$$.

The subject of convex optimisation already has the tools for this, but in order to use it we need to transform the domain of convergence to be a convex set and $$\textbf{w}^{-\textbf{r}}$$ to be a convex function.

Give examples of how useful convex is...

Fortunately, the logarithmic image of the domain of convergence of a power series of a complex function is convex.

Therefore, we define

 * $$Relog(\textbf{z}) = (\log |z_1|, \cdots, \log |z_d|)$$

 * $$amoeba(H) = \{Relog(\textbf{z}) : H(\textbf{z}) = 0\}$$

The domain of convergence of our function can now be defined as the complement of this amoeba

 * $$amoeba(H)^c = \R^d \setminus amoeba(H)$$

This may leave us with multiple unconnected components, each one for a different Laurent series expansion. Denote the component we are interested in as $$B$$

 * $$\mathcal{D} = Relog^{-1}(B)$$

The logarithmic image of $$\textbf{w}^{-\textbf{r}}$$ is $$h(\textbf{w}) = -\textbf{r} \cdot Relog(\textbf{w})$$. Because $$\log$$ is a concave function, $$-\log$$ is convex.

So we now have a problem of minimising a convex function over a convex set.

We want to find the supporting hyperplane to $$\bar B$$ with outward-facing normal $$-\nabla h(\textbf{w})$$.

Critical point equations
This happens when the supporting hyperplane defined above coincides with the tangent plane with normal $$\nabla H(\textbf{w})$$.

This means they are not linearly independent and therefore the matrix

 * $$\begin{pmatrix}

\frac{\partial H}{\partial z_1}(\textbf{w}) & \cdots & \frac{\partial H}{\partial z_d}(\textbf{w}) \\ r_1/w_1 & \cdots & r_d/w_d \end{pmatrix}$$

is rank deficient, or its 2 x 2 submatrices have zero determinants. This is equivalent to a system of equations referred to as the critical point equations

 * $$H(\textbf{w}) = 0 \quad r_j w_1 \frac{\partial H}{\partial z_1}(\textbf{w}) - r_1 w_j \frac{\partial H}{\partial z_j}(\textbf{w}) = 0 \quad (2 \leq j \leq d).$$

Caution
Needs to be smooth...

Not necessarily tight...


text:
User:Rojothattil

Rojo T J

S/o Jose Ousephunny, Thattil house, kuruvilassery p. O, Mala, Kerala, India

Pin-680732

title: User:Rojothattil


text:
User:Dirk Hünniger/PostgreSQL

= Major Features =

= Supported Platforms =

= Download, Installation =

= Managing the Instance =

= DBA Tools: psql, pgAdmin, phpAdmin, ... =

= Configuration =

= Backup & Recovery =

= Architecture: Collaboration of Processes, RAM, and Files =

= The logical Perspective: Cluster, Database, Schema =

= The physical Perspective: Directories and Files =

= Transactions =

= The ACID Paradigm =

= Visibility of Rows: Isolation Levels =

= Multiversion Concurrency Control (MVCC): Implementation of the ACID Paradigm =

= Vacuum =

= Wraparound and Freeze =

= Visibility Map and Free Space Map =

= Write-Ahead-Log (WAL) =

= Client-Server Communication: The Client Side =

= Client-Server Communication: The Server Side =

= Security within the Database: Roles, Users, Privileges =

= Replication =

= Partitioning =

= Tablespace =

= Upgrade =

= Glossary / Prominent Terms =

= The Extension Mechanism =

= PostGIS - Spatial Data =

= Foreign Data Wrappers =

= BDR: Bidirectional Replication =

= Page Layout for Data and Index Files =

= Indices =

= B-tree =

= GIN =

= BRIN =

= Hash =

title: User:Dirk Hünniger/PostgreSQL


text:
User:Dirk Hünniger/MySQL

= Introduction =

= Practical Guide =

= Databases manipulation =

= Browsing the databases =

= Specifying table names =

= Definitions =

= User Variables =

= Alias =

= Data Types =

= Table manipulation =

= Data manipulation =

= Queries =

= Using/Dealing with NULL =

= Operators =

= Import / export =

= Functions =

= Stored Programs =

= Spatial databases =

= Exercises =

= Pivot table =

= Table types =

= Administration =

= Replication =

= Optimization =

= APIs =

= Debugging =

= CheatSheet =

= Contributors =

title: User:Dirk Hünniger/MySQL


text:
User:Dirk Hünniger/PHP Programming

= Introduction =

= Setup and Installation =

= Uses of PHP =

= Beginning_with "Hello World!" = = Nuts and Bolts =

= Commenting and Style =

= Comparison operators =

= Arrays =

= The if Structure =

= The switch Structure =

= The while Loop = = The do while Loop = = The for Loop =

= The foreach Loop = = Functions =

= PHP Include Files =

= Files =

= Images =

= Mailing =

= Cookies = = Sessions =

= MySQL =

= PHP and MySQL =

= PostgreSQL =

= PHP Data Objects =

= Neo4j =

= DBAL =

= Integration Methods (HTML Forms, etc.) = = Regular expressions =

= Data Structures =

= Classes =

= Special Methods =

= Overriding and Overloading =

= Inheritance =

= SSH Class =

= Caching =

= Why Templating =

= Templates =

= Smarty templating system =

= Smarty templating system/Functions =

= Smarty templating system/Simple tutorial =

= XML =

= XSL =

= registerPHPFunctions =

= PHP PEAR =

= PHP Libraries = = Frameworks =
 * 1) PHP Manual Function Reference
 * 2) PHP 5 Functions

= Register Globals =

= SQL Injection Attacks =

= Building a secure user login system =

= Cross Site Scripting Attacks =

= Secure HTTP headers =

= Encryption =

= More Security = in the. (CSRF)

= PHP Command-Line Interface =

= PHP-GTK =

= Daemonization =

= Alternative Hungarian Notation =

= Code Snippets =

= Coding Standards =

= Formatting Notes =

= Get Apache and PHP =

= Headers and Footers =

= HTML Output =

= Advanced Input Validation =

= Input Validation =

= phpDocumentor =

= Reserved Words =

= Contributors =

= Editors =

= Resources =

title: User:Dirk Hünniger/PHP Programming


text:
Cookbook:Cream Wafers

Cream wafers are a type of sandwich cookie that pair delicate, buttery, sugar-coated cookies with a filling of buttercream icing. You are more likely to see this at an afternoon tea than as an after-dinner dessert.

Equipment

 * Mixing bowl
 * Mixing spoon
 * Rolling pin
 * Plastic cling wrap, parchment paper, or wax paper (optional but recommended)
 * Cookie sheet
 * Cookie cutter, round or fluted, about 1½ inches (3–4 cm) in diameter
 * Cooling rack
 * Spatula

Mix dough

 * 1) Cut the butter into smaller pieces.
 * 2) Put the butter pieces and flour into a mixing bowl, and blend the ingredients together. You can do this by hand or with an electric mixer.
 * 3) Pour in the the whipping cream, and mix gently until the dough holds together. Do not overmix, or the cookies will be tough.

Sheet and freeze dough

 * 1) Turn the dough out onto the counter or a flat board and form into a disk.
 * 2) * If you cover your work area with plastic cling wrap, you do not need to put any flour on the surface. Cover the top of the dough with another layer of plastic wrap to keep your hands or rolling pin clean. You will also be able to re-roll and use the scrap dough with a lower risk of the second rolling being tough.
 * 3) * If you are working on a counter or board, sprinkle a large spoonful of flour on the surface before taking the dough out of the mixing bowl, and then another spoonful on top. Use just enough flour to keep the dough from sticking too much.
 * 4) Roll the dough out until it is ⅛ inch (3–4 mm) thick and almost as big as your baking sheet.Cheese_Sticks_(5729526519).jpg
 * 5) Place the whole sheet of dough on your baking pan, and put it in the freezer for at least 20 minutes until it is completely frozen.
 * 6) * If you are using plastic cling wrap, leave the dough on the plastic cling wrap.
 * 7) * If you have too much dough to fit on your baking sheet, divide the dough into parts and repeat the process until all of the dough has been rolled out and placed in the freezer. Sheets of dough can stack on top of each other in the same pan, as long as there is a layer of plastic cling wrap or other barrier between them, to keep the sheets of dough from sticking to each other.
 * 8) * If you cover the sheets of dough tightly to prevent them from drying out or absorbing other smells and flavors from the freezer, they can stay in the freezer for at least a week.

Cut out cookies

 * 1) Put the white sugar in a shallow bowl or on a small plate.
 * 2) Remove one sheet of dough from the freezer. If you have rolled it on plastic cling wrap, loosen the frozen dough (both sides) from the plastic wrap.
 * 3) Using the cookie cutter, cut out as many circles of dough as you can. Set aside scrap dough for re-rolling and re-freezing.
 * 4) Dip both sides of each cookie into the bowl of sugar, and place them on an ungreased, unlined baking sheet.
 * 5) * If the frozen dough starts melting, then it may become difficult to pick up the cookies without stretching them. If this happens, you can put the sheet of dough back into the freezer for a few minutes so it can firm up again.
 * 6) * The cookies do not expand much in the oven, so they can be placed fairly close together on the baking sheet, but you don't want to let them touch each other.
 * 7) Dock each cookie with a fork to make a pattern and to prevent uneven bubbles during the baking process.
 * 8) Repeat the rolling, freezing, and cutting process for the scrap dough pieces.

Bake cookies

 * 1) Preheat oven to 375 °F (190 °C, gas mark 5—moderately hot).
 * 2) Bake each sheet for 7–9 minutes, until the top is set and the bottom edges are just turning brown.
 * 3) * Be careful when moving the tray of cookies, as they slide around very easily. If your baking pan doesn't have a solid rim on all sides, the raw cookies might try to slide off the pan and onto the floor or the bottom of the oven.
 * 4) With a cookie spatula/lifter, carefully remove the fragile cookies from the pan and place them on a wire cooling rack. Cool completely before trying to move them or frost them.

Fill cookies

 * 1) Put a small spoonful of frosting on the back of one cookie.
 * 2) Place another cookie on top of the frosting to make a sandwich, and set aside.
 * 3) Serve cookies at room temperature.

Notes, tips, and variations

 * Store at room temperature. The frosted cookies keep well for a couple of days. Unfrosted cookies keep well for about a week if protected from excessive humidity.
 * There is no sugar in the dough—the sugar is used to coat the cookies later.
 * This recipe scales well (e.g. to half, double, or quadruple). If you are making a large number of cookies, consider using a piping bag to squirt frosting onto the cookies.
 * You can use gluten-free flour substitutes, but the result will be fragile. Try making thicker cookies so they are a little sturdier.
 * The whipping cream should be liquid (like milk), not already whipped.
 * If your butter is cold, the dough may have some drier or crumbly spots; if your butter is very soft, it may be sticky. If the dough is sticky, rolling it between sheets of plastic cling wrap will be much easier.
 * Ordinary white granulated sugar is the most typical, but you can use decorative colored sugar. Do not use powdered sugar, brown sugar, or sugar substitutes to coat the cookies.
 * The number of cookies you will get depends on the size of the cookie cutter you use.

title: Cookbook:Cream Wafers


text:
User talk:47.217.107.229

June 2024
MathXplore (discuss • contribs) 04:32, 30 June 2024 (UTC)

title: User talk:47.217.107.229


text:
User:MFNickster

This is my only line.

title: User:MFNickster


text:
User talk:Morshed RC

June 2024
MathXplore (discuss • contribs) 13:39, 30 June 2024 (UTC)

title: User talk:Morshed RC


text:
User:JackkBrown

.

title: User:JackkBrown


text:
Talk:A Traveler's Guide to the World of Pokémon/Regions

hey, does anyone have a diffinitive map of the pokemon world?
I need one so i can fit my fan region, the mezoa region, into the map which would be cool 2601:240:4E00:1190:82A:EF2C:F12C:7FB1 (discuss) 01:19, 1 July 2024 (UTC)


text:
User talk:188.236.2.8

July 2024
MathXplore (discuss • contribs) 01:33, 1 July 2024 (UTC)

title: User talk:188.236.2.8


text:
User talk:Jfw01

Delete all
Delete all recent codes 31.154.161.121 (discuss) 12:36, 1 July 2024 (UTC)

title: User talk:Jfw01


text:
User talk:27.74.194.175

Çınar
Kırca

78.177.133.131 (discuss) 15:47, 1 July 2024 (UTC)

title: User talk:27.74.194.175


text:
Talk:Ada Programming/Libraries/Ada.Environment Variables

History for the content recovered from wiki.ada-dk.org/ada.environment_variables
From http://web.archive.org/web/20210921134732/http://wiki.ada-dk.org/ada.environment_variables

2012/01/14 20:44 ada.environment_variables – created thomaslocke (current)

The footer says "Except where otherwise noted, content on this wiki is licensed under the following license: Public Domain"

-- ManuelGR (discuss • contribs) 19:25, 1 July 2024 (UTC)


text:
User:Rajibarber

I am a budding page editor, contributor with background in cultural studies, ready to learn, explore, and eventually help.

Thanks.

title: User:Rajibarber


text:
AI Art Generation Handbook/Node Prompting in Stable Diffusion/ComfyUI Custom Output Name

To create a custom output name is easy, the format is usually goes like this

Here are 3 most common ways to customise the prompt name

(1) K-Sampler
Original Node name for S&R : (2) Text Prompt Original Node name for S&R : (3) Empty Latent Image Original Node name for S&R :


text:
Talk:Ada Programming/Variables

History for the content recovered from wiki.ada-dk.org
From http://web.archive.org/web/20210921133457/http://wiki.ada-dk.org/variables_and_constants

2012/01/14 20:44 ada.environment_variables – created thomaslocke (current)

 * 2013/02/21 08:31 variables_and_constants – [Variables] thomaslocke (current)
 * 2012/03/06 22:18 variables_and_constants – fixed a few grammar erros cvanvliet
 * 2011/12/16 20:50 variables_and_constants thomaslocke
 * 2011/12/15 20:19 variables_and_constants thomaslocke
 * 2011/12/15 20:18 variables_and_constants – created thomaslocke

The footer says "Except where otherwise noted, content on this wiki is licensed under the following license: Public Domain"

-- ManuelGR (discuss • contribs) 19:44, 2 July 2024 (UTC)

title: Talk:Ada Programming/Variables


text:
Talk:Ada Programming/Constants

History for the content recovered from wiki.ada-dk.org
From http://web.archive.org/web/20210921133457/http://wiki.ada-dk.org/variables_and_constants

2012/01/14 20:44 ada.environment_variables – created thomaslocke (current)

 * 2013/02/21 08:31 variables_and_constants – [Variables] thomaslocke (current)
 * 2012/03/06 22:18 variables_and_constants – fixed a few grammar erros cvanvliet
 * 2011/12/16 20:50 variables_and_constants thomaslocke
 * 2011/12/15 20:19 variables_and_constants thomaslocke
 * 2011/12/15 20:18 variables_and_constants – created thomaslocke

The footer says "Except where otherwise noted, content on this wiki is licensed under the following license: Public Domain"

-- ManuelGR (discuss • contribs) 19:44, 2 July 2024 (UTC)

title: Talk:Ada Programming/Constants


text:
Cherokee/Structural Nuggets

These "structural nuggets" refer to elements in the Cherokee language categorized as units of structure, as opposed to content words like nouns, for example. As such, the words or word parts found here do not solely belong to one part of speech. These "nuggets" are like the glue holding much of the language together!

Each nugget is presented in a boldface header, followed by a line defining it. Uppercase abbreviations such as ADJ for "adjective" are used to represent variable words or word parts, while lowercase Cherokee text represents invariable elements within the nugget.

Following the definition, you may find examples.

At the bottom of each entry you may find questions whose answers are unclear to the writers of this book. We empower you to ask these questions to native speakers of Cherokee and to document the answers in the Discussion section for this page, found at the top of the screen to the right of the tab that says "Book." You are always encouraged to ask for and document other ways to express the same idea for every nugget.

Abbreviations
ADJ = adjective

S = subject

S1 = subject number 1

V = verb

V1 = verb number 1

CSP = citation for Cherokee Speech Patterns by JW Webster

ADJ + jigi
the (possibly also "a") ADJ one giígágẽ j-igi

red REL-be

the red one

CSP 22 Questions: How do you say "the red ones" or "some red ones"?

ADJ -yú
-ly

One way to form adverbs from adjectives, equivalent to the English suffix -ly, is to add -yú to the end of the adjective.

If the adjective ends in -i, the /i/ lengthens and gets a rising tone in anticipation of the high tone on the suffix -yú. uusganõli > uusganõliíyú

slow > slowly

CSP 23

S1 agvvyĩ V1 si ni- V2 -ṽna(wú) S2
S1 V1 before S2 V2

One way to express that an action happens before another action is to use this structure. maági agvvyĩ uùhnigíisééqi si núúluhjṽnawú uweej ageéhya

Mark first 3SG.B-left still without-3SG.B-arriving 3SG.B-child woman

Mark left before his daughter arrived.

CSP24

title: Cherokee/Structural Nuggets


text:
Ada Programming/Input Output/Text Example

Introduction
Those of us with American friends often have to deal with the Fahrenheit temperature scale. While the rest of the world has adopted the Celsius temperature scale, America and a few other countries have stayed true to Fahrenheit.

While this is both a small and insignificant problem when dealing with friends, it is nevertheless a problem worthy of having its own program: A Fahrenheit to Celsius converter.

The necessary files and directories
Before we start, we need to do a little preparation. First create the following directory/file structure somewhere on your computer:

The above should leave you with the following contents in the  directory:

exe/ objects/ ftoc.adb ftoc.gpr

We will use these two directories and files in the following manner:

 * exe/ This is the directory where the  executable is placed when compiling the program
 * objects/ When compiling a program, the compiler creates ALI files, object files and tree files. These files are placed in this directory.
 * ftoc.adb The main Ada source file for the ftoc program.
 * ftoc.gpr This is an Ada project file. This file controls various properties of the program, such as how to compile it, what sources to include, where to put things, and so on.

The Project File
Add this to the  file:

Please go here for an explanation on the different parts of the above project file.

The Actual Program
With the project file out of the way, we turn our attention to the actual  code. Add this to the  file:

Save the file, and lets move on to the final step: Compiling.

Compile And Run FtoC
If you use the excellent GNAT Studio IDE, the compiling is a simple matter of pressing  to compile the project, and   to execute it. If you're not using this IDE, then do this instead:

You should see some output scroll by:

gcc -c -gnatwa -gnaty3abcdefhiklmnoprstux -Wall -O2 -I- -gnatA /home/thomas/FtoC/ftoc.adb gnatbind -I- -x /home/thomas/FtoC/objects/ftoc.ali gnatlink /home/thomas/FtoC/objects/ftoc.ali -o /home/thomas/FtoC/exe/ftoc

You now have an executable in the / directory. When you run it, you get this (somewhat abbreviated here):

0 -17.78 1 -17.22  2 -16.67  ...  26  -3.33  27  -2.78  28  -2.22  29  -1.67  30  -1.11  31  -0.56  32   0.00  33   0.56  34   1.11  35   1.67  ...  48   8.89  49   9.44  50  10.00  51  10.56  52  11.11  ...  67  19.44  68  20.00  69  20.56  70  21.11  71  21.67  ...  84  28.89  85  29.44  86  30.00  87  30.56  ...  210  98.89  211  99.44  212 100.00

Now we know that 0 degrees Fahrenheit equals -17.78 Celsius and at 212 degrees Fahrenheit water boils, which to us Celsius users is known as 100 degrees Celsius. The program works! Lets go over it in detail, to figure out how it works.

Note: All output in the following examples will be heavily abbreviated, because printing 213 lines of output for every little example is madness.

How Does The FtoC Program Work?
Lets start with the first three lines:

These are called  clauses and   declarations. An Ada  clause can be likened to a C. When you see, it means the utilities of the   package are being made available to the program. When next you see the declaration, it means that the utilities of   are directly visible to the program, ie. you do not have to write

to call the  procedure. Instead you simply do

In the FtoC program we utilize, and make visible, three packages:,   and. These packages provide exactly what their names imply: Text IO capabilities for different types.

Looking at the source, you might wonder where the need for  comes in, as we're only outputting numbers. We will get to that in a minute, so stay tuned.

The FtoC declarations
Next we have this code:

This is called the declarative part of an Ada program. It is here we declare our variables, constants, types and whatnot. In the case of FtoC we have 5 declarations. Lets talk a bit about the first two:

That right there is one of the biggest selling points of Ada: The ability to create your own types, with your own constraints. It might not seem like a big deal but, believe me, it is. In this case we've created a new subtype of the built-in subtype Natural. We've constrained the type's range to, meaning that objects declared as a   can never go below 0 or above 212. If a value outside this range is assigned to an object of the  type, a   exception is raised.

With the  type in place, we direct our attention to the declaration and assignment of the   variable. If you've never seen this syntax before or it makes no sense to you, please read the Constants article on this Wiki, and then return here.

The  variable is of the   type and it's initial value is 0. Why 0? Because we assign it the value, and the   part equals the first value in the range constraint of the type, in this case 0. Consequently the value for  is 212.

Let's take a look at the final three object declarations:

What's going on here? Why are there no  associated with any of those declarations? Well, if you've read the Constants article, you will know that these constants are called named numbers and their  is called an universal type. Named numbers can be of any size and precision.

The  and   constants are used in the Fahrenheit-to-Celsius calculation, and   define how many conversions we do in the program.

The FtoC body
With the declarations out of the way, we turn our attention to the body of the program:

The reserved word  signifies the beginning of the   and that same body ends with the final. Between those two, we have a bunch of statements.

The loop
The first one is the  statement. Loops come in many different shapes in Ada, each of which obeys the basic premise of

Loops can be terminated using the  keyword:

This construction is so common that a shorter version has been made available:

It is this last version we use in the FtoC program and we exit the loop when  equals the   value of the   type.

FtoC output - putting integers on the screen
Immediately after the  statement we encounter the   procedure:

We know from the declaration that  is a subtype of , which in turn is a subtype of  , so the call to   on this line actually calls. As you can see, we give  two parameters:   and. The meaning of  should be obvious: It's the integer we want to output, in our case the   variable.

on the other hand does not make as much sense. The  parameter gives the minimum number of characters required to output the integer type or, in our case, subtype, as a literal, plus one for a possible negative sign. If the  parameter is set too high, the integer literal is padded with whitespace. If it's set too low, it is automatically expanded as necessary. Setting the  parameter to 0, results in the field being the minimum width required to contain the integer.

The  attribute returns the maximum width of the type, so if we change the   later on, we wouldn't have to do a single thing about this call to  ; it would simply adjust itself accordingly.

Let's do some tests with various  parameters:

The output now looks like this:

0 -17.78          1 -17.22           2 -16.67           3 -16.11           4 -15.56           ...

Lots of wasted space there. This is because  now sets aside space for the , which is the type   is derived from. Let's try with 0:

And the output:

0 -17.78 1 -17.22  2 -16.67  3 -16.11  9 -12.78  10 -12.22  11 -11.67  99  37.22  100  37.78  101  38.33  ...

Unfortunately for readability, the  integer literal is no longer right-justified. Each number is given the exact width necessary to hold it and no more.

Let's try it with a  that is wide enough for some of the   values, but not all of them:

This outputs:

0 -17.78  1 -17.22   2 -16.67   9 -12.78  10 -12.22  11 -11.67  98  36.67  99  37.22  100  37.78  101  38.33  102  38.89  103  39.44  ...

As you can see, the single digit values are right-justified and padded with 1 space, the two-digit values come out even, but the rest of the results are expanded to hold the third character.

FtoC output - now with floats
With  for integer types out of the way, we move on to the next  >

The  parameter for this call to   is a float, because   is a named number that contains a decimal point and the expression   is converted to a float using the   expression. So when calling this, we're actually calling.

The  parameter gives the minimum character count necessary to output the value preceding the decimal point. As with  for the integer types,   will automatically expand if necessary. sets the precision after the decimal point, in this case 2. And finally  sets the exponent field size. A value of  signifies that no exponent will be output. Anything other than zero will output the exponent symbol "E", a +/-, and the digit(s) of the exponent. Note: The value of  should not be less than zero!

Let's try a few different combinations:

The output:

0      -17.7778    1       -17.2222   15        -9.4444   16        -8.8889   17        -8.3333   26        -3.3333   27        -2.7778  100        37.7778  101        38.3333  102        38.8889  103        39.4444  104        40.0000  ...

Or how about this:

And the output:

0 -1.78E+1 1 -1.72E+1 2 -1.67E+1 8 -1.33E+1 9 -1.28E+1 10 -1.22E+1 11 -1.17E+1 18 -7.78E+0 37  2.78E+0 98  3.67E+1 99  3.72E+1 100  3.78E+1 101  3.83E+1 ...

And finally:

This outputs:

0-17.8   8-13.3    9-12.8   10-12.2   11-11.7   31-0.6   320.0   499.4   9836.7   9937.2  10037.8  10138.3  10238.9  ...

Which obviously isn't very pretty to look at.

A new line, an exit strategy, and a step
The last four lines of the FtoC program finish our formatting, get us out of here if we are done, and, if not, set the next value of  to be converted:

The single call to  is the reason we have to make   available to the FtoC program using. What  does is output a single line feed. Running the program without this call to  would result in output looking like this:

0 -17.78  1 -17.22   2 -16.67   3 -16.11   4 -15.56   5 -15.00   6 -14.44   7 -13.89   8 -13.33   9 -12.78  10 -12.22  11 -11.67 ...

The  procedure accepts a   parameter, meaning you can do this to output consecutive line feeds:

Or simply

We've already discussed the  method of terminating a loop, and the final statement is merely a simple counter. The value of  is incremented with   on each iteration of the loop. When  equals , the loop is terminated.

The final line,, signifies the end of the program. There's nothing more to do and nothing more to see. Control is handed back to whatever called the program in the first place, and life goes on.

Conclusion
I hope you've enjoyed this little tutorial on building a Fahrenheit to Celsius conversion table. It is left to the reader to figure out how to add Kelvin to the mix. Have fun!

Wikibook

 * Ada Programming/Input Output


text:
Talk:Ada Programming/Input Output/Text Example

History for the content recovered from wiki.ada-dk.org
From http://web.archive.org/web/20210921140745/http://wiki.ada-dk.org/ftoc_-_a_fahrenheit_to_celsius_converter

 * 2012/03/06 22:20 ftoc_-_a_fahrenheit_to_celsius_converter – fixed a few grammar erros cvanvliet (current)
 * 2011/12/16 22:24 ftoc_-_a_fahrenheit_to_celsius_converter – [A new line, an exit strategy, and a step] thomaslocke
 * 2011/12/16 22:23 ftoc_-_a_fahrenheit_to_celsius_converter – [FtoC output - putting integers on the screen] thomaslocke
 * 2011/12/16 22:21 ftoc_-_a_fahrenheit_to_celsius_converter – [The loop] thomaslocke
 * 2011/12/16 22:20 ftoc_-_a_fahrenheit_to_celsius_converter – [The FtoC declarations] thomaslocke
 * 2011/12/16 22:18 ftoc_-_a_fahrenheit_to_celsius_converter thomaslocke
 * 2011/12/16 22:17 ftoc_-_a_fahrenheit_to_celsius_converter thomaslocke
 * 2011/12/16 22:12 ftoc_-_a_fahrenheit_to_celsius_converter thomaslocke
 * 2011/12/16 21:08 ftoc_-_a_fahrenheit_to_celsius_converter thomaslocke
 * 2011/12/16 20:59 ftoc_-_a_fahrenheit_to_celsius_converter – created thomaslocke

The footer says "Except where otherwise noted, content on this wiki is licensed under the following license: Public Domain"

-- ManuelGR (discuss • contribs) 21:36, 2 July 2024 (UTC)


text:
User talk:174.214.49.181

July 2024
MathXplore (discuss • contribs) 03:47, 3 July 2024 (UTC)

title: User talk:174.214.49.181


text:
User talk:2409:40C1:54:D35E:357B:2C9E:3C9E:8BC1

July 2024
MathXplore (discuss • contribs) 12:47, 3 July 2024 (UTC)


text:
User talk:Bong'musa Mamba

Hi everyone I'm Bong'musa Mamba from Eswatini but currently staying at Mpumalanga in South Africa thanks for accepting me here 😊

title: User talk:Bong'musa Mamba


text:
User:Bong'musa Mamba

Mechanical engineering tips

title: User:Bong'musa Mamba


text:
Talk:Ada Programming/Libraries/Ada.Interrupts

History for the content recovered from wiki.ada-dk.org
From http://web.archive.org/web/20210921145739/http://wiki.ada-dk.org/catching_and_handling_interrupts_in_ada

 * 2012/01/02 21:50 catching_and_handling_interrupts_in_ada – [catch_signals.gpr] thomaslocke (current)
 * 2012/01/02 20:46 catching_and_handling_interrupts_in_ada – [The Program] thomaslocke
 * 2012/01/02 20:45 catching_and_handling_interrupts_in_ada – [The Program] thomaslocke
 * 2012/01/02 20:44 catching_and_handling_interrupts_in_ada – created thomaslocke

The footer says "Except where otherwise noted, content on this wiki is licensed under the following license: Public Domain"

-- ManuelGR (discuss • contribs) 19:30, 3 July 2024 (UTC)

 * The original github repository no longer exists, so I've used a fork from another user. ManuelGR (discuss • contribs) 19:31, 3 July 2024 (UTC)


text:
Ada Programming/Libraries/GNAT.String Split

Introduction
Exploding a string into several components based on a set of separators can be done in many different ways. In this article we're going to focus on a solution involving the  package.

Caveat
If you use the following example in a program of your own, the result will be a less portable program. The GNAT packages are only found in the [|GNAT GPL] and in the [|GNU GCC GNAT] compilers, meaning that your program probably won't compile with other Ada compilers.

The Problem
You want to split a string into a set of individual components, such as

This is a string

into

This is a  string

And this is exactly what you can do with the  package.

The GNAT.String_Split Solution
Let's dive straight into the code necessary to solve our string split problem. Create a file named  and add this to it:

You compile and execute the  program like this:

$ gnatmake explode.adb $ ./explode

You should see output similar to this:

Splitting 'This becomes a  bunch of     substrings' at whitespace. Got 6 substrings: 1 -> This (length 4) 2 -> becomes (length 7) 3 -> a (length 1) 4 -> bunch (length 5) 5 -> of (length 2) 6 -> substrings (length 10) The comments in the example should more or less explain what's going on, but for the sake of clarity, we're going to do a step-by-step walk-through of the code, starting with the dependencies and  clauses:

The three  lines list the packages on which our program depends. When the compiler encounters these, it retrieves those packages from its library. The "//Procedure Explode is//" line marks the start of our program, specifically the declarative part, where we declare/initialize our constants and variables. It also names our program. Note the  clauses. Adding these enables us to do this:

instead of this

in the program. Very handy.

As an exercise, try commenting the three  clauses, and prefix the actual package names to all types and procedures in the program.

Next up we have this:

This is the  we're going to split into individual components. is a constant declared in. It inserts a horizontal tab in the string. Since we don't change the value of  throughout the program, we've initialized it as a constant.

The  variable is the container for the individual components, or "slices".

These are our separators. In this case we want to split the string on space (" ") and horizontal tabs (//Latin_1.HT//). Note that the separators are NOT included as part of the resulting. Try experimenting with different separators.

marks the beginning of the body of our program. Immediately after  we output a short message.

This is the meat of the program. In this one statement the    is split into individual slices based on the   separators, and the resulting slices are placed in the. Note the  parameter. When using  mode,   will treat consecutive whitespace and horizontal tabs as one separator.

As an exercise, try changing  to   and see what happens.

This is the line that's responsible for the output:

Got 6 substrings:

Yes, it looks like an awfully long line for very little output, but there's method to the madness:

That line is responsible for the "6" part of the output. What it does is transform the  value   into the   value "6", and it does so using the   [|attribute]. return a  type, which is basically just an   with a value >=0, and   then convert this to a   suitable for output.

Here we start a loop that repeats  times, which in our case is 6. So on the first loop  is 1 and on the final loop   is 6. Inside the loop we  a new block. This enables us to locally initialize the  constant, which on each repeat of the loop is initialized anew with the next slice from our split. This is done using the  function which takes our   constant and the   loop counter as parameters, and return a. In the body of the block we output each slice, along with its index in the  and its length. As you can see, we once again make use of the  attribute to convert numeric values to.

You can get rid of the block inside the loop like this:

As you can see, we're no longer using the  constant. Instead we call  directly. It works just the same, but it is perhaps a bit less readable.

Another option is to use an. You can see a possible solution here:

Finally we have:

Which simply ends the program.

And with that, we've concluded this small tutorial on how to split a string into individual parts (slices) based on a set of separators. I hope you enjoyed reading it, as much as I enjoyed writing it.

Wikibook

 * Ada Programming/Libraries/GNAT

|GNAT.String_Split


text:
Talk:Ada Programming/Libraries/GNAT.String Split

History for the content recovered from wiki.ada-dk.org
From http://web.archive.org/web/20210921134146/http://wiki.ada-dk.org/gnat.string_split_basic_usage_example

 * 2012/03/06 22:21 gnat.string_split_basic_usage_example – fixed a few grammar erros cvanvliet (current)
 * 2011/12/28 17:16 gnat.string_split_basic_usage_example thomaslocke
 * 2011/12/28 17:12 gnat.string_split_basic_usage_example – created thomaslocke

The footer says "Except where otherwise noted, content on this wiki is licensed under the following license: Public Domain"

-- ManuelGR (discuss • contribs) 19:54, 3 July 2024 (UTC)

Thanks (from original author, Thomas Locke)
I'd like to thank caracal of #ada (Freenode IRC channel) fame for the example source code. And while on the subject of IRC, I'd like to encourage all beginners to join the #ada channel. There are a lot of helpful (and very skilled) Ada programmers hanging out in that channel, and more often than not, they'll gladly help beginning Ada programmers.

The original example can be found here: http://adacommons.org/Separate_a_string_into_substrings_using_GNAT.String_Split

-- ManuelGR (discuss • contribs) 19:57, 3 July 2024 (UTC)


text:
Talk:Ada Programming/Libraries/Ada.Directories

History for the content recovered from wiki.ada-dk.org
From http://web.archive.org/web/20210921141405/http://wiki.ada-dk.org/ada.directories

2012/02/01 10:31 ada.directories – [Start_Search] thomaslocke (current) 2012/02/01 10:30 Show differences to current revisions ada.directories – [Modification_Time] thomaslocke 2012/02/01 10:30 Show differences to current revisions ada.directories – [Size] thomaslocke 2012/02/01 10:30 Show differences to current revisions ada.directories – [Kind] thomaslocke 2012/02/01 10:29 Show differences to current revisions ada.directories – [Exists] thomaslocke 2012/02/01 10:29 Show differences to current revisions ada.directories – [Compose] thomaslocke 2012/02/01 10:28 Show differences to current revisions ada.directories – [Base_Name] thomaslocke 2012/02/01 10:28 Show differences to current revisions ada.directories – [Extension] thomaslocke 2012/02/01 10:27 Show differences to current revisions ada.directories – [Containing_Directory] thomaslocke 2012/02/01 10:27 Show differences to current revisions ada.directories – [Simple_Name] thomaslocke 2012/02/01 10:26 Show differences to current revisions ada.directories – [Full_Name] thomaslocke 2012/02/01 10:26 Show differences to current revisions ada.directories – [Copy_File] thomaslocke 2012/01/31 21:14 Show differences to current revisions ada.directories – [Rename] thomaslocke 2012/01/31 21:14 Show differences to current revisions ada.directories – [Delete_File] thomaslocke 2012/01/31 21:13 Show differences to current revisions ada.directories – [Delete_Tree] thomaslocke 2012/01/31 21:13 Show differences to current revisions ada.directories – [Create_Path] thomaslocke 2012/01/31 21:12 Show differences to current revisions ada.directories – [Delete_Directory] thomaslocke 2012/01/31 21:11 Show differences to current revisions ada.directories – [Create_Directory] thomaslocke 2012/01/31 21:11 Show differences to current revisions ada.directories – [Set_Directory] thomaslocke 2012/01/31 21:10 Show differences to current revisions ada.directories – [Current_Directory] thomaslocke 2012/01/31 21:09 Show differences to current revisions ada.directories – [Modification_Time (Directory Entries)] thomaslocke

The footer says "Except where otherwise noted, content on this wiki is licensed under the following license: Public Domain"

-- ManuelGR (discuss • contribs) 21:49, 3 July 2024 (UTC)


text:
User talk:2601:19C:8100:5200:91B0:B7AE:FA46:2016

--SHB2000 (discuss • contribs) 04:09, 4 July 2024 (UTC)


text:
User:Saniwasgone

hi

title: User:Saniwasgone


text:
AI Art Generation Handbook/GUI/SD.Next

SD.Next is one of the most up to date of text prompting local Web UI (at the rate faster than Auto1111).

Don't be overwhelmed if you are majority of the users as you are probably be using just the 20% of the features listed here

Here, you can do pretty much the following

title: AI Art Generation Handbook/GUI/SD.Next


text:
User talk:2600:6C5A:637E:CF00:51EA:16B7:B791:C88E

July 2024
MathXplore (discuss • contribs) 06:20, 4 July 2024 (UTC)


text:
User talk:38.109.5.24

July 2024
MathXplore (discuss • contribs) 13:22, 4 July 2024 (UTC)

title: User talk:38.109.5.24