Received: from 173-13-139-235-sfba.hfc.comcastbusiness.net ([173.13.139.235]:44337 helo=jukni.digitalkingdom.org) by stodi.digitalkingdom.org with smtp (Exim 4.80.1) (envelope-from ) id 1XgZN4-0001LB-6p; Tue, 21 Oct 2014 06:21:11 -0700 Received: by jukni.digitalkingdom.org (sSMTP sendmail emulation); Tue, 21 Oct 2014 06:21:06 -0700 From: "Apache" Date: Tue, 21 Oct 2014 06:21:06 -0700 To: webmaster@lojban.org, nictytan@gmail.com Subject: [jvsw] Definition Edited At Word ce'oi -- By gleki Bcc: jbovlaste-admin@lojban.org Message-ID: <54465dc2.CcioCO3z0zcvPcrb%webmaster@lojban.org> User-Agent: Heirloom mailx 12.5 7/5/10 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Spam-Score: 0.5 (/) X-Spam_score: 0.5 X-Spam_score_int: 5 X-Spam_bar: / X-Spam-Report: Spam detection software, running on the system "stodi.digitalkingdom.org", has NOT identified this incoming email as spam. The original message has been attached to this so you can view it or label similar future email. If you have any questions, see @@CONTACT_ADDRESS@@ for details. Content preview: In jbovlaste, the user gleki has edited a definition of "ce'oi" in the language "English". Differences: 5,5c5,5 < "ce'oi" is the word of choice to separate the arguments in bridi3. Using {ce'o} there has obvious limitations when the selbri actually calls for a sequence. Obviously, ce'oi has issues too if the selbri can accept an argument list, but this can be circumvented more readily with {ke}...{ke'e} brackets than it can with {ce'o}. Consider ".i lo ka broda cu selbri fi ko'a ce'o ko'e". Without inspecting the type requirements of {broda} and the respective types of {ko'a} and {ko'e}, one cannot determine the meaning of the {bridi}. Furthermore, if one accepts non-static typing of {sumti} places, multiple correct answers can be given for a question asking what is the bridi1. This would create ambiguity that is otherwise resolved by "ce'oi". See also {ka}, {du'u}, {me'au}. --- > "ce'oi" is the word of choice to separate the arguments in $bridi_3$. Using {ce'o} there has obvious limitations when the selbri actually calls for a sequence. Obviously, ce'oi has issues too if the selbri can accept an argument list, but this can be circumvented more readily with {ke}...{ke'e} brackets than it can with {ce'o}. Consider ".i lo ka broda cu selbri fi ko'a ce'o ko'e". Without inspecting the type requirements of {broda} and the respective types of {ko'a} and {ko'e}, one cannot determine the meaning of the {bridi}. Furthermore, if one accepts non-static typing of {sumti} places, multiple correct answers can be given for a question asking what is the $bridi_1$. This would create ambiguity that is otherwise resolved by "ce'oi". See also {ka}, {du'u}, {me'au} [...] Content analysis details: (0.5 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- 0.0 URIBL_BLOCKED ADMINISTRATOR NOTICE: The query to URIBL was blocked. See http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block for more information. [URIs: lojban.org] 1.4 RCVD_IN_BRBL_LASTEXT RBL: No description available. [173.13.139.235 listed in bb.barracudacentral.org] -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% [score: 0.0000] 1.0 RDNS_DYNAMIC Delivered to internal network by host with dynamic-looking rDNS In jbovlaste, the user gleki has edited a definition of "ce'oi" in the language "English". Differences: 5,5c5,5 < "ce'oi" is the word of choice to separate the arguments in bridi3. Using {ce'o} there has obvious limitations when the selbri actually calls for a sequence. Obviously, ce'oi has issues too if the selbri can accept an argument list, but this can be circumvented more readily with {ke}...{ke'e} brackets than it can with {ce'o}. Consider ".i lo ka broda cu selbri fi ko'a ce'o ko'e". Without inspecting the type requirements of {broda} and the respective types of {ko'a} and {ko'e}, one cannot determine the meaning of the {bridi}. Furthermore, if one accepts non-static typing of {sumti} places, multiple correct answers can be given for a question asking what is the bridi1. This would create ambiguity that is otherwise resolved by "ce'oi". See also {ka}, {du'u}, {me'au}. --- > "ce'oi" is the word of choice to separate the arguments in $bridi_3$. Using {ce'o} there has obvious limitations when the selbri actually calls for a sequence. Obviously, ce'oi has issues too if the selbri can accept an argument list, but this can be circumvented more readily with {ke}...{ke'e} brackets than it can with {ce'o}. Consider ".i lo ka broda cu selbri fi ko'a ce'o ko'e". Without inspecting the type requirements of {broda} and the respective types of {ko'a} and {ko'e}, one cannot determine the meaning of the {bridi}. Furthermore, if one accepts non-static typing of {sumti} places, multiple correct answers can be given for a question asking what is the $bridi_1$. This would create ambiguity that is otherwise resolved by "ce'oi". See also {ka}, {du'u}, {me'au} Old Data: Definition: argument list separator: acts as a comma between arguments in an argument list supplied to a function. Notes: "ce'oi" is the word of choice to separate the arguments in bridi3. Using {ce'o} there has obvious limitations when the selbri actually calls for a sequence. Obviously, ce'oi has issues too if the selbri can accept an argument list, but this can be circumvented more readily with {ke}...{ke'e} brackets than it can with {ce'o}. Consider ".i lo ka broda cu selbri fi ko'a ce'o ko'e". Without inspecting the type requirements of {broda} and the respective types of {ko'a} and {ko'e}, one cannot determine the meaning of the {bridi}. Furthermore, if one accepts non-static typing of {sumti} places, multiple correct answers can be given for a question asking what is the bridi1. This would create ambiguity that is otherwise resolved by "ce'oi". See also {ka}, {du'u}, {me'au}. Jargon: Gloss Keywords: Word: argument list separator, In Sense: Place Keywords: New Data: Definition: argument list separator: acts as a comma between arguments in an argument list supplied to a function. Notes: "ce'oi" is the word of choice to separate the arguments in $bridi_3$. Using {ce'o} there has obvious limitations when the selbri actually calls for a sequence. Obviously, ce'oi has issues too if the selbri can accept an argument list, but this can be circumvented more readily with {ke}...{ke'e} brackets than it can with {ce'o}. Consider ".i lo ka broda cu selbri fi ko'a ce'o ko'e". Without inspecting the type requirements of {broda} and the respective types of {ko'a} and {ko'e}, one cannot determine the meaning of the {bridi}. Furthermore, if one accepts non-static typing of {sumti} places, multiple correct answers can be given for a question asking what is the $bridi_1$. This would create ambiguity that is otherwise resolved by "ce'oi". See also {ka}, {du'u}, {me'au} Jargon: Gloss Keywords: Word: argument list separator, In Sense: Place Keywords: You can go to to see it.