On 17 June 2013 19:14, H. S. Teoh <hsteoh@quickfur.ath.cx> wrote:
> On Sun, Jun 16, 2013 at 06:29:21PM -0700, Walter Bright wrote:
>> http://www.reddit.com/r/programming/comments/1gfk15/ć_programming_language_compile_c_subset_to_c_java/
>
> How on earth do you pronounce the name of this language? :-(  "Cee acute"? I'm tempted to propose renaming it to C-flat. :-P
>

That's a B!  :o)


In an unrelated (musical) note... a C, an Eb and a G walk into a bar, the bartender says:  "Sorry, we don't server minors".

A tumbleweed rolls past...

--
Iain Buclaw

*(p < e ? p++ : p) = (c & 0x0f) + '0'

On Tue, Jun 18, 2013 at 12:40:56AM +0100, Iain Buclaw wrote:
> On 17 June 2013 19:14, H. S. Teoh <hsteoh@quickfur.ath.cx> wrote:
> > On Sun, Jun 16, 2013 at 06:29:21PM -0700, Walter Bright wrote:
> >> http://www.reddit.com/r/programming/comments/1gfk15/ć_programming_language_compile_c_subset_to_c_java/
> >
> > How on earth do you pronounce the name of this language? :-(  "Cee acute"? I'm tempted to propose renaming it to C-flat. :-P
> >
> 
> That's a B!  :o)
> 
> 
> In an unrelated (musical) note... a C, an Eb and a G walk into a bar, the bartender says:  "Sorry, we don't server minors".
[...]

Bartender? I thought it would be the time signature raising an objection... from extra notes in the bar! :-)


T

-- 
Laissez-faire is a French term commonly interpreted by Conservatives to mean 'lazy fairy,' which is the belief that if governments are lazy enough, the Good Fairy will come down from heaven and do all their work for them.

On Monday, 17 June 2013 at 23:24:28 UTC, Walter Bright wrote:
>
> Why not try it on your machine and report what the autocomplete says?

Through secure Tor network with no history on my end anyway, I typed as far as "d pr" and "d programming" showed up as the second item in the list, so I would also say that D the language is easy to find these days.

--rt

On 6/18/13, monarch_dodra <monarchdodra@gmail.com> wrote:
> On Monday, 17 June 2013 at 21:33:20 UTC, Walter Bright wrote:
>> I tried it on a machine I never use google on, and I got the same autocomplete results.
>
> So anybody want to talk about the language?

I don't see much point in the language. If you limit yourself to a minimalistic language in order for your library to be translatable, how will the API look like in the target languages? It won't use any language-specific features that make APIs easy to uses (for example it likely won't provide any range functionality or templates in D..).

You might as well use C, or C++ with some extern "C" API functions. Then you can write a stable API, have full optimizations, and can even distribute the built binaries for some platforms (and you build once per platform, instead of N*platforms * N*languages). Most languages can interface with C too.

On Tuesday, 18 June 2013 at 02:17:19 UTC, Andrej Mitrovic wrote:
> On 6/18/13, monarch_dodra <monarchdodra@gmail.com> wrote:
>> On Monday, 17 June 2013 at 21:33:20 UTC, Walter Bright wrote:
>>> I tried it on a machine I never use google on, and I got the
>>> same autocomplete results.
>>
>> So anybody want to talk about the language?
>
> I don't see much point in the language. If you limit yourself to a
> minimalistic language in order for your library to be translatable,
> how will the API look like in the target languages? It won't use any
> language-specific features that make APIs easy to uses (for example it
> likely won't provide any range functionality or templates in D..).
>
> You might as well use C, or C++ with some extern "C" API functions.
> Then you can write a stable API, have full optimizations, and can even
> distribute the built binaries for some platforms (and you build once
> per platform, instead of N*platforms * N*languages). Most languages
> can interface with C too.

One of the problems (which is always a pain), is to link the actual C code, which is always a task in itself. Also, as the authors presented it, it can also work for "deployable languages", such a javascript, which wouldn't work with C.

It's true the language only has access to the lowest common denominator of features.

I hadn't thought about "API stability": indeed, looking through the examples, each language has its own variants in the translation: EG the casing between C# and Java:
http://cito.sourceforge.net/hello.html

It also seems to be trying to target both GC and non GC languages, which appears to make a mess of things... For example it currently doesn't allow string concatenation.

Also, for classes: "new C() allocates new instance of class C and returns a pointer to it. If you target the C programming language, delete the allocated object some time later." Ouch.