Home
About Us
Service
Subscriber
Contact Us
Thank You For Contacting
GEO CHITS PRIVATE LIMITED.
We Will Get Back To You Shortly...


lit - LLVM Integrated Tester
lit [options] [tests]
lit is a portable tool for executing LLVM and Clang style test suites, summarizing their results, and providing indication of failures. lit is designed to be a lightweight testing tool with as simple a user interface as possible.
lit should be run with one or more tests to run specified on the command line. Tests can be either individual test files or directories to search for tests (see TEST DISCOVERY).
Each specified test will be executed (potentially in parallel) and once all tests have been run lit will print summary information on the number of tests which passed or failed (see TEST STATUS RESULTS). The lit program will execute with a non-zero exit code if any tests fail.
By default lit will use a succinct progress display and will only print summary information for test failures. See OUTPUT OPTIONS for options controlling the lit progress display and output.
lit also includes a number of options for controlling how tests are executed (specific features may depend on the particular test format). See EXECUTION OPTIONS for more information.
Finally, lit also supports additional options for only running a subset of the options specified on the command line, see SELECTION OPTIONS for more information.
Users interested in the lit architecture or designing a lit testing implementation should see LIT INFRASTRUCTURE
Show the lit help message.
Run N tests in parallel. By default, this is automatically chosen to match the number of detected available CPUs.
Search for NAME.cfg and NAME.site.cfg when searching for test suites, instead of lit.cfg and lit.site.cfg.
Add a user defined parameter NAME with the given VALUE (or the empty string if not given). The meaning and use of these parameters is test suite dependent.
Suppress any output except for test failures.
Show less output, for example don't show information on tests that pass.
Show more information on test failures, for example the entire test output instead of just the test result.
Do not use curses based progress bar.
Specify an addition PATH to use when searching for executables in tests.
Run individual tests under valgrind (using the memcheck tool). The --error-exitcode argument for valgrind is used so that valgrind failures will cause the program to exit with a non-zero status.
When --vg is used, specify an additional argument to pass to valgrind itself.
Track the wall time individual tests take to execute and includes the results in the summary output. This is useful for determining which tests in a test suite take the most time to execute. Note that this option is most useful with -j 1.
Run at most N tests and then terminate.
Spend at most N seconds (approximately) running tests and then terminate.
Run the tests in a random order.
Run lit in debug mode, for debugging configuration issues and lit itself.
List the discovered test suites as part of the standard output.
Run Tcl scripts internally (instead of converting to shell scripts).
Run each test N times. Currently this is primarily useful for timing tests, other results are not collated in any reasonable fashion.
lit will exit with an exit code of 1 if there are any FAIL or XPASS results. Otherwise, it will exit with the status 0. Other exit codes are used for non-test related failures (for example a user error or an internal program error).
The inputs passed to lit can be either individual tests, or entire directories or hierarchies of tests to run. When lit starts up, the first thing it does is convert the inputs into a complete list of tests to run as part of test discovery.
In the lit model, every test must exist inside some test suite. lit resolves the inputs specified on the command line to test suites by searching upwards from the input path until it finds a lit.cfg or lit.site.cfg file. These files serve as both a marker of test suites and as configuration files which lit loads in order to understand how to find and run the tests inside the test suite.
Once lit has mapped the inputs into test suites it traverses the list of inputs adding tests for individual files and recursively searching for tests in directories.
This behavior makes it easy to specify a subset of tests to run, while still allowing the test suite configuration to control exactly how tests are interpreted. In addition, lit always identifies tests by the test suite they are in, and their relative path inside the test suite. For appropriately configured projects, this allows lit to provide convenient and flexible support for out-of-tree builds.
Each test ultimately produces one of the following six results:
The test succeeded.
The test failed, but that is expected. This is used for test formats which allow specifying that a test does not currently work, but wish to leave it in the test suite.
The test succeeded, but it was expected to fail. This is used for tests which were specified as expected to fail, but are now succeeding (generally because the feature they test was broken and has been fixed).
The test failed.
The test result could not be determined. For example, this occurs when the test could not be run, the test itself is invalid, or the test was interrupted.
The test is not supported in this environment. This is used by test formats which can report unsupported tests.
Depending on the test format tests may produce additional information about their status (generally only for failures). See the Output section for more information.
This section describes the lit testing architecture for users interested in creating a new lit testing implementation, or extending an existing one.
lit proper is primarily an infrastructure for discovering and running arbitrary tests, and to expose a single convenient interface to these tests. lit itself doesn't know how to run tests, rather this logic is defined by test suites.
As described in TEST DISCOVERY, tests are always located inside a test suite. Test suites serve to define the format of the tests they contain, the logic for finding those tests, and any additional information to run the tests.
lit identifies test suites as directories containing lit.cfg or lit.site.cfg files (see also --config-prefix). Test suites are initially discovered by recursively searching up the directory hierarchy for all the input files passed on the command line. You can use --show-suites to display the discovered test suites at startup.
Once a test suite is discovered, its config file is loaded. Config files themselves are Python modules which will be executed. When the config file is executed, two important global variables are predefined:
The global lit configuration object (a LitConfig instance), which defines the builtin test formats, global configuration parameters, and other helper routines for implementing test configurations.
This is the config object (a TestingConfig instance) for the test suite, which the config file is expected to populate. The following variables are also available on the config object, some of which must be set by the config and others are optional or predefined:
name [required] The name of the test suite, for use in reports and diagnostics.
test_format [required] The test format object which will be used to discover and run tests in the test suite. Generally this will be a builtin test format available from the lit.formats module.
test_src_root The filesystem path to the test suite root. For out-of-dir builds this is the directory that will be scanned for tests.
test_exec_root For out-of-dir builds, the path to the test suite root inside the object directory. This is where tests will be run and temporary output files placed.
environment A dictionary representing the environment to use when executing tests in the suite.
suffixes For lit test formats which scan directories for tests, this variable is a list of suffixes to identify test files. Used by: ShTest, TclTest.
substitutions For lit test formats which substitute variables into a test script, the list of substitutions to perform. Used by: ShTest, TclTest.
unsupported Mark an unsupported directory, all tests within it will be reported as unsupported. Used by: ShTest, TclTest.
parent The parent configuration, this is the config object for the directory containing the test suite, or None.
root The root configuration. This is the top-most lit configuration in the project.
on_clone The config is actually cloned for every subdirectory inside a test suite, to allow local configuration on a per-directory basis. The on_clone variable can be set to a Python function which will be called whenever a configuration is cloned (for a subdirectory). The function should takes three arguments: (1) the parent configuration, (2) the new configuration (which the on_clone function will generally modify), and (3) the test path to the new directory being scanned.
Once test suites are located, lit recursively traverses the source directory (following test_src_root) looking for tests. When lit enters a sub-directory, it first checks to see if a nested test suite is defined in that directory. If so, it loads that test suite recursively, otherwise it instantiates a local test config for the directory (see LOCAL CONFIGURATION FILES).
Tests are identified by the test suite they are contained within, and the relative path inside that suite. Note that the relative path may not refer to an actual file on disk; some test formats (such as GoogleTest) define "virtual tests" which have a path that contains both the path to the actual test file and a subpath to identify the virtual test.
When lit loads a subdirectory in a test suite, it instantiates a local test configuration by cloning the configuration for the parent direction -- the root of this configuration chain will always be a test suite. Once the test configuration is cloned lit checks for a lit.local.cfg file in the subdirectory. If present, this file will be loaded and can be used to specialize the configuration for each individual directory. This facility can be used to define subdirectories of optional tests, or to change other configuration parameters -- for example, to change the test format, or the suffixes which identify test files.
The b<lit> output for a test run conforms to the following schema, in both short and verbose modes (although in short mode no PASS lines will be shown). This schema has been chosen to be relatively easy to reliably parse by a machine (for example in buildbot log scraping), and for other tools to generate.
Each test result is expected to appear on a line that matches:
<result code>: <test name> (<progress info>)
where <result-code> is a standard test result such as PASS, FAIL, XFAIL, XPASS, UNRESOLVED, or UNSUPPORTED. The performance result codes of IMPROVED and REGRESSED are also allowed.
The <test name> field can consist of an arbitrary string containing no newline.
The <progress info> field can be used to report progress information such as (1/300) or can be empty, but even when empty the parentheses are required.
Each test result may include additional (multiline) log information in the following format.
<log delineator> TEST '(<test name>)' <trailing delineator> ... log message ... <log delineator>
where <test name> should be the name of a preceeding reported test, <log delineator> is a string of '*' characters at least four characters long (the recommended length is 20), and <trailing delineator> is an arbitrary (unparsed) string.
The following is an example of a test run output which consists of four tests A, B, C, and D, and a log message for the failing test C.
PASS: A (1 of 4) PASS: B (2 of 4) FAIL: C (3 of 4) ******************** TEST 'C' FAILED ******************** Test 'C' failed as a result of exit code 1. ******************** PASS: D (4 of 4)
The lit distribution contains several example implementations of test suites in the ExampleTests directory.
valgrind(1)
Written by Daniel Dunbar and maintained by the LLVM Team (http://llvm.org/).


About my career
My career experience and skills have grown from my hobbies: reading, curiosity. I loved to come up with an idea about consistency between things and how they have been building.
I began my career as a student in a civil engineering school, and after getting my degree. my loving to learn led me to explore new fields in a lot of different majors, So I got a lot of Technical proficiencies include:
- Programming languages: Python, JavaScript, PHP, HTML, and CSS.
- Database: SQL.
- Tools: Node.js and Django, bootstrap.
My goal
My goal now is to find a career in a respectable company that satisfies my abilities and skills ensures a great working atmosphere, and increases my knowledge and experience.
Education
University of Jordan
Bachelor's degree, Civil Engineering · (2015 - 2019)
Abdul Aziz AlGhurair School of Advanced Computing (ASAC) - LTUC
software developer · (2020 - 2021)
Best movies in 2021
- Venom: Let There Be Carnage
- Black Widow
- Fast & Furious 9
- The Matrix 4
- The Eternals
- No Time to Die
- Wrath of Man
- The Conjuring
- Free Guy
- Uncharted


Details
Name: Chimezie Akadonye Stanley
Slack UserName:@stannymezie
Stanley Mezie brief bio
My name is Stanley Akadonye and I am a junior Web Application Developer and Software Developer, currently living in Surulere, Lagos. I have a Bachelor of Science in Statistics from Imo State University, and my primary focus and inspiration for my studies is Technology. I am both driven and self-motivated, and I am constantly experimenting with new technologies and techniques. I am very passionate about Web Development, and strive to better myself as a developer, and the development community as a whole.
Link to #stage1 result : https://github.com/staniventor/hngTest.git


We redefine cats!
- scale dot-com e-markets
- reintermediate B2B architectures
- transition collaborative web services
- strategize clicks-and-mortar action-items
- matrix turn-key eyeballs
- architect scalable e-business
- matrix turn-key action-items
- harness revolutionary communities
- unleash synergistic functionalities
- strategize virtual infomediaries
- engineer out-of-the-box infomediaries
- transition 24/365 vortals
- synergize clicks-and-mortar content


M
d
p
Home
Services
About
Contact
Web Design
&
Development
About
lorem ipsum text placegolder random words and letter and other things what am I saying
Portfolio
123
456
789
abc
def
ghi
jkl
mno
pqr


Images of usability
The most common user action on a Web site is to flee. – Edward Tufte
Images of usability is a theory about usability. It states that there are six definitions or images rather, of usability. Each of these images provide a partial but different view of usability and can be used to generate complementary insight about the usability of systems.
Universal usability seeks to make a system universally easy to use. Situational usability states that the usability is equivalent to the quality-in-use of a system in a specific use situation. Perceived usability is about the users subjective experience with the interaction. Hedonic usability is about the joy of use and emotions related to the interaction. Organizational usability usability implies groups of people working together. Cultural usability states that the usability of a product is dependant on the users cultural background.
Collectively these images can give you a wider scope when it comes to usability testing and make sure that you acknowledge that your users can assume different images.
Read more:
Images of Usability – Morten Hertzum


Sowmya Vajjala, Bodhisattwa Majumder, Anuj Gupta, Harshit Surana
Endorsed by Zachary Lipton, Sebastian Ruder & Marc Najork
Foreword by Julian McAuley
Read the testimonialsPractical NLP focuses squarely on an overlooked demographic: the practitioners and business leaders in industry! While many great books focus on ML’s algorithmic fundamentals, this book exposes the anatomy of real-world systems: from e-commerce applications to virtual assistants. Painting a realistic picture of modern production systems, the book teaches not only deep learning, but also the heuristics and patchwork pipelines that define the (actual) state of the art for deployed NLP systems. The authors zoom out, teaching problem formulation, and aren’t afraid to zoom in on the grimy details, including handling messy data and sustaining live systems. This book will prove invaluable to industry professionals keen to build and deploy NLP in the wild.
This book does a great job bridging the gap between natural language processing (NLP) research and practical applications. From healthcare to e-commerce and finance, it covers many of the most sought-after domains where NLP is being put to use and walks through core tasks in a clear and understandable manner. Overall, the book is a great manual on how to get the most out of current NLP in your industry.
There are two kinds of computer science books on the market: academic textbooks that give you a deep understanding of a domain but can be difficult to access for a non-academic, and "cookbooks" that outline solutions to very specific problems without providing the technical foundations that would allow the reader to generalize the recipes. This book offers the best of both worlds: it is thorough yet accessible. It provides the reader with a solid foundation in natural-language processing,if you would like to go from zero to one in NLP, this book is for you!
There are text books or research papers or books on programming tips, but not a book that tells us how to build an end-to-end NLP system from scratch. I am happy to see this book on “Practical NLP”, which fills this much needed gap. The authors have meticulously, thoughtfully and lucidly covered each and every aspect of NLP that one has to be aware of while building large scale practical systems; at the same time, this book has also managed to cover a large number of examples and varied application areas and verticals. This book is a must for all aspiring NLP engineers, entrepreneurs who want to build companies around language technologies, and also academic researchers who would like to see their inventions reach the real users.
This book bridges the gap between theory and practice by explaining the underlying concepts while keeping in mind varied real-world deployments across different business verticals. There is much hard-fought practical advice from the trenches whether it is about tweaking parameters of open source libraries, setting up data pipelines for building models, or optimizing for fast inference. A must-read for engineers building NLP applications.
I feel this is not only an essential book for NLP practitioners, it is also a valuable reference for the research community to understand the problem spaces in real-world applications. I very much appreciate this book and wish this could be a long-term project with up-to-date NLP applications trending!
This book shows how to put NLP to practice. It bridges the ever widening gap between NLP theory and practical engineering. From fundamentals to hands on code examples of state of the art modeling techniques, this book provides a thoughtful and in-depth experience to the reader. The authors achieved a rare feat by simplifying the esoteric art of design and architecture of production quality machine learning systems. I wish I had access to this book early on in my professional career and evaded the mistakes I made along the way. I am deeply convinced that this book is an essential read for anybody involved in developing a robust, high-performing NLP system.
Practical NLP focuses on how to properly build NLP systems for the real world. Before this book, anyone taking an NLP model past the prototype stage for the first time had to rely on trial and error and a patchwork of blog posts from around the Internet. This book gives a consolidated look at modern practice, starting from an MVP and building up to examples for sophisticated use cases.
The field of Natural Language Processing has undergone a dramatic shift in recent years, both in terms of methodology and in terms of the applications supported. Methodological advances have ranged from new ways of representing documents to new techniques for language synthesis. With these have come new applications ranging from open-ended conversational systems to techniques that use natural language for model interpretability. Finally, these advances have seen natural language processing gain a foothold in related areas, such as computer vision and recommender systems, some of which my lab is working on with support from Amazon, Samsung and the National Science Foundation.
As NLP is expanding into these exciting new areas, so too has the audience of practitioners wanting to make use of NLP techniques. In the Data Science course (CSE 258) I take at UCSD which is often the most attended in the computer science department, I see more and more students are doing their projects on NLP based topics. Rapidly, NLP is becoming a necessary skill required by engineers and product managers, to scientists, students, and enthusiasts wishing to build applications on top of natural language data. On one hand, new tools and libraries for NLP and machine learning have made natural language modeling more accessible than ever. But on the other hand, resources for learning NLP must target this ever-growing and diverse audience. This is especially true for organizations that have recently adopted NLP, or for students working with natural language data for the first time.
It has been my pleasure over the last few years to collaborate with Bodhisattwa Majumder on exciting new applications in natural language processing and dialog, so I was thrilled to hear about his efforts, along with Sowmya Vajjala, Anuj Gupta, Harshit Surana, to write a book on NLP. They have a wide experience in scaling NLP including at early-stage startups, the MIT Media Lab, Microsoft Research, and Google AI.
I am excited by the end-to-end approach taken in their book, which will make it useful for a range of scenarios, and will help readers to work with the labyrinth of possible options while building NLP applications. I am especially thrilled by the focus on modern NLP applications such as chatbots, as well as the focus on interdisciplinary topics such as e-commerce and retail. These topics will be especially useful for industry leaders and researchers, and critically are topics that have been given limited coverage in existing textbooks. This book will be ideal both as a first resource to discover the field of natural language processing, as well as for seasoned practitioners looking to discover the latest developments in this exciting area.


Interest rates (pynance.interest
)¶
-
pynance.interest.
conttogrowth
(contrate)[source]¶ Convert continuous compounding rate to annual growth
-
pynance.interest.
growthfromrange
(rangegrowth, startdate, enddate)[source]¶ Annual growth given growth from start date to end date.
-
pynance.interest.
growthtocont
(annualgr)[source]¶ Convert annual growth to continuous compounding rate
-
pynance.interest.
loanpayment
(amount, rate, npmts)[source]¶ Amount of a constant loan payment.
Parameters: amount : float
amount of loan
rate : float
interest rate for the given payment, i.e., monthly interest if the loan is to be paid off monthly.
npmts : int
number of payments to be made.
Returns: out : float
amount to be paid each period.
-
pynance.interest.
pvannuity
(rate, npmts, amt=1.0)[source]¶ Present value of n payments of a given size given an interest rate per payment interval of rate.
Changed in version 0.3.0: amt can be specified in function call.
Parameters: rate : float
Interest rate per payment period. Note that if payments are monthly and known interest rate is annual, rate must be calculated as effective monthly interest.
npmts : int
Number of payments.
amt : float, optional
Amount of each payment. Defaults to 1.
-
pynance.interest.
retfromrange
(rangeret, startdate, enddate)[source]¶ Annual return given return from start date to end date.


Actually looking forward to getting home knowing full well that a postponed garbage disposal fix awaits. Not a top 10 work day I guess.
8/11/2009, 4:14:36 PM
Favs: 0
Retweets: 0
link--- layout: tweet ---
Actually looking forward to getting home knowing full well that a postponed garbage disposal fix awaits. Not a top 10 work day I guess.
8/11/2009, 4:14:36 PM
Favs: 0
Retweets: 0
link


One or more tags assigned to the resource. Tags are specified using the format key=value, for example: Project=MyAWSProject
Project=MyAWSProject
Multiple tags should be seperated by a semi-colon: Project=MyAWSProject;Environment=build
Project=MyAWSProject;Environment=build


Universal Oracle
问题描述 :
In computer science, an oracle is something that gives you the answer to a particular question. For this problem, you need to write an oracle that gives the answer to everything. But it’s not as bad as it sounds; you know that 42 is the answer to life, the universe, and everything.
输入:
The input consists of a single line of text with at most 1000 characters. This text will contain only well-formed English sentences. The only characters that will be found in the text are uppercase and lowercase letters, spaces, hyphens, apostrophes, commas, semicolons, periods, and question marks. Furthermore, each sentence begins with a single uppercase letter and ends with either a period or a question mark. Besides these locations, no other uppercase letters, periods, or question marks will appear in the sentence. Finally, every question (that is, a sentence that ends with a question mark) will begin with the phrase “What is…”
输出:
The input consists of a single line of text with at most 1000 characters. This text will contain only well-formed English sentences. The only characters that will be found in the text are uppercase and lowercase letters, spaces, hyphens, apostrophes, commas, semicolons, periods, and question marks. Furthermore, each sentence begins with a single uppercase letter and ends with either a period or a question mark. Besides these locations, no other uppercase letters, periods, or question marks will appear in the sentence. Finally, every question (that is, a sentence that ends with a question mark) will begin with the phrase “What is…”
样例输入:
Let me ask you two questions. What is the answer to life? What is the answer to the universe?
样例输出:
Forty-two is the answer to life. Forty-two is the answer to the universe.
/* 这是昨天比赛很水的题目，而我却没有做出来，真是不应该的； 题目没有看仔细，What 以.结尾不要 回答的，这点注意就OK 发现STL很强大，决定好好学下。 */ #include <iostream> #include <string> #include <cstdio> using namespace std; int main() { string str; while( getline(cin, str) ) { string str1 = "What"; size_t found1; found1 = str.find(str1); int i; while(found1 != string::npos) { int len = str.size(); for(i = found1 + 4; i < len; i++) { if(str[i] == '?') { cout << "Forty-two"; for(int j = found1 + 4; j < i; j++) cout << str[j]; cout << "." << endl; //found1 = i; break; } if(str[i] == '.') { //found1 = i; break; } } found1 = str.find(str1, found1 + (i - 4 - found1)); } } }
参考：http://blog.csdn.net/huixisheng/article/details/5743845
(adsbygoogle = window.adsbygoogle || []).push({});
三叔啊，我想知道门后面是什么
三叔啊，我想知道门后面是什么
三叔啊，我想知道门后面是什么
三叔啊，我想知道门后面是什么
三叔啊，我想知道门后面是什么
三叔啊，我想知道门后面是什么
三叔啊，我想知道门后面是什么
三叔啊，我想知道门后面是什么
三叔啊，我想知道门后面是什么
三叔啊，我想知道门后面是什么
三叔啊，我想知道门后面是什么
三叔啊，我想知道门后面是什么
三叔啊，我想知道门后面是什么
6题应该就是算概率的吧
先从简单的做起，归并排序，二叉树相关的遍历等
第二块代码if(it != mp.end())应改为if(it != mp.end() && (i+1)!=(it->second +1))；因为第二种解法如果数组有重复元素 就不正确
终于AC了！next数组还是不好理解啊，mark
比较基础，找些自信
如何解决overload的问题呢？
大致看了下，算法的时间复杂度没有很本性的提升，算不上高效。
程序输出是对的，呈三角型。原程序是按C++写的，已经改成了C的
比较基础，找些自信
说的就是无向图啊，有向图的算法也是类似的
第二个方法好！
很赞的解答
很好的思路，可以借鉴


--- layout: page title: About header-img: "img/about-bg.png" ---
I am first a child of God, second a husband and then a father. I am an entrepreneur, a career coach, and a student. I always have had a passion to learn software development. I final get a chance to grow and develop in a life long dream.


Mexico is rad and the Cenotes are so unbelievably cool! They are underground caves full of crystal clear water.
Hawaii is an amazing place. If I could be anywhere right now, I would be snorkeling on one of their beaches, getting blasted by the sun.
Japan is
so cool! They embrace technology and have so many wonderful
bits to offer. I visited there in highschool and I would really love
to go


“‘Your allotted time has long since expired, Thol of Gharphut,’ rasped a bulbous looking guard of the Garden of Mhersa, on Mars, eyeing my shocking nakedness with marked disapproval. ‘Go at once to the Laboratory and make your report, then present yourself to the Grand Ghazza of the Supreme Interplanetary Council’.“—Don Juan, Don Juan Visits The Planet Mars


We're sorry but okr-tracker doesn't work properly without JavaScript enabled. Please enable it to continue.


WritePreferenceDouble()
语法
WritePreferenceDouble(Key$, Value.d)概要
Creates or changes the specified key and its associated double value under the form: 'Key$ = Value' in the preference file, previously created with CreatePreferences() or opened with OpenPreferences().
参数
Key$ The key name to write. If PreferenceGroup() has been used, then the write is restricted to the current group. If the key was already created, its associated value is replaced with the new specified value. Value The double value to associate with the key.
返回值
无.
示例
See the example at WritePreferenceFloat()
参阅
WritePreferenceFloat(), WritePreferenceInteger(), WritePreferenceLong(), WritePreferenceQuad(), WritePreferenceString()
已支持操作系统
所有


{{also|Appendix:Variations of "so"}}
==English==
{{wikipedia}}
===Etymology 1===
From {{inh|en|enm|so}}, {{m|enm|swo}}, {{m|enm|zuo}}, {{m|enm|swa}}, {{m|enm|swe}}, from {{inh|en|ang|swā}}, {{m|ang|swǣ}}, {{m|ang|swē|t=so, as, the same, such, that}}, from {{inh|en|gem-pro|*swa}}, {{m|gem-pro|*swē|t=so}}, from {{der|en|ine-pro|*swé|*swē, *swō}} (reflexive pronomial stem). Cognate with {{cog|sco|sae||so}}, {{cog|fy|sa||so}}, {{cog|nds|so||so}}, {{cog|nl|zo||so}}, {{cog|de|so||so}}, {{cog|da|så||so}}, {{cog|nn|so}}, [[Swedish]] ''[[så]]'' ("so, such that"), Old {{cog|la|suad||so}}, {{cog|sq|sa||how much, so, as}}, {{cog|grc|ὡς||as}}.
====Pronunciation====
* {{a|UK}} {{enPR|sō}}, {{IPA|en|/səʊ/}}
* {{a|US}} {{IPA|en|/soʊ/}}
* {{audio|en|en-us-so.ogg|Audio (US)}}
* {{rhymes|en|əʊ}}
* {{homophones|en|sew|soh|sow|soy}} {{qualifier|some non-standard dialects}}
====Conjunction====
{{en-con}}
# In [[order]] [[that]].
#: {{ux|en|Eat your broccoli '''so''' you can have dessert.}}
 This is a rich man's summer ‘cottage’{{nb...}}.” '''So''' I started to back away again into the bushes. But I hadn't backed more'n a couple of yards when I see something so amazing that I couldn't help scooching down behind the bayberries and looking at it.}}
#: {{ux|en|I was hungry '''so''' I asked if there was any more food.}}
#: {{ux|en|He ate too much cake, '''so''' he fell ill.}}
#: {{ux|en|He wanted a book, '''so''' he went to the library.}}
#: {{ux|en|“I need to go to the bathroom.”
―“'''So''' go!”}}
# {{lb|en|archaic}} [[provided|Provided]] that; on condition that, as long as.
#* '''1594''', {{w|William Shakespeare}}, ''{{w|The Two Gentlemen of Verona}}'', Act III, Scene 1,[http://www.opensourceshakespeare.org/views/plays/play_view.php?WorkID=twogents&Scope=entire&pleasewait=1&msg=pl]
#*: ''Speed''. ‘Item: She doth talk in her sleep.’
#*: ''Launce''. It’s no matter for that, '''so''' she sleep not in her talk.
#* {{RQ:Florio Montaigne Essayes|chapter=18|book=II|passage=As we cal money not onely that which is true and good, but also the false; '''so''' it be currant.}}
#* '''1644''', {{w|John Milton}}, ''{{w|Areopagitica}}'', London, p. 35,[http://name.umdl.umich.edu/A50883.0001.001]
#*: {{...}} though all the windes of doctrin were let loose play upon the earth, '''so''' Truth be in the field, we do injuriously by licencing and prohibiting to misdoubt her strength.
#* '''1743''', {{w|Robert Drury (sailor)|Robert Drury}}, ''The Pleasant, and Surprizing Adventures of Mr. Robert Drury, during his Fifteen Years Captivity on the Island of Madagascar'', London, p. 111,[https://archive.org/details/pleasantandsurp00drurgoog]
#*: I went away very well satisfy’d, not caring where I was sent, '''so''' it was but out of his Sight; for he now became more my Aversion than ever.
=====Usage notes=====
Chiefly in North American use, a [[comma]] or [[pause]] is often used before the conjunction when used in the sense ''with the result that''. (A similar meaning can often be achieved by using a [[semicolon]] or [[colon]] (without the '''''so'''''), as for example: ''He drank the poison; he died.'')
=====Synonyms=====
* {{sense|in order that}} {{l|en|so that}}, {{l|en|that}}
=====Translations=====
{{trans-top|in order that}}
* Catalan: {{t+|ca|perquè}} {{qualifier|followed by the subjunctive}}
* Chinese:
*: Mandarin: {{t+|cmn|以便|tr=yǐbiàn|sc=Hani}}
* Czech: {{t+|cs|aby}}
* Danish: {{t+|da|så}}
* Dutch: {{t+|nl|zodat}}, {{t+|nl|zodoende}}
* Esperanto: {{t|eo|por ke}}
* Finnish: {{t+|fi|jotta}}
* French: {{t+|fr|afin que}} {{qualifier|followed by the [[subjunctive]]}}, {{t+|fr|pour que}} {{qualifier|followed by the subjunctive}}
* Georgian: {{t-needed|ka}}
* German: {{t+|de|damit}}, {{t+|de|sodass}}, {{t|de|[[um]] ... [[zu]]}}
* Greek: {{t|el|[[για]] [[να]]}}
*: Ancient: {{t|grc|ἵνα}}, {{t|grc|ὡς}}
* Hungarian: {{t+|hu|hogy}} {{qualifier|followed by the imperative}}, {{t|hu|azért, hogy}}
* Italian: {{t+|it|perché}} {{qualifier|followed by the subjunctive}}, {{t+|it|affinché}}
* Japanese: {{t+|ja|ため|tr=tame ni|alt=ために|sc=Jpan}}
{{trans-mid}}
* Korean: {{t+|ko|위해|alt=하기 위해}}, {{t+|ko|으로}}
* Lao: {{t-needed|lo}}
* Latin: {{t+|la|ut}}
* Malay: {{t|ms|jadi}}, {{t|ms|supaya}}, {{t+|ms|agar}}
* Mongolian: {{t-needed|mn}}
* Norwegian: {{t+|no|så}}
* Novial: {{t|nov|por}}
* Pashto: {{t+|ps|چې|tr=če}}
* Polish: {{t+|pl|aby}}
* Portuguese: {{t|pt|para que}}
* Romanian: {{t+|ro|așadar|alt=aşadar}}
* Russian: {{t+|ru|что́бы|tr=štóby}}
* Scottish Gaelic: {{t|gd|mar sin}}
* Spanish: [[para]] [[que]] {{qualifier|followed by the subjunctive}}
* Swedish: {{t+|sv|så}}
* Thai: {{t+|th|เพื่อ}}
* Ukrainian: {{t+|uk|аби}}, {{t+|uk|щоб}}
* Vietnamese: {{t|vi|để cho}}
{{trans-bottom}}
{{trans-top|with the result that}}
* Arabic: {{t+|ar|فَـ|tr=fa-}}, {{t|ar|لِذَا|tr=li-ḏā}}
* Armenian: {{t+|hy|ուստի}} {{qualifier|formally}}
* Catalan: {{t+|ca|així que}}
* Chinese:
*: Mandarin: {{t+|cmn|所以|tr=suǒyǐ|sc=Hani}}, {{t+|cmn|因此|tr=yīncǐ|sc=Hani}}
* Czech: {{t+|cs|tak}}
* Dutch: {{t+|nl|dus}}
* Finnish: {{t+|fi|joten}}, {{t+|fi|niinpä}}
* French: {{t+|fr|alors}}, {{t+|fr|donc}}
* Galician: {{t|gl|logo}}, {{t|gl|entón}}
* Georgian: {{t-needed|ka}}
* German: {{t+|de|so}}
* Greek: {{t|el|[[για|γι']] [[αυτό]]}}
*: Ancient: {{t|grc|ὥστε}} {{qualifier|usually + infinitive}}
* Hungarian: {{t+|hu|úgyhogy}}, {{t+|hu|így}}, {{t+|hu|ezért}}
* Indonesian: {{t+|id|jadi}}
* Italian: {{t+|it|allora}}
* Japanese: {{t+|ja|だから|tr=dakara|sc=Jpan}}
{{trans-mid}}
* Korean: {{t+|ko|그래서}}
* Lao: {{t-needed|lo}}
* Latin: {{t|la|igitur}}
* Malay: {{t|ms|jadi}}
* Mongolian: {{t-needed|mn}}
* Pashto: {{t+|ps|نو|tr=no}}
* Polish: {{t+|pl|więc}}, {{t+|pl|dlatego}}, {{t+|pl|toteż}}, {{t+|pl|przeto}}, {{t|pl|tak że}}, {{t+|pl|zatem}}
* Portuguese: {{t+|pt|então}}
* Romanian: {{t+|ro|deci}}
* Russian: {{t+|ru|и}}, {{t+|ru|поэ́тому}}, {{t+|ru|та́к что|tr=ták što}}
* Sardinian:
*: Campidanese: {{t|sc|intzàndus}}
*: Logudorese: {{t|sc|assora}}, {{t|sc|tando}}
*: Sassarese: {{t|sdc|tandu}}
* Slovak: {{t|sk|takže}}
* Spanish: {{t|es|así que}}
* Swedish: {{t+|sv|så}}, {{t+|sv|därför}}
* Thai: {{t+|th|ดังนั้น|tr=dang nán}}
* Ukrainian: {{t|uk|тому́}}, {{t|uk|так що}}
* Vietnamese: {{t+|vi|nên}}, {{t|vi|thế nên}}, {{t|vi|vậy nên}}, {{t|vi|thành ra}}, {{t+|vi|thành thử}}
{{trans-bottom}}
====Adverb====
{{en-adv|-}}
# To the (explicitly stated) extent [[that]].
#: {{ux|en|It was '''so''' hot outside that all the plants died. {{nowrap|He was '''so''' good, they hired him on the spot.}}}}
#* {{quote-book|en|year=1913|author={{w|Joseph C. Lincoln}}|chapter=1
|title=[http://openlibrary.org/works/OL5535161W Mr. Pratt's Patients]
|passage=Thinks I to myself, “Sol, you're run off your course again. This is a rich man's summer ‘cottage’{{nb...}}.” So I started to back away again into the bushes. But I hadn't backed more'n a couple of yards when I see something '''so''' amazing that I couldn't help scooching down behind the bayberries and looking at it.}}
#* {{quote-journal|en|date=2013-07-20|volume=408|issue=8845|magazine={{w|The Economist}}
|title=[http://www.economist.com/news/science-and-technology/http://www.economist.com/news/science-and-technology/21581980-latest-research-suggests-humans-are-not-warriors-their-genes-after-all-old Old soldiers?]
|passage=Whether modern, industrial man is less or more warlike than his hunter-gatherer ancestors is impossible to determine. The machine gun is '''so''' much more lethal than the bow and arrow that comparisons are meaningless.}}
# {{lb|en|informal}} To the (implied) [[extent]].
#: {{ux|en|I need a piece of cloth '''so''' long. [{{=}} ''this'' long]}}
#* {{quote-book|en|year=1898|author={{w|Winston Churchill (novelist)|Winston Churchill}}
|title={{w|The Celebrity}}|chapter=2
|passage=We drove back to the office with some concern on my part at the prospect of '''so''' large a case. Sunning himself on the board steps, I saw for the first time Mr. Farquhar Fenelon Cooke.}}
## {{lb|en|informal}} [[very|Very]] (positive clause).
##: {{ux|en|He is '''so''' good!}}
##* {{RQ:EHough PrqsPrc|I|0105}}
##*: Captain Edward Carlisle{{...}}felt a curious sensation of helplessness seize upon him as he met her steady gaze,{{nb...}}; he could not tell what this prisoner might do. He cursed the fate which had assigned such a duty, cursed especially that fate which forced a gallant soldier to meet '''so''' superb a woman as this under handicap '''so''' hard.
## {{lb|en|informal}} [[very|Very]] (negative clause).
##: {{ux|en|It’s not '''so''' bad. [i.e. it's acceptable]}}
## {{lb|en|slang|chiefly|US}} Very much.
##: {{ux|en|But I '''so''' want to see the Queen when she visits our town! That is '''so''' {{nowrap|not true!}}}}
##* {{RQ:Jefferies Amateur Poacher|chapter=1|passage=Molly the dairymaid came a little way from the rickyard, and said she would pluck the pigeon that very night after work. She was always ready to do anything for us boys; and we could never quite make out why they scolded her '''so''' for an idle hussy indoors. It seemed so unjust.}}
##* '''1963''', Mike Hawker, {{w|Ivor Raymonde}} (music and lyrics), {{w|Dusty Springfield}} (vocalist), ''{{w|I Only Want to Be with You}}'' (single),
##*: Don′t know what it is that makes me love you '''so''', / I only know I never want to let you go.
##*{{quote-av|en||{{w|Andrea Baker|Andrea Taylor}}|{{w|Totally Spies!}}|2|9||Yeah! Not eating is '''so''' 90’s!|role=Clover|episode=I, Dude|writers=Michael Stokes|network={{w|Teletoon}}|publisher={{w|Marathon Media}}|date=Apr 16 2003}}
# In a particular [[manner]].
#: {{ux|en|Place the napkin on the table just '''so'''. If that's what you mean, then say '''so'''; (or '''do so''').}}
# In the same manner or to the same extent as aforementioned; also.
#: {{ux|en|Just as you have the right to your free speech, '''so''' I have the right to mine. {{nowrap|Many people say she's the world's greatest athlete, but I don't think '''so'''.}} {{nowrap|"I can count backwards from one hundred." "'''So''' can I."}}}}
#* '''1883''', {{w|Howard Pyle}}, ''{{w|The Merry Adventures of Robin Hood}}'' [[s:The Merry Adventures of Robin Hood/Chapter V|Chapter V]]
#*: "Good morrow to thee, jolly fellow," quoth Robin, "thou seemest happy this merry morn." ¶ "Ay, that am I," quoth the jolly Butcher, "and why should I not be '''so'''? Am I not hale in wind and limb? Have I not the bonniest lass in all Nottinghamshire? And lastly, am I not to be married to her on Thursday next in sweet Locksley Town?"
#* {{quote-journal|en|date=May 19, 2012|author=Paul Fletcher|work=BBC Sport
|title=[http://www.bbc.co.uk/sport/0/football/18044378 Blackpool 1-2 West Ham]
|passage=It was a goal that meant West Ham won on their first appearance at Wembley in 31 years, in doing '''so''' becoming the first team since Leicester in 1996 to bounce straight back to the Premier League through the play-offs.}}
# {{sense|with [[as]]}} To such an extent or degree; [[as]].
#: {{ux|en|'''so''' far as; '''so''' long as; '''so''' much as}}
=====Usage notes=====
* Use of '''''so''''' in the sense ''to the '''implied''' extent'' is discouraged in formal writing; spoken intonation which might render the usage clearer is not usually apparent to the reader, who might reasonably expect the ''extent'' to be made explicit. For example, the reader may expect ''He is '''so''' good'' to be followed by an explanation or consequence of how good ''he'' is. Devices such as use of underscoring and the [[exclamation mark]] may be used as a means of clarifying that the implicit usage is intended; capitalising ''SO'' is also used. The derivative subsenses ''very'' and ''very much'' are similarly more apparent with spoken exaggerated intonation.
* The difference between ''so'' and ''very'' in implied-extent usage is that ''very'' is more descriptive or matter-of-fact, while ''so'' indicates more emotional involvement. For example, ''she is very clever'' is a simple statement of opinion; ''she is so clever'' suggests admiration. Likewise, ''that is very typical'' is a simple statement; ''that is SO typical of him!'' is an indictment. A formal (and reserved) apology may be expressed ''I am very sorry'', but after elbowing someone in the nose during a basketball game, a man might say, ''Dude, I am so sorry!'' in order to ensure that it's understood as an accident.[Mark Liberman, [http://languagelog.ldc.upenn.edu/nll/?p=3866 "Ask Language Log: So feminine?"], 2012 March 26]
=====Synonyms=====
* {{sense|very}} {{l|en|really}}, {{l|en|truly}}, {{l|en|that}}, {{l|en|very}}
* {{sense|to a particular extent}} {{l|en|that}}, {{l|en|this}}, {{l|en|yea}}
* {{sense|in a particular manner}} {{l|en|like}} [[this]], [[thus]]
* {{sense|slang: very much}} {{l|en|really}}, {{l|en|truly}}, {{l|en|very}} [[much]]
=====Derived terms=====
{{der-top}}
* {{l|en|or so}}
* {{l|en|so-so}}
* {{l|en|so on}}
* {{l|en|so forth}}
{{der-mid}}
* {{l|en|so much}}
* {{l|en|so there}}
* {{l|en|so what}}
{{der-bottom}}
=====Translations=====
{{trans-top|very}}
* Catalan: {{t+|ca|tan}}
* Chinese:
*: Cantonese: {{t|yue|好|tr=hou2|sc=Hani}}
*: Mandarin: {{t+|cmn|很|tr=hěn|sc=Hani}}, {{t+|cmn|非常|tr=fēicháng|sc=Hani}}, {{t+|cmn|太|tr=tài|sc=Hani}}
* Czech: {{t+|cs|tak}}
* Danish: {{t+|da|så}}
* Dutch: {{t+|nl|zo}}, {{t+|nl|zodanig}}
* Esperanto: {{t+|eo|tiel}}
* Finnish: {{t+|fi|niin}}
* French: {{t+|fr|tellement}}, {{t+|fr|vraiment}}, {{t+|fr|si}}
* German: {{t+|de|so}}, {{t+|de|sehr}}
* Greek: {{t+|el|τόσο}}
*: Ancient: {{t|grc|ὡς}}, {{t|grc|οἷον}}
* Hebrew: {{t|he|כל כך}}
* Hungarian: {{t+|hu|olyan}}, {{t+|hu|annyira}}
* Italian: {{t+|it|tanto}}, {{t+|it|veramente}}
* Japanese: {{t+|ja|とても|tr=totemo|sc=Jpan}}
* Korean: {{t+|ko|너무}}, {{t+|ko|매우}}
* Latin: {{t+|la|tam}}
{{trans-mid}}
* Malay: {{t|ms|sangat}}, {{t|ms|-nya}}
* Norwegian: {{t+|no|så}}
* Novial: {{t|nov|tantim}}, {{t|nov|tre}}
* Old English: {{t|ang|swā}}
* Polish: {{t+|pl|tak}}
* Portuguese: {{t+|pt|tão}}
* Romanian: {{t+|ro|atât}}
* Russian: {{t+|ru|о́чень}}, {{t+|ru|так}}
* Scottish Gaelic: {{t|gd|cho}}
* Slovene: {{t+|sl|tako}}
* Spanish: {{t+|es|tan}}
* Swedish: {{t+|sv|så}}
* Turkish: {{t+|tr|o kadar}}
* Ukrainian: {{t|uk|ду́же}}
* Vietnamese: {{t+|vi|rất}}, {{t+|vi|lắm}}, {{t+|vi|lém}}
* Volapük: {{t+|vo|so}}
* Walloon: {{t+|wa|si}}, {{t+|wa|si télmint}}
{{trans-bottom}}
{{trans-top|to a particular extent}}
* Armenian: {{t+|hy|այնքան}}
* Belarusian: {{t|be|так}}
* Bulgarian: {{t+|bg|така́}}
* Catalan: {{t+|ca|tan}}
* Chinese:
*: Cantonese: {{t+|yue|咁|tr=gam3|sc=Hani}}
*: Mandarin: {{t+|cmn|這麼|sc=Hani}}, {{t+|cmn|这么|tr=zhème|sc=Hani}}, {{t+|cmn|那麼|sc=Hani}}, {{t+|cmn|那么|tr=nàme|sc=Hani}}
* Czech: {{t+|cs|tak}}, {{t+|cs|takto}}, {{t+|cs|takhle}}
* Danish: {{t+|da|så}}
* Dutch: {{t+|nl|zo}}
* Esperanto: {{t+|eo|tiom}}
* Finnish: {{t+|fi|niin}}
* French: {{t+|fr|aussi}}
* Georgian: {{t|ka|იმდენად}}
* German: {{t+|de|so}}
* Greek: {{t+|el|τόσο}}
*: Ancient: {{t|grc|ὅσον}}
* Hindi: {{t+|hi|इतना|tr=itnā}}
* Hungarian: {{t+|hu|olyan}}, {{t+|hu|annyira}}, {{t+|hu|ilyen}}, {{t|hu|ennyire}}
* Irish: {{t|ga|chomh}}
* Italian: {{t+|it|tanto}}, {{t+|it|così}}
* Japanese: {{t+|ja|そう|tr=sō|sc=Jpan}}, {{t+|ja|こんな|tr=konna ni|alt=こんなに|sc=Jpan}}, {{t|ja|[[それ]]ほど|tr=sorehodo|sc=Jpan}}, {{t|ja|この[[よう]]に|tr=kono yō ni|sc=Jpan}}
* Korean: {{t+|ko|그렇게}}
* Lao: {{t-needed|lo}}
{{trans-mid}}
* Latin: {{t+|la|tam}}
* Macedonian: {{t|mk|та́ка}}
* Mongolian: {{t-needed|mn}}
* Norwegian: {{t+|no|så}}
* Novial: {{t|nov|tantim}}
* Old English: {{t|ang|swā}}
* Polish: {{t+|pl|tak}}
* Portuguese: {{t+|pt|tão}}
* Romanian: {{t+|ro|atât}}
* Russian: {{t+|ru|так}}
* Scottish Gaelic: {{t|gd|cho}}
* Serbo-Croatian:
*: Cyrillic: {{t|sh|та̀ко̄|sc=Cyrl}}
*: Roman: {{t+|sh|tàkō}}
* Slovak: {{t|sk|tak}}, {{t|sk|takto}}
* Slovene: {{t+|sl|tako}}
* Spanish: {{t+|es|tan}}
* Swedish: {{t+|sv|så}}
* Thai: {{t+|th|มาก}}
* Turkish: {{t+|tr|kadar}}
* Ukrainian: {{t+|uk|так}}
* Urdu: {{t+|ur|اتنا|tr=itnā|sc=ur-Arab}}
* Vietnamese: {{t+|vi|vậy}}, {{t+|vi|như vậy}}
* Walloon: {{t+|wa|si}}
{{trans-bottom}}
{{trans-top|in a particular manner}}
* Catalan: {{t+|ca|així}}
* Chinese:
*: Cantonese: {{t|yue|噉樣|sc=Hani}}, {{t|yue|噉样|tr=gam2 joeng6-2|sc=Hani}}
*: Mandarin: {{t+|cmn|這樣|sc=Hani}}, {{t+|cmn|这样|tr=zhèyàng|sc=Hani}}, {{t+|cmn|如此|tr=rúcǐ|sc=Hani}}
* Czech: {{t+|cs|tak}}
* Dalmatian: {{t|dlm|coisa}}
* Danish: {{t+|da|sådan}}
* Dutch: {{t+|nl|zo}}, {{t+|nl|zodanig}}
* Esperanto: {{t+|eo|tiel}}
* Finnish: {{t+|fi|niin}}, {{t+|fi|siten}}, {{t+|fi|täten}}
* French: {{t+|fr|ainsi}}, {{t+|fr|comme ça}}
* Friulian: {{t|fur|cussì}}
* German: {{t+|de|so}}
* Greek: {{t+|el|έτσι}}
* Hindi: {{t+|hi|ऐसा|tr=aisā}}
* Hungarian: {{t+|hu|úgy}}, {{t+|hu|így}}
* Icelandic: {{t+|is|svona}}
* Istriot: {{t|ist|cussèi}}
* Italian: {{t+|it|così}}
* Japanese: {{t|ja|この[[よう]]に|tr=sono yō ni|sc=Jpan}}
{{trans-mid}}
* Korean: {{t+|ko|그렇게}}
* Lao: {{t-needed|lo}}
* Latin: {{t|la|sic}}
* Maori: {{t|mi|pēnā}}
* Norwegian: {{t+|no|slik}}
* Novial: {{t|nov|talim}}
* Old English: {{t|ang|swā}}
* Polish: {{t+|pl|tak}}
* Portuguese: {{t+|pt|assim}}
* Romanian: {{t+|ro|așa}}
* Russian: {{t+|ru|так}}
* Slovene: {{t+|sl|tako}}
* Spanish: {{t+|es|así}}
* Swedish: {{t+|sv|så}}
* Thai: {{t|th|เพื่อให้|tr=pêua hâi}}
* Turkish: {{t+|tr|böyle}}, {{t+|tr|şöyle}}, {{t+|tr|öyle}}
* Ukrainian: {{t+|uk|так}}
* Venetian: {{t|vec|cusì}}
* Walloon: {{t+|wa|insi}}, {{t+|wa|inla}}, {{t|wa|come çoula}}, {{t|wa|come ça}}
{{trans-bottom}}
{{trans-top|slang: very much}}
* Catalan: {{t+|ca|tan}}
* Czech: {{t+|cs|tak}}
* Danish: {{t+|da|så}}
* Esperanto: {{t+|eo|tre}}
* Finnish: {{t+|fi|tosi}}
* French: {{t+|fr|tellement}}
* Hebrew: {{t|he|כל כך}}
* Hungarian: {{t+|hu|annyira}}
{{trans-mid}}
* Novial: {{t|nov|tre}}, {{t|nov|tre multim}}
* Portuguese: {{t+|pt|tão}}
* Romanian: {{t+|ro|atât}}
* Russian: {{t+|ru|о́чень}}, {{t+|ru|так}}
* Swedish: {{t+|sv|så}}
* Ukrainian: {{t|uk|ду́же}}, {{t+|uk|так}}
{{trans-bottom}}
{{checktrans-top}}
* Ido: {{t+check|io|tante}}
{{trans-mid}}
{{trans-bottom}}
=====References=====
====Adjective====
{{en-adj|-}}
# [[true|True]], [[accurate]].
#: {{ux|en|That is '''so'''. {{nowrap|You are responsible for this, is that not '''so'''?}}}}
#* {{RQ:Frgsn Zlnstn|IV}}
#*: “My Continental prominence is improving,” I commented dryly. ¶ Von Lindowe cut at a furze bush with his silver-mounted rattan. ¶ “Quite '''so''',” he said as dryly, his hand at his mustache. “I may say if your intentions were known your life would not be worth a curse.”
# In that state or manner; with that attribute. {{non-gloss definition|A [[proadjective]] that replaces the aforementioned [[adjective phrase]].}}
#* '''1823''', {{w|Andrew Reed (minister)|Andrew Reed}}, ''Martha''
#*: If this separation was painful to all parties, it was most '''so''' to Martha.
#* '''1872''', {{w|Charles Dickens}}, J., ''The Personal History of {{w|David Copperfield}}''
#*: But if I had been more fit to be married, I might have made you more '''so''' too.
#* '''1947''', Liberty Hyde Bailey, ''The Standard Cyclopedia of Horticulture''
#*: It must be understood that while the nelumbiums are hardy, they are '''so''' only as long as the tubers are out of the reach of frost.
# {{lb|en|dated|UK|slang}} [[homosexual|Homosexual]].
#: {{ux|en|Is he '''so'''?}}
=====Synonyms=====
* {{sense|true}} {{l|en|correct}}, {{l|en|right}}, {{l|en|true}}
* {{sense|euphemistic: homosexual}} {{l|en|musical}}, {{l|en|one of the family}}, {{l|en|one of them}}, {{l|en|that way inclined}}
=====Derived terms=====
* {{l|en|make it so}}
* {{l|en|more so}}
=====Translations=====
{{trans-top|true}}
* Burmese: {{t+|my|ဟုတ်|sc=Mymr}}
* Catalan: {{t+|ca|això}}, {{t+|ca|açò}}
* Czech: {{t+|cs|tak}}
* Danish: {{t+|da|sådan}}
* Finnish: {{t+|fi|näin}}, {{t+|fi|niin}}
* German: {{t+|de|so}}
* Greek:
*: Ancient: {{t|grc|οὕτως}}, {{t|grc|ὡς}}
{{trans-mid}}
* Hungarian: {{t+|hu|igaz}}, {{t|hu|így van}}
* Japanese: {{t+|ja|そう|tr=sō|sc=Jpan}}
* Korean: {{t+|ko|그래}}
* Portuguese: {{t+|pt|assim}}
* Russian: {{t+|ru|так}}
{{trans-bottom}}
{{trans-top|in that state}}
* Finnish: {{t+|fi|sellainen}}
* French: {{t+|fr|le}}
* Greek:
*: Ancient: {{t|grc|τοιοῦτος}}, {{t|grc|τοιόσδε}}, {{t|grc|οἷος}}, {{t|grc|τοῖος}} {{qualifier|poetic}}
{{trans-mid}}
* Japanese: {{t+|ja|そう|tr=sō|sc=Jpan}}
* Russian: {{t+|ru|тако́й}}
{{trans-bottom}}
====Interjection====
{{en-interj}}
# {{n-g|Used after a pause for thought to introduce a new [[topic]], [[question]] or [[story]].}}
#: {{syn|en|look|well|see|hey}}
#: {{ux|en|'''So''', let's go home.}}
#: {{ux|en|'''So''', what'll you have?}}
#: {{ux|en|'''So''', there was this squirrel stuck in the chimney...}}
#* {{quote-book|en|year=1913|author={{w|Joseph C. Lincoln}}|chapter=11
|title=[http://openlibrary.org/works/OL5535161W Mr. Pratt's Patients]
|passage='''So''', after a spell, he decided to make the best of it and shoved us into the front parlor.  — "'''So'''?"}}
# {{n-g|Used to connect previous conversation or events to the following question.}}
#: {{ux|en|So how does this story end?}}
#: {{ux|en|So, everyone wants to know - did you win the contest or not?}}
# {{lb|en|archaic}} Be as you are; stand still; {{n-g|used especially to cows; also used by sailors.}}
=====Usage notes=====
Though common for a long time, the "sentence-initial so" became controversial in the mid-2010s.[[https://www.npr.org/2015/09/03/432732859/so-whats-the-big-deal-with-starting-a-sentence-with-so So, What's The Big Deal With Starting A Sentence With 'So'?]]
=====Translations=====
{{trans-top|interjection used to introduce a new topic}}
* Arabic: {{t|ar|يَعْنِي}}
* Basque: {{t|eu|ba}}
* Catalan: {{t+|ca|així}}, {{t|ca|doncs}}
* Chinese:
*: Mandarin: {{t+|cmn|那麼|sc=Hani}}, {{t+|cmn|那么|tr=nàme|sc=Hani}}
* Danish: {{t+|da|så}}
* Dutch: {{t+|nl|dus}}
* Finnish: {{t+|fi|eli}}
* French: {{t+|fr|alors}}, {{t+|fr|du coup}}
* German: {{t+|de|also}}
* Greek: {{t+|el|λοιπόν}}
* Hebrew: {{t+|he|אז|tr=az}}
* Hindi: {{t+|hi|तो|tr=to}}
{{trans-mid}}
* Hungarian: {{t+|hu|na}}, {{t+|hu|és}}, {{t+|hu|no}}, {{t+|hu|nos}}, {{t+|hu|akkor}}, {{t|hu|hát akkor}}
* Italian: {{t+|it|allora}}
* Japanese: {{t+|ja|そう|tr=sō|sc=Jpan}}, {{t|ja|では|tr=dewa|sc=Jpan}}, {{t+|ja|じゃ|tr=ja|sc=Jpan}}
* Latin: {{t+|la|ergo}}
* Malay: {{t|ms|jadi}}
* Persian: {{t+|fa|پس|tr=pas|sc=fa-Arab}}, {{t+|fa|باری|tr=bâri|sc=fa-Arab}}
* Polish: {{t|pl|tak więc}}, {{t+|pl|zatem}}, {{t|pl|cóż, więc}}, {{t+|pl|no}}, {{t|pl|no i}}
* Portuguese: {{t+|pt|então}}, {{t+|pt|aí}}, {{t+|pt|daí}}
* Russian: {{t+|ru|так}}, {{t+|ru|ита́к}}
* Spanish: {{t+|es|pues}}, {{t+|es|entonces}}
* Swedish: {{t+|sv|så}}
* Ukrainian: {{t|uk|отже}}
* Urdu: {{t|ur|تو|tr=to|sc=ur-Arab}}
{{trans-bottom}}
{{trans-top|short for so what}}
* Danish: {{t+|da|og}}
* Finnish: {{t+|fi|ja}}
{{trans-mid}}
* Hungarian: {{t|hu|na és}}, {{t|hu|és akkor}}, {{t|hu|és aztán}}, {{t|hu|na és aztán}}
* Swedish: {{t+|sv|och}}
{{trans-bottom}}
====Pronoun====
{{head|en|pronoun}}
# {{abbreviation of|en|[[someone]]}}
=====Synonyms=====
* {{l|en|sb|t=somebody}}
===Etymology 2===
Shortened from {{m|en|sol}}, to make it an [[open syllable]] for uniformity with the rest of the scale.
====Noun====
{{en-noun}}
# {{lb|en|music}} A syllable used in [[solfège]] to represent the fifth note of a [[major scale]].
=====Translations=====
{{trans-see|sol}}
===Etymology 3===
Borrowed from {{bor|en|ja|蘇|tr=so}}.
====Noun====
{{en-noun|-}}
# {{lb|en|foods}} A type of [[dairy]] product made in [[Japan]] between the seventh and 10th centuries.
===See also===
* {{pedia|So (dairy product)}}
* {{projectlink|commons|File:Kodai no So.JPG}}
===Anagrams===
* {{anagrams|en|a=os|-os|-os-|O&S|O's|O. S.|O.S.|OS|OS.|Os|o's|o.s.|os}}
[[Category:English basic words]]
[[Category:English coordinating conjunctions]]
[[Category:English degree adverbs]]
[[Category:English demonstrative adverbs]]
[[Category:English discourse markers]]
[[Category:English intensifiers]]
[[Category:English pro-forms]]
[[Category:English two-letter words]]
----
==Aiwoo==
===Verb===
{{head|nfl|verb}}
# to [[stand]] {{gloss|be in a standing position}}
===References===
* {{R:ABVD|lang=Äiwoo|id=501|cite={{cite-journal|author=Ross, M. & Næss, Å.|date=2007|title=An Oceanic origin for Äiwoo, the language of the Reef Islands?|work=Oceanic Linguistics|volume=46|issue=2}}.}}
----
==Asturian==
===Etymology 1===
From {{inh|ast|la|sub}}.
====Preposition====
{{head|ast|preposition}}
# [[under]]
=====Derived terms=====
* [[sol]]
===Etymology 2===
From {{inh|ast|la|suus||his, her, its}}
====Adjective====
{{ast-adj|f=so|n=so|mpl=sos|fpl=sos}}
# [[his]], [[her]], [[its]]
# [[your]] (polite)
# [[their]]
====Pronoun====
{{head|ast|pronoun}}
# [[his]], [[hers]]
# [[yours]] (polite)
====Related terms====
* {{l|ast|suyu}}
===Etymology 3===
====Alternative forms====
* [[soi#Asturian|soi]]
====Verb====
{{ast-verb-form}}
# {{inflection of|ast|ser||1|s|pres|indc}}
----
==Basque==
===Noun===
{{head|eu|noun}}
# [[look]]
----
==Brokskat==
===Pronoun===
{{head|bkk|pronoun}}
# [[he]]
----
==Catalan==
===Etymology===
From {{inh|ca|pro|son}} (compare {{cog|oc|son}}), from {{inh|ca|la|sonus}} (compare {{cog|fr|son}}, {{cog|es|son}}, {{m|es|sueno}}, {{cog|it|suono}}).
===Pronunciation===
* {{ca-IPA}}
===Noun===
{{ca-noun|m|sons}}
# [[sound]]
====Related terms====
* {{l|ca|sonar}}
* {{l|ca|sònic}}
===Further reading===
* {{R:IEC2}}
* {{R:GDLC}}
* {{R:DNV}}
* {{R:DCVB}}
----
==Danish==
===Etymology===
From {{inh|da|non|sýr}}, from {{inh|da|gem-pro|*sūz}}, from {{inh|da|ine-pro|*sū-}}.
===Noun===
{{da-noun|en|søer}}
# [[sow]] (female pig)
# {{lb|da|pejorative}} [[slut]]
====Declension====
{{da-noun-infl|en|søer|søerne}}
===References===
* {{R:DDO}}
----
==Elfdalian==
===Etymology===
From {{der|ovd|non|svá}}, from {{der|ovd|gem-pro|*swa}}, {{m|gem-pro|*swē}}. Cognate with {{cog|sv|så}}.
===Adverb===
{{ovd-adv|cat2=demonstrative adverbs}}
# {{l|en|so}}, like that, in that manner
# so, to such a degree
----
==Esperanto==
===Pronunciation===
* {{audio|eo|LL-Q143 (epo)-Robin van der Vliet-so.wav|Audio}}
===Noun===
{{eo-head}}
# {{Latn-def|eo|name|S|s}}
===See also===
* {{list:Latin script letter names/eo}}
----
==Faroese==
===Etymology===
From {{inh|fo|non|svá}}, from {{inh|fo|gem-pro|*swa}}, {{m|gem-pro|*swē||so}}, from {{inh|fo|ine-pro|*swē}}, {{m|ine-pro|*swō}} (reflexive pronomial stem).
===Pronunciation===
* {{IPA|fo|/soː/}}
* {{rhymes|fo|oː}}
* {{homophones|fo|soð}}
===Adverb===
{{fo-adv|-}}
# {{l|en|so}}, [[thus]], [[as]]
# [[then]]
----
==Folopa==
===Alternative forms===
* {{l|ppo|sou}}
===Noun===
{{head|ppo|noun}}
# [[woman]]
===References===
* Karl James Franklin, ''Pacific Linguistics'' (1973, {{ISBN|0858831007}}, page 130: Polopa ''so''/''sou'' woman, cf. DAR ''sou'' female animal but ''we'' woman.
* Karl J. Franklin, ''[https://web.archive.org/web/20160305070551/http://www-01.sil.org/pacific/png/pubs/10745/Comp_Wordlist_Gulfdistrict.pdf Comparative Wordlist 1 of the Gulf District and adjacent areas]'' (1975), page 15: Boro, Suri, Tebera ''sou'', Sopese ''šo''
* Carol Anderson, ''Beginning Folopa Language Lessons and Simple Glossary'' (2010) (as ''so'')
----
==Friulian==
===Etymology===
From {{inh|fur|la|suus}}.
===Pronoun===
{{head|fur|pronoun|third-person singular possessive of masculine singular||of feminine singular|sô|of masculine plural|siei|of feminine plural|sôs}}
# {{lb|fur|used attributively}} [[his]], [[her]], [[its]]; of [[his]], [[hers]], [[its]]
# {{lb|fur|used predicatively}} [[his]], [[hers]], [[its]]
# {{lb|fur|used substantively}} [[his]], [[hers]], [[its]]; the thing belonging to him, her,it
===See also===
* {{l|fur|gno}}
* {{l|fur|lôr}}
* {{l|fur|nestri}}
* {{l|fur|to}}
* {{l|fur|vuestri}}
----
==Galician==
===Etymology===
From {{inh|gl|roa-opt|so}}, {{m|roa-opt|su}}, {{m|roa-opt|sob}}, from {{inh|gl|la|sub}}.
===Pronunciation===
* {{IPA|gl|/so̝/}}
===Preposition===
{{head|gl|preposition}}
# [[under]], [[beneath]]
===References===
* {{R:DDGM}}
* {{R:DDLG}}
----
==German==
===Etymology===
From {{inh|de|gem-pro|*swa}}, {{m|gem-pro|*swē}}, compare with {{cog|odt|so}} and {{cog|nl|zo}}.
===Pronunciation===
* {{IPA|de|/zoː/}}
* {{audio|de|De-so.ogg|Audio}}
* {{rhymes|de|oː}}
===Adverb===
{{de-adv}}
# {{l|en|so}}, [[that]]
#: {{ux|de|Die Leute sind '''so''' nett.|t=People are so nice.|inline=1}}
#: {{ux|de|Dieser Hammer ist nicht '''so''' gut.|t=This hammer is not that good.|inline=1}}
# [[as]] {{qualifier|followed by an adjective or adverb plus {{m|de|wie}} in a statement of equality}}
#: {{ux|de|Er rennt '''so''' schnell wie der Blitz.|t=He runs as fast as lightning.|inline=1}}
# [[thus]], [[like]] [[this]]/[[that]], in this/that [[way]], in this/that [[manner]]
#: {{ux|de|Wenn du den Ball '''so''' wirfst, triffst du die Zielscheibe.|t=If you throw the ball like this, you'll hit the target.}}
# [[then]] {{gloss|in that case}}
#: {{ux|de|Wirst du wieder gesund, '''so''' freue ich mich.|If you get healthy again, then I'll be happy.}}
# {{lb|de|colloquial|}} ''[[expletive]]; sometimes intensifying, sometimes with no noticeable meaning''
#: {{ux|de|Wir sind runtergegangen und haben uns hier '''so''' hingesetzt.|t=We went downstairs and, [[like#Particle|like]], sat down here.}}
====Derived terms====
* {{l|de|einfach so}}
===Conjunction===
{{head|de|conjunction}}
# {{lb|de|archaic}} [[an]], [[if]]
#: {{ux|de|'''So''' es Euch beliebt.|t=If it pleases you.|inline=1}}
====Synonyms====
* {{l|de|falls}}
===Pronoun===
{{head|de|pronoun|cat2=relative pronouns}}
# {{lb|de|obsolete|relative}} [[that]], [[which]], [[who]]
#: {{ux|de|Derhalben sind die Christen schuldig, der Obrigkeit unterthan {{...}} zu seyn in Allem, '''so''' ohne Sünde geschehen mag.|t=That do the Christians owe: to be obedient to the authority {{...}} in all '''that''' may be done without sin.}} (Augsburger Bekenntnis)
====Synonyms====
* {{l|de|der}}
* {{l|de|welcher}}
----
==Gothic==
===Romanization===
{{got-rom|head=sō}}
# {{romanization of|got|𐍃𐍉}}
----
==Indonesian==
===Adverb===
{{head|id|adverb}}
# {{alternative form of|id|sok}}
----
==Irish==
===Pronunciation===
* {{IPA|ga|/sˠɔ/}}
===Determiner===
{{head|ga|determiner}}
# {{alternative form of|ga|seo|from=Munster}} {{q|used after a word ending in a velarized (“broad”) consonant}}
#* '''1938''', Peig Sayers, “Inghean an Cheannaidhe”[{{R:ga:Sjoestedt Description|193}}]:
#*: {{quote|ga|Ní raibh aoinne cloinne age n-a muinntir ach í agus do mhéaduigh sin uirrim agus grádh na ndaoine don inghean óg '''so'''.|Her parents had no children but her, and that increased the esteem and love of the people for this young girl.}}
===References===
===Further reading===
* {{R:ga:Ó Dónaill}}
----
==Italian==
===Alternative forms===
* {{l|it|sò}} {{qual|misspelling}}
===Pronunciation===
* {{it-IPA|sò}}
* {{rhymes|it|ɔ}}
===Verb===
{{head|it|verb form}}
# {{inflection of|it|sapere||1|s|pres|indc}} - (I) {{l|en|know}}
#: {{ux|it|[[non|Non]] [[lo]] '''so'''.|inline=1|I don't '''know''' (it).}}
#: {{ux|it|Lo '''so''' [[io]]!|inline=1|(But) I '''do''' ('''know''' it)!}}
====Usage notes====
Unlike English, Italian verb forms for first/second/third-person are different, rendering {{m|it|io||I}} redundant, unless emphasis is required as shown in last example above.
----
==Japanese==
===Romanization===
{{ja-romaji}}
# {{ja-romanization of|そ}}
# {{ja-romanization of|ソ}}
----
==Luxembourgish==
===Verb===
{{head|lb|verb form}}
# {{inflection of|lb|soen||2|s|impr}}
----
==Mauritian Creole==
===Pronunciation===
* {{IPA|mfe|/so/}}
===Etymology 1===
From {{der|mfe|fr|son}}
===Pronoun===
{{head|mfe|pronoun}}
# (''possessive'') [[his]], [[her]], [[its]], [[one's]]
===Etymology 2===
From {{der|mfe|fr|chaud}}
===Adjective===
{{head|mfe|adjective}}
# [[hot]], [[warm]].
====Antonyms====
* {{l|mfe|fre}}
----
==Middle Dutch==
===Etymology 1===
From {{inh|dum|odt|sō}}, from {{inh|dum|gem-pro|*swa}}.
====Pronunciation====
* {{IPA|dum|/zoː/}}
====Adverb====
{{dum-adv|head=sô|cat2=demonstrative adverbs}}
# {{l|en|so}}, like that, in that manner
# so, to such a degree
# {{lb|dum|so ... {{l|dum|alse}}}} [[as]]
# [[then]], in that case
# so, [[therefore]]
====Conjunction====
{{head|dum|conjunction|head=sô}}
# [[if]], in the case that
# [[like]], as
# {{lb|dum|so ... so}} [[both]] ... [[and]]
====Descendants====
* {{desc|nl|zo}}
* {{desc|li|zoe}}, {{l|li|zoea}}
===Etymology 2===
Weakened form of {{m|dum|soe}}.
====Pronunciation====
* {{IPA|dum|/zoː/|/zo/}}
====Pronoun====
{{head|dum|pronoun|head=sô}}
# {{lb|dum|chiefly|Flemish|nocat=1}} {{alternative form of|dum|si|t=she}}
===Further reading===
* {{R:VMNW|ID19472|I}}
* {{R:VMNW|ID50982|II}}
* {{R:MNW|53057}}
----
==Middle English==
===Pronoun===
{{head|enm|pronoun}}
# {{lb|enm|chiefly Northern dialectal}} {{alt form|enm|sche}}
===References===
* {{R:MED Online|entry= she, (pron.) |id=MED39823 |accessdate=9 May 2018}}
[[Category:Northern Middle English]]
----
==Northern Sami==
===Etymology===
Borrowed from {{bor|se|no|så}}.
===Pronunciation===
{{rfp|se}}
===Adverb===
{{se-adv}}
# [[so]], [[then]], in that case
# so, to this or that [[extent]]
====Further reading====
* {{R:Álgu|9503}}
----
==Norwegian Nynorsk==
===Alternative forms===
* {{l|no|så}}
===Etymology===
From {{der|nn|non|svá}}, from {{der|nn|ine-pro|*swa}}. Akin to {{cog|en|so}}.
===Pronunciation===
* {{IPA|nn|/suː/}}
===Adverb===
{{head|nn|adverb}}
# {{l|en|so}}
#: {{ux|nn|Dei seier '''so'''.|t='''So''' they say.}}
# {{l|en|that}}
#: {{ux|nn|Eg visste ikkje at dei skulle vera '''so''' mange.|t=I didn't know that they were going to be '''that''' many.}}
# {{l|en|as}}
#: {{ux|nn|'''So''' vidt eg veit.|t='''As''' far as I know.}}
# [[so#English|then]]
#: {{ux|nn|Eg gjekk på kino. '''So''' gjekk eg heim.|t=I went to the movies. '''Then''' I went home.}}
===Conjunction===
{{head|nn|conjunction}}
# [[so]]
#: {{ux|nn|Eg barberte meg, '''so''' ho skulle synast eg var fin.|t=I shaved '''so''' that she would think I looked nice.}}
===References===
* {{R:Dokpro|lang=nn}}
----
==Old Dutch==
===Etymology===
From {{inh|odt|gem-pro|*swa}}.
===Adverb===
{{head|odt|adverb|cat2=demonstrative adverbs|head=sō}}
# [[#English|so]], like that, in that manner
====Descendants====
* {{desctree|dum|sô}}
====Further reading====
* {{R:ONW|3970|sō|I}}
----
==Old Irish==
===Alternative forms===
* {{alter|sga|sa|se|sea|seo|siu}}
===Etymology===
From {{inh|sga|cel-pro|*so||this}}, from {{inh|sga|ine-pro|*só}}.
===Pronunciation===
* {{IPA|sga|/so/}}
===Determiner===
{{head|sga|determiner}}
# [[this]] {{qualifier|used after the noun, which is preceded by the [[definite article]]}}
#: {{uxi|sga|ind epistil '''so'''|this epistle}}
====Derived terms====
* {{l|sga|inso}}
====Descendants====
* {{desc|ga|seo}}
* {{desc|gd|seo}}
* {{desc|gv|shoh}}
----
==Old Saxon==
===Etymology===
From {{inh|osx|gem-pro|*swa}}.
===Adverb===
{{head|osx|adverb|cat2=demonstrative adverbs|head=sō}}
# {{l|en|so}}, like that, in that manner
----
==Pali==
===Alternative forms===
{{pi-alt}}
{{pi-alt|Latn=sa}}
===Pronoun===
{{head|pi|pronoun}}
# [[he]], [[it]]
===Adjective===
{{head|pi|adjective form}}
# {{inflection of|pi|ta||m|nom|s|t=that}}
----
==Rawa==
===Noun===
{{head|rwo|noun}}
# [[grass]]
===References===
* Norma Toland, Donald Toland, ''[https://web.archive.org/web/20180711152806/http://www-01.sil.org/pacific/png/pubs/928474523695/Rawa_ref_gram.pdf#page=59 Reference Grammar of the Karo/Rawa Language]'' (1991)
----
==Romani==
===Adverb===
{{head|rom|adverb}}
# [[what]]
----
==Rwanda-Rundi==
===Noun===
{{head|rw|noun}}
# {{l|en|father}}
----
==Serbo-Croatian==
===Alternative forms===
* {{sense|Croatian}} {{l|sh|sȏl}}
===Etymology===
From {{inh|sh|sla-pro|*solь}}, from {{der|sh|ine-pro|*seh₂ls}}.
===Pronunciation===
* {{IPA|sh|/sôː/}}
===Noun===
{{sh-noun|g=f|head=sȏ}}
# {{lb|sh|Bosnian|Serbian}} [[salt]]
====Declension====
{{sh-decl-noun
|so / sol|soli
|soli|soli
|soli|solima
|so / sol|soli
|soli|soli
|soli|solima
|solju / soli|solima
}}
----
==Slavomolisano==
===Etymology===
From {{inh|svm|sh|so}}.
===Pronunciation===
* {{IPA|svm|/so/}}
===Noun===
{{head|svm|noun|g=m}}
# [[salt]]
====Declension====
{{svm-noun-m-o|so}}
===References===
* {{R:svm:DCMAC}}
----
==Slovak==
===Pronunciation===
* {{IPA|sk|/sɔ/}}
===Preposition===
{{sk-prep|desc=+ instrumental}}
# [[with]]
====Synonyms====
* {{l|sk|s}}
===Further reading===
* {{R:SDK}}
----
==Slovene==
===Pronunciation===
* {{sl-IPA|sȍ}}
===Verb===
{{head|sl|verb form|head=sȍ}}
# {{inflection of|sl|bíti||3|p|pres}}
----
==Spanish==
===Pronunciation===
* {{es-IPA}}
===Etymology 1===
From {{inh|es|la|sub}}, from {{inh|es|itc-pro|*supo}}, from {{inh|es|ine-pro|*upo}}.
====Preposition====
{{head|es|preposition}}
# {{lb|es|archaic}} [[under]]
=====Usage notes=====
''So'' is very rare in modern Spanish, surviving only in certain expressions, including {{m|es|so pena de||on pain of, under penalty of}}, {{m|es|so pretexto de}} or {{m|es|so color de||under pretext of}}, {{m|es|a so capa||secretly, with bribery}}.
====Pronoun====
{{head|es|pronoun}}
# [[you]] {{qualifier|emphatic, derogatory}}
#:* {{ux|es|¡So [[tonto]]!|inline=1|t=You blithering idiot!}}
#:* {{ux|es|¡So [[borrachos]]!|inline=1|t=You bloody drunks!}}
===Etymology 2===
Borrowed from {{bor|es|en|so}}.
====Interjection====
{{head|es|interjection}}
# {{lb|es|United States|Puerto Rico|El Salvador}} [[so]]
===Etymology 3===
====Interjection====
{{head|es|interjection}}
# [[whoa|whoa!]]
----
==Swedish==
===Etymology===
From {{inh|sv|non|sýr}}, from {{inh|sv|gem-pro|*sūz}}, from {{inh|sv|ine-pro|*sū-}}.
===Noun===
{{sv-noun|c}}
# {{lb|sv|rare}} [[sow]], female [[pig]]
====Usage notes====
* The more common synonym is {{m|sv|sugga}}, especially for the plural form.
====Declension====
{{sv-infl-noun-c-r}}
====Synonyms====
* {{l|sv|sugga}}
===Anagrams===
* {{anagrams|sv|a=os|OS|os}}
----
==Tok Pisin==
===Etymology 1===
From {{der|tpi|en|saw}}.
====Noun====
{{head|tpi|noun}}
# [[saw]]
===Etymology 2===
From {{der|tpi|en|show}}.
====Noun====
{{head|tpi|noun}}
# [[show]]
----
==Veps==
===Etymology===
From {{inh|vep|fiu-fin-pro|*soo}}.
===Noun===
{{vep-noun}}
# [[swamp]], [[marsh]], [[bog]]
====Inflection====
{{vep-decl-stems|so||n|d|id}}
====Derived terms====
* {{l|vep|sohein}}
* {{l|vep|sokesk}}
===References===
* {{R:vep:UVVV|болото}}
{{topics|vep|Landforms}}
----
==Vietnamese==
===Pronunciation===
{{vi-pron}}
===Etymology 1===
====Verb====
{{vi-verb}}
# {{lb|vi|transitive}} to [[compare]]
#: {{ux|vi|'''So''' với bạn thì nó cao hơn.|inline=1|t=Compared to his friend, he is taller.}}
# {{lb|vi|transitive}} to [[pair up]]
#: {{ux|vi|'''so''' đũa|inline=1|t=to pair up chopsticks}}
# {{lb|vi|intransitive}} to [[straighten]] one's [[shoulders]], as if to [[compare]] one's height to another's
=====Synonyms=====
* {{sense|to compare}} {{vi-l|so sánh}}
===Etymology 2===
Compare {{vi-link|sơ|first|初}}.
====Adjective====
{{vi-adj}}
# [[firstborn]]
#: {{ux|vi|con '''so'''|inline=1|t=firstborn child}}
#: {{ux|vi|chửa con '''so'''|inline=1|t=to be pregnant for the first time}}
#: {{ux|vi|trứng gà '''so'''|inline=1|t=a chicken's first egg (usually a small egg)}}
=====Derived terms=====
* {{vi-l|con so}}
===Etymology 3===
====Noun====
{{vi-noun|cls=con}}
# {{taxlink|Carcinoscorpius rotundicauda|species|noshow=1|ver=180202}}, {{vern|mangrove horseshoe crab}}
----
==Volapük==
===Adverb===
{{head|vo|adverb}}
# {{l|en|so}}
----
==Welsh==
===Verb===
{{head|cy|verb form}}
# {{lb|cy|colloquial|South Wales}} {{inflection of|cy|bod||2|s|pres|negative}}
# {{lb|cy|colloquial|South Wales}} {{inflection of|cy|bod||3|s|pres|negative}}
#: {{ux|cy|'''So''' e’n credu.|t=He doesn’t think so.|inline=1}}
# {{lb|cy|colloquial|South Wales}} {{inflection of|cy|bod||1|p|pres|negative}}
# {{lb|cy|colloquial|South Wales}} {{inflection of|cy|bod||2|p|pres|negative}}
# {{lb|cy|colloquial|South Wales}} {{inflection of|cy|bod||3|p|pres|negative}}
====Usage notes====
Unlike other negative verb forms, this form—and {{m|cy|sa}}, which is used for the first-person singular—is not complemented by {{m|cy|ddim}} after the subject.
----
==Xhosa==
===Pronoun===
{{xh-pron|stem=1}}
# {{xh-combining stem of|sona}}
----
==Zulu==
===Pronoun===
{{zu-pron|stem=1}}
# {{zu-combining stem of|sona}}


--- layout: post title: This Smartphone Keyboard Doesn't Need A Battery or Bluetooth thumbnail: /img/nfc-keyboard.JPG ---
Some people just need a physical keyboard for their smartphone. They can't stand typing on glass, or having to look while they type.
Until now, most of those people have turned to bluetooth keyboard cases.
These keyboards work pretty well, but they're a bit heavy, you have to charge them frequently, and they're a bit of a drain on your smartphone's battery.
At New York's CE Week, I met with a company called one2TOUCH, whose solution is a bit more elegant.
one2TOUCH's Flipcover case runs off of NFC (Near-Field-Communication).
NFC chips are small circuits that run off of ambient energy emitted by your smartphone. When a key is pressed, the circuit is activated, sending a signal to your phone. Bluetooth, on the other hand, is always on, always connected.
Using NFC eliminates the need for an on-keyboard battery, and the need for bluetooth on your phone. This saves weight, and energy, making one2TOUCH's covers very light.
Of course, this method has its downsides. Many phones don't have NFC technology installed. Bluetooth keyboards are cheap and readily available. The NFC keyboard is new, and not yet on the market.
Still, I think this is a promising use of NFC, and I look forward to the other ways that people will use NFC for accessories.


BLADE DEATH
Edinburgh dad stabbed to death outside football social club but killer denies murdering him
by Wilma RileyA 42-YEAR-old man admitted killing a dad outside Edinburgh City Football Club's social club by stabbing him on the neck with knife.
Paul Smith, who is charged with murdering electrician Andrew McCarron at Lochend Road South, Edinburgh, on July 21 offered to plead guilty to the reduced charge of culpable homicide at Glasgow's High Court.
The plea was tendered by Smith's solicitor advocate Brian Gilfedder.
But it was not accepted by prosecutor Lisa Gillespie.
Smith denies murdering Mr McCarron and assaulting Robert Smith to his permanent disfigurement by repeatedly striking him on the body with a knife.
Judge Lord Matthews set a trial date for April 14 at the High Court in Edinburgh.
After his death, McCarron's family issued a statement.
It read: "Andrew was a loving family man, a kind soul and an Aston Villa fan through and through, who was sadly taken away from us on Sunday 21st July.
"He will be dearly missed by his parents, siblings, children, family and friends.
"The loss of our beloved Andrew is immeasurable, but so also, is the love he left behind.
"Rest in Peace, Andrew."


resource ldap_first_entry ( resource $link_identifier , resource $result_identifier )
Returns the entry identifier for first entry in the result. This entry identifier is then supplied to ldap_next_entry() routine to get successive entries from the result. Entries in the LDAP result are read sequentially using the ldap_first_entry() and ldap_next_entry() functions.
Returns the result entry identifier for the first entry on success and FALSE on error.


A small group gathered at Info.nl for our fifth meetup. The aim of this gathering was to transition from the open-ended meeting format we have been using thus far into more goal directed sessions. To this end some of us had analysed the previous meeting minutes and formulated the things we felt were at the top of the list to start working on. The agenda was as follows:
This time we had people from design agencies, the open government data field, and digital activism. After a brief round of introductions we got started.
We start out with a presentation of a clustering of all the ideas from previous meeting minutes. Ideas fall under one of six categories:
After this overview we open it up to feedback from attendees.
Many of the ideas clustered under the above categories come across as rather inwards focused. We should ask ourself what we have to offer to others.
‘Professionals’ are often mentioned as audience. ‘Tech worker’ too. So are we aiming to be a group by a particular group of people for a group of similar people? In other words: by tech workers, for tech workers?
What if we aim to offer things to other groups, such as politicians? For example, Digital Defenders supports journalists with grants and tools and other things.
Hard technology only goes so far, you also need soft technology (methods for change-making) to really create impact. For example, open data has been applied to allow citizens to inspect the government budget for their neighbourhood and determine wether they agree with its priorities.
Another question is what kind of organisation we need to be. And to also question wether we need to adopt a formal organisation structure at all. For example, the Cooperative University of Amsersfoort is not an actual university but applied the scientific method to social issues. For example ’ such as climate change. ‘Meet je stad!’ is a citizen science project for which sensor kits were developed that enable ordinary people to contribute heat measurements.
If we develop more specific goals like this we will enable people to join more easily. Once again, it’s not just about technology but also using ‘network thinking’ to get people involved and to enable them to stay involved.
Maybe to achieve our aims we need to go out into the field. Then we will see what we need to do to get to where we want to be. Seeking out a direct confrontation with every day reality will provide us with valuable insights into where we are right now and what we need to do to get to where we want to be.
Another example mentioned is True Price, a social enterprise that helps organisations quantity their impact on society.
Following this first section of the analysis of what we’ve discussed over the course of the previous four meetups, we share a plan of action for the immediate future. This plan is broken down into three parts:
We get some feedback on this from a community building perspective. Ton Zijlstra has a good model which outlines a number of ‘levers’ we can use to influence the growth of a community. These are:
The ones marked with a * are the first to get right. The rest can come after. The importance of the levers and their required settings will change as the group evolves. We should strive to create feedback loops, continuously ask people how we are doing.
With regards to the three elements in the plan of action, attendees find them recognisable. As we make choices about comms infrastructure we should keep asking ourselves if the tools are a good match for our audience.
On the subject of the chat system we now employ, it’s clear it does not support cases where people can contribute new ideas and small groups can form around them and branch off to do their thing. This is a shame because this is how new initiatives can emerge. At the moment it’s hard to see who is involved. This doesn’t help on this point either.
Someone asks, do we want to do something for vulnerable groups directly or do we want to radicalise tech workers? The question is left unanswered but it is something to keep in mind.
A quality of a well-functioning community is how welcoming are we for people who are outsiders or newcomers and who aren’t super technical per se.
We talk a little bit about the distinction between offering toolkits and developing tools. We feel the former is more interesting to pursue than the latter. There are so many tools out there already, it is more a matter of helping those in need adopt them. An example would be Bits of Freedom’s ‘Internetvrijheid Toolbox’. How would something like this look like for organisations serving the marginalised in the Netherlands?
When talking about tools it’s not just about hard technology but soft (social) technology as well. Ton Zijlstra has a great model for this as well which he calls the agency map. It is described at the bottom of this blog post, the rest of the series is worth a read as well. In short, the model suggests mapping out the persons who are in need of increased agency, the technologies required, the methods required, and finally the desired outcomes or impacts.
Such a model could serve us well once we start working with organisations. It helps us look past only the hard technology and also think about methods that are suitable to our aims.
We start brainstorming next actions and ideas for subjects and people to invite to future meetups.
On a community organising level, things that might be interesting to talk about are bread funds, distributed energy cooperatives, and local food networks such as Rechtstreex.
Another subject people care about is public ignorance of the workings of social media and related privacy concerns. The power differential between companies like Facebook and the public. The way such platforms shape our perception of reality. We could invite people who are building alternatives to such services. We could also consider activist groups such as Bits of Freedom or the Pirates.
A subject that keeps popping up is the rise of the populist right. The analysis we’ve done at previous meetups is that these ultimately are a product of the political and economic system we are part of. So we can work to raise awareness of injustices, but we could also work to address the material conditions that produce and sustain these intolerances.
We talk about the concept of resilience and the different viewpoints we have on this idea. Is it about individual leverage, or organising collectively in solidarity with each other? Ultimately individuals are rather powerless in the face of these issues. But collectively, as tech workers, we have some power to wield. Particularly those who are employed by significant economic actors.
As it stands, the left in technology is fractured and marginalised. The tech scene has become increasingly inhospitable to leftist ideas. Cyberculture has been taken over and coopted by the right. It is time to formulate a leftist answer to it. An alternative conceptualisation of technology’s role in society, beyond individual liberty.
Relatedly, we talk about the phenomenon of tech workers fitting the stereotype of the ‘rootless cosmopolitans’ who are not connected to their local communities. This is a more pronounced issue in the US. But in the Netherlands it manifests itself as well.
A case raised by one attendee is of moving cities and seeking to get rooted in the new place. How does one go about it, in particular if you’re workplace is not embedded in it? The best way seems to be to participate in local communities.
More ideas for people to invite and topics to discuss:
Rutger Bregman to talk about universal basic income, or his colleague Jesse Frederik about the debt industry.
Ethics by design. Lots of organisations need to figure out ethical design of technology but lack the expertise. Existing organisations in our field such as privacy advocacy groups do not offer such services. This could be a thing we could offer.
More people doing interesting work in the area of technology and activism:
Our next meetup is August 7. We might do a pilot with a speaker. Everyone leaves with renewed hope for the future.


Go to Class and Go to Symbol
A custom language plugin can provide its own items to be included in the lists shown when the user chooses the Go to | Class...
or Go to | Symbol...
action.
In order to do so, the plugin must provide implementations for the
ChooseByNameContributor
interface (separate implementations need to be provided for Go to Class
and Go to Symbol
), and register them in the com.intellij.gotoClassContributor
and com.intellij.gotoSymbolContributor
extension points.
Each contributor needs to be able to return a complete list of names to show in the list for a specified project, which will then be filtered by the IDE according to the text typed by the user in the dialog. For each name in that list, the contributor needs to provide a list of NavigationItem instances (typically PsiElement ), which specify the destinations to jump to when a specific name is selected from the list.


{% comment %}
To put the site into maintenance mode (for regular users),
rename base.html to base_original.html and change this file's name
to base.html. Edit the text within this DIV to reflect expecte return
to service and to provide background information.
Really, the site should return a 503, but for the limited maintenance
downtime we experience, this will suffice.
{% endcomment %}
The Knowledge Commons DC website is down for maintenance. We expect to be back up at 3 a.m. on Monday, 9 April.
Questions? Contact us at contact@knowledgecommonsdc.org.


You need to enable JavaScript to run this app.
RNBO Granular Web Synth
Sam Wells
MIDI Input
Use the keyboard below or (if you are using Google Chrome) attached MIDI devices
A
W
S
E
D
F
T
G
Y
H
U
J
K
O
L
P
;
Buffer Selector
Load File into "usr_buff" buffer:
Parameters
No parameters
Credits and Thanks
Bret Cameron's playable synth keyboard
Evan Sondregger's Web Audio Peak Meter
Inspiration from John Gibson's jg.granulate Max external


Copyright © 2014 W3C© (MIT, ERCIM, Keio), All Rights Reserved. W3C liability, trademark and document use rules apply.
This specification describes a method that enables web applications to synchronize data when next online.
This section describes the status of this document at the time of its publication. Other documents may supersede this document. A list of current W3C publications and the latest revision of this technical report can be found in the W3C technical reports index at http://www.w3.org/TR/.
This document was published by the Web Applications Working Group as an Editor's Draft. If you wish to make comments regarding this document, please send them to<EMAIL_ADDRESS>(subscribe, archives). All feedback is welcome.
Publication as an Editor's Draft does not imply endorsement by the W3C Membership. This is a draft document and may be updated, replaced or obsoleted by other documents at any time. It is inappropriate to cite this document as other than work in progress.
This document was produced by a group operating under the 5 February 2004 W3C Patent Policy. W3C maintains a public list of any patent disclosures made in connection with the deliverables of the group; that page also includes instructions for disclosing a patent. An individual who has actual knowledge of a patent which the individual believes contains Essential Claim(s) must disclose the information in accordance with section 6 of the W3C Patent Policy.
All diagrams, examples, notes, are non-normative, as well as sections explicitly marked as non-normative. Everything else in this specification is normative.
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in the normative parts of this document are to be interpreted as described in RFC2119. For readability, these words do not appear in all uppercase letters in this specification.
Any point, at which a conforming UA must make decisions about the state or reaction to the state of the conceptual model, is captured as algorithm. The algorithms are defined in terms of processing equivalence. The processing equivalence is a constraint imposed on the algorithm implementors, requiring the output of the both UA-implemented and the specified algorithm to be exactly the same for all inputs.
This document relies on the following specifications:
Web Applications traditionally assume that the network is reachable. The HTML5 Application Cache and Service Workers are beginning to challenge these assumptions and applications which are written to take advantage of them now face the challenge of attempting to synchronize client state to servers when clients .
TODO
TODO
Underscored functions and attributes are UA-internal properties.
TODO
Thanks go to ....
The authors would also like to thank Jeffery Yasskin for his scripts and formatting tools which have been essential in the production of this specification.


| Filename | Description |
| Makefile | Just a little wrapper for Makefile.cil |
| Makefile.cil.in | configure source for the Makefile for building CIL |
| configure | The configure script |
| configure.in | The autoconf source for configure |
| config.guess, config.sub, install-sh | stuff required by configure |
| doc/ | HTML documentation of the CIL API |
| obj/ | Directory that will contain the compiled CIL modules and executables |
| bin/cilly.in | The configure source for a Perl script that can be invoked with the same arguments as either gcc or Microsoft Visual C and will convert the program to CIL, perform some simple transformations, emit it and compile it as usual. |
| lib/CompilerStub.pm | A Perl class that can be used to write code that impersonates a compiler. cilly uses it. |
| lib/Merger.pm | A subclass of CompilerStub.pm that can be used to merge source files into a single source file.cilly uses it. |
| bin/patcher.in | A Perl script that applies specified patches to standard include files. |
| src/check.ml,mli | Checks the well-formedness of a CIL file |
| src/cil.ml,mli | Definition of CIL abstract syntax and utilities for manipulating it |
| src/clist.ml,mli | Utilities for efficiently managing lists that need to be concatenated often |
| src/errormsg.ml,mli | Utilities for error reporting |
| src/ext/heapify.ml | A CIL transformation that moves array local variables from the stack to the heap |
| src/ext/logcalls.ml,mli | A CIL transformation that logs every function call |
| src/ext/sfi.ml | A CIL transformation that can log every memory read and write |
| src/frontc/clexer.mll | The lexer |
| src/frontc/cparser.mly | The parser |
| src/frontc/cabs.ml | The abstract syntax |
| src/frontc/cprint.ml | The pretty printer for CABS |
| src/frontc/cabs2cil.ml | The elaborator to CIL |
| src/maincil.ml | A test application called cilly |
| src/pretty.ml,mli | Utilities for pretty printing |
| src/rmtmps.ml,mli | A CIL tranformation that removes unused types, variables and inlined functions |
| src/stats.ml,mli | Utilities for maintaining timing statistics |
| src/testcil.ml | A random test of CIL (against the resident C compiler) |
| src/trace.ml,mli | Utilities useful for printing debugging information |
| ocamlutil/ | Miscellaneous libraries that are not specific to CIL. |
| ocamlutil/Makefile.ocaml | A file that is included by Makefile |
| ocamlutil/Makefile.ocaml.build | A file that is included by Makefile |
| ocamlutil/perfcount.c | C code that links with src/stats.ml and reads Intel performance counters. |
| obj/<EMAIL_ADDRESS>| File generated by Makefile.cil describing which extra “features” to compile. See Section 5 |
| obj/<EMAIL_ADDRESS>| File generated by Makefile.cil containing information about your architecture, such as the size of a pointer |
| src/machdep.c | C program that generates machdep.ml files |


{{game.description}}
*bunch of scrollable screenshots (thumbnails openable in a lightbox) from/of game here*
Release Date
Universe
*universe that game takes place in*
Series
*series*
Prequel
*previous game*
Sequel
*next game*


All good things have to come to an end, and it is with much sadness that we have to announce that this is the last segment of our active essay. *sobs* However, we have some fun and light-hearted activity installed for you so stay tuned!
For this segment, you would also need the Netlogo software which you downloaded. Open the Be a Minion.nlogo file and start exploring! Do ensure that the Gameofdeath.png file is in the NetLogo Data folder!
In this segment of the active essay, you will be a purple minion in the model! How cool is that? Besides that, we have integrated initial-delay-mean and initial-delay-sd to become my-initial-delay as an input box, as well as integrated min-my-speed and max-my-speed to just my-own-speed as an input box. What are all these input boxes for?  How fast will you move? Be true to youself, and input all these into the model! If you are not sure about the conversion rates from measurements in real life, the next section will be useful! See how you fare in the evacuation process! Have fun and hope you have enjoyed the website thus far! It would be good if you can us fill in the survey form at the bottom of the page! Thank you!
5 seconds in real-life = 1 unit of time in the model
5 speed units in my-own-speed = 0.3m travelled per second in real-life.


The ability to access cookies has been a feature of JavaScript since, well, forever.
Cookies are now obsolete for client-side storage (unless you need to support
really old browser versions) but they can still be a useful mechanism for
exchanging non-critical data between the server and client. Unfortunately,
accessing cookies via document.cookie
is simply horrible.
UsefulJS.Storage presents a DOM storage-compatible interface to document.cookie
that allows you to treat cookies as named key-value data stores. If you're unlucky enough
to have to support a browser that does not offer storage, it can provide a fix to
emulate both local storage and session storage using cookies.
new UsefulJS.Storage(name[, props])
name
Stringprops
ObjectThrows: TypeError if name
is anything other than a non-empty string.
The optional props
parameter can have the following properties:
Adds a storage entry to UsefulJS.featureSupport that allows for testing
localStorage
/ sessionStorage
support.
Exposes the following properties:
Whether cookies are enabled.
Whether localStorage
is supported and enabled.
sessionStorage
is supported and enabled.
See the W3C documentation for more information.
Read-only property that reflects the number of items in the datastore.
Object.defineProperty
. Otherwise it can be written to. Assigning a value to
it doesn't change the underlying data.
Clears the store; the underlying cookie is removed
storage.clear()
Retrieves an item from the data store
storage.getItem(key)
Returns String
if the key exists in the store, otherwise returns
null
.
Retrieves a key name from the store at a given numeric index
storage.key(index)
Returns String
if there is a key at the given index, otherwise returns
null
.
Removes an item from the data store
storage.removeItem(key)
Stores an item in the data store; the value stored is coerced to a String if it is not a String
storage.setItem(key, value)
Stringifies the cookie data
storage.toString()
Returns String
The returned string takes the form name=<ENCODED_VALUE>
where "name" is the name of the data store and "<ENCODED_VALUE>" is the
store data with URI-encoding applied. When the value is URI-decoded, it takes
the same form as a query string: key1=value1&key2=value2...
. Each
key and value is individually URI-encoded.
// Load the user's high score var score = 0, store = new UsefulJS.Storage("my.game.data"), hiScore = Number(store.getItem("hs")); ... // If there's a new high score, persist it if (score > hiScore) { store.setItem("hs", score); }
The storage specification says that an event should be issued to all open tabs that might be interested in the modified data. Well, that ain't going to happen.
Cookies may trivially be disabled by the browser user. If that is the case, values may be stored but they won't be persisted.
In Chrome (at least), cookies are not allowed with file:// URLs, which is handy when you're developing stuff locally. Can't quite see what security issue this restriction solves myself since native storage works just fine.
The fixes for the Storage module are defined in the _storage namespace of the fix options.
If, by some chance, your code is running in a browser that doesn't offer a
native storage implementation, this fix will emulate window.localStorage
using a cookie called UsefulJSLocalStorage. This fix will not be applied if storage
has been disabled in browser settings. If UsefulJS.featureSupport.storage.local
is false and so is _storage.localStorage
in the return Object from
UsefulJS.fix
, storage has probably been disabled either explicitly
or as a side effect of private browsing.
If required, this fix emulates window.sessionStorage
with a
session cookie called UsefulJSSessionStorage.


This is a paragraph
Headings do not have to be declared in any order, can only be from 1 to 6 and can be repeated


Rack::ShowExceptions
Sinatra::ShowExceptions catches all exceptions raised from the app it wraps. It shows a useful backtrace with the sourcefile and clickable context, the whole Rack environment and the request data.
Be careful when you use this on public-facing sites as it could reveal information helpful to attackers.
# File lib/sinatra/showexceptions.rb, line 20 20: def call(env) 21: @app.call(env) 22: rescue Exception => e 23: errors, env["rack.errors"] = env["rack.errors"], @@eats_errors 24: 25: if respond_to?(:prefers_plain_text?) and prefers_plain_text?(env) 26: content_type = "text/plain" 27: body = [dump_exception(e)] 28: else 29: content_type = "text/html" 30: body = pretty(env, e) 31: end 32: 33: env["rack.errors"] = errors 34: 35: [500, 36: {"Content-Type" => content_type, 37: "Content-Length" => Rack::Utils.bytesize(body.join).to_s}, 38: body] 39: end
# File lib/sinatra/showexceptions.rb, line 43 43: def frame_class(frame) 44: if frame.filename =~ /lib\/sinatra.*\.rb/ 45: "framework" 46: elsif (defined?(Gem) && frame.filename.include?(Gem.dir)) || 47: frame.filename =~ /\/bin\/(\w+)$/ 48: "system" 49: else 50: "app" 51: end 52: end
Disabled; run with --debug to generate this.
Generated with the Darkfish Rdoc Generator 1.1.6.


---
layout: default
---
{% include header.html page='restrictions' %}
{% comment %}
List all the exception includes here in __alphabetical__ order.
The first one should be passed with `class='top'` and the last
should be passed with `class='bottom'`.
To add a site, just copy and paste the
_includes/exceptions/_template.html file and use that as the base.
Example:
{% include exceptions/amazon.html class='top' %}
{% include exceptions/paypal.html %}
{% include exceptions/twitter.html class='bottom' %}
{% endcomment %}
{% include exceptions/none.html %}
{% comment %}
End the exceptions includes.
{% endcomment %}


Loading...
Loading...
Loading...
Loading...
Loading...
Game Over
Wish to play again?
Restart
X
You Won
Hurray! You have completed all levels, Wish to play again?
Restart
X