Received-SPF: pass (google.com: domain of felipeg.assis@gmail.com designates 2607:f8b0:4001:c03::236 as permitted sender) client-ip=2607:f8b0:4001:c03::236;
MIME-Version: 1.0
In-Reply-To: <52E449FD.90002@gmx.de>
References: <CALMa68r_+2Ys6K46nuQNUDUn2ZdWwnE5_BdP9ETVdseUvm3H1w@mail.gmail.com>
	<52E449FD.90002@gmx.de>
Date: Sat, 25 Jan 2014 21:54:53 -0200
Message-ID: <CALMa68r7X68wfitLXK-2KfSm_NLnPLgkujxSqstCH3JBMZE+xA@mail.gmail.com>
Subject: Re: [lojban] [oz] {binxo}
From: =?ISO-8859-1?Q?Felipe_Gon=E7alves_Assis?= <felipeg.assis@gmail.com>
To: lojban@googlegroups.com
Reply-To: lojban@googlegroups.com
Precedence: list
Mailing-list: list lojban@googlegroups.com; contact lojban+owners@googlegroups.com
Sender: lojban@googlegroups.com
Content-Type: multipart/alternative; boundary=089e01184b0c7159d104f0d433c4
X-Spam_score: 0.0
X-Spam_score_int: 0
X-Spam_bar: /

--089e01184b0c7159d104f0d433c4
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

That was my bet, but then I find examples (3) and (4) quite odd. Are you
sure you didn't want to use properties there? Maybe you want to check
examples (6) and (8) as well.

By the way, what do you think about the idea of using {co'a} to replace
property-binxo? People tend to associate {co'a} with processes, but there
is no reason to limit its scope like that.

mu'o
mi'e .asiz.

On 25 January 2014 21:34, selpa'i <seladwa@gmx.de> wrote:

> la .asiz. cu cusku di'e
>
>  I noticed you sometimes use a property as binxo2, and sometimes a
>> concrete object. I know you make use of overloading (or polymorphism),
>> but I couldn't understand what your particular interpretation of each
>> version of {binxo} is that makes you sometimes use one version and
>> sometimes another.
>>
>
> I think I use them more or less interchangeably, but one is often more
> convenient than the other.
>
> With a concrete object, it means that one thing turns into another, as in=
:
>
>
>  (7) {lo m=E0pku cu b=ECnxo lo t=E0nbo}
>>
>
> "The cap turned into a board."
>
> It's just *really* useful to be able to say that.
>
> With a property it means "to begin to have a property" or "to undergo  a
> change towards having a property".
>
> I'm not sure which one I would pick if I had to choose one over the other
> as the only acceptable binxo2. I think I might lean towards the concrete
> object version, however. The other one could still be accessed via
> {kairbi'o} =3D {binxo lo ckaji be lo ka}, while the exremely useful {binx=
o lo
> mlatu} would remain correct.
>
> mi'e la selpa'i mu'o
>
> --
> You received this message because you are subscribed to the Google Groups
> "lojban" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to lojban+unsubscribe@googlegroups.com.
> To post to this group, send email to lojban@googlegroups.com.
> Visit this group at http://groups.google.com/group/lojban.
> For more options, visit https://groups.google.com/groups/opt_out.
>

--=20
You received this message because you are subscribed to the Google Groups "=
lojban" group.
To unsubscribe from this group and stop receiving emails from it, send an e=
mail to lojban+unsubscribe@googlegroups.com.
To post to this group, send email to lojban@googlegroups.com.
Visit this group at http://groups.google.com/group/lojban.
For more options, visit https://groups.google.com/groups/opt_out.

--089e01184b0c7159d104f0d433c4
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">That was my bet, but then I find examples (3) and (4) quit=
e odd. Are you sure you didn&#39;t want to use properties there? Maybe you =
want to check examples (6) and (8) as well.<br><br>By the way, what do you =
think about the idea of using {co&#39;a} to replace property-binxo? People =
tend to associate {co&#39;a} with processes, but there is no reason to limi=
t its scope like that.<br>
<br>mu&#39;o<br>mi&#39;e .asiz.<br><div class=3D"gmail_extra"><br><div clas=
s=3D"gmail_quote">On 25 January 2014 21:34, selpa&#39;i <span dir=3D"ltr">&=
lt;<a href=3D"mailto:seladwa@gmx.de" target=3D"_blank">seladwa@gmx.de</a>&g=
t;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left:1px solid rgb(204,204,204);padding-left:1ex">la .asiz. cu cusku di&#39=
;e<div class=3D"im"><br>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left:1px solid rgb(204,204,204);padding-left:1ex">
I noticed you sometimes use a property as binxo2, and sometimes a<br>
concrete object. I know you make use of overloading (or polymorphism),<br>
but I couldn&#39;t understand what your particular interpretation of each<b=
r>
version of {binxo} is that makes you sometimes use one version and<br>
sometimes another.<br>
</blockquote>
<br></div>
I think I use them more or less interchangeably, but one is often more conv=
enient than the other.<br>
<br>
With a concrete object, it means that one thing turns into another, as in:<=
div class=3D"im"><br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left:1px solid rgb(204,204,204);padding-left:1ex">
(7) {lo m=E0pku cu b=ECnxo lo t=E0nbo}<br>
</blockquote>
<br></div>
&quot;The cap turned into a board.&quot;<br>
<br>
It&#39;s just *really* useful to be able to say that.<br>
<br>
With a property it means &quot;to begin to have a property&quot; or &quot;t=
o undergo =A0a change towards having a property&quot;.<br>
<br>
I&#39;m not sure which one I would pick if I had to choose one over the oth=
er as the only acceptable binxo2. I think I might lean towards the concrete=
 object version, however. The other one could still be accessed via {kairbi=
&#39;o} =3D {binxo lo ckaji be lo ka}, while the exremely useful {binxo lo =
mlatu} would remain correct.<br>

<br>
mi&#39;e la selpa&#39;i mu&#39;o<span class=3D""><font color=3D"#888888"><b=
r>
<br>
-- <br>
You received this message because you are subscribed to the Google Groups &=
quot;lojban&quot; group.<br>
To unsubscribe from this group and stop receiving emails from it, send an e=
mail to <a href=3D"mailto:lojban%2Bunsubscribe@googlegroups.com" target=3D"=
_blank">lojban+unsubscribe@<u></u>googlegroups.com</a>.<br>
To post to this group, send email to <a href=3D"mailto:lojban@googlegroups.=
com" target=3D"_blank">lojban@googlegroups.com</a>.<br>
Visit this group at <a href=3D"http://groups.google.com/group/lojban" targe=
t=3D"_blank">http://groups.google.com/<u></u>group/lojban</a>.<br>
For more options, visit <a href=3D"https://groups.google.com/groups/opt_out=
" target=3D"_blank">https://groups.google.com/<u></u>groups/opt_out</a>.<br=
>
</font></span></blockquote></div><br></div></div>

<p></p>

-- <br />
You received this message because you are subscribed to the Google Groups &=
quot;lojban&quot; group.<br />
To unsubscribe from this group and stop receiving emails from it, send an e=
mail to lojban+unsubscribe@googlegroups.com.<br />
To post to this group, send email to lojban@googlegroups.com.<br />
Visit this group at <a href=3D"http://groups.google.com/group/lojban">http:=
//groups.google.com/group/lojban</a>.<br />
For more options, visit <a href=3D"https://groups.google.com/groups/opt_out=
">https://groups.google.com/groups/opt_out</a>.<br />

--089e01184b0c7159d104f0d433c4--