Re: [dev] lsw 0.3

2014-11-27 Thread Dmitrij D. Czarkoff
Anselm R Garbe said: > I will create a formal release tonight. Thanks! -- Dmitrij D. Czarkoff

Re: [dev] K, a low-level procedural imperative programming language

2014-11-27 Thread M Farkas-Dyck
On 27/11/2014, M Farkas-Dyck wrote: > • Unambiguous grammar > • Low level > • Tuples > • Easy interface with C Forgot one: • Free declaration order On 27/11/2014, Troels Henriksen wrote: > The only implementation seems to be written in a pretty atrocious style: > https://github.com/strake/pkc/b

Re: [dev] K, a low-level procedural imperative programming language

2014-11-27 Thread Troels Henriksen
M Farkas-Dyck writes: > Given the comments on alternatives to C lately on dev@ I thought this > a good time to introduce mine: http://k-lang.org/ The only implementation seems to be written in a pretty atrocious style: https://github.com/strake/pkc/blob/master/CodeGen/Common.hs Also - why care

Re: [dev] K, a low-level procedural imperative programming language

2014-11-27 Thread M Farkas-Dyck
On 27/11/2014, FRIGN wrote: > No, bloody you! ... I'm proposing the language. If you want to claim that my language won't work, and fill out the checklist, feel free; I'll be over here, using it.

Re: [dev] K, a low-level procedural imperative programming language

2014-11-27 Thread FRIGN
On Thu, 27 Nov 2014 16:35:42 -0500 M Farkas-Dyck wrote: > Who? "You" is a 2nd-person pronoun. Richard Stallman of course. ... No, bloody you! -- FRIGN

Re: [dev] K, a low-level procedural imperative programming language

2014-11-27 Thread M Farkas-Dyck
On 27/11/2014, FRIGN wrote: > On Thu, 27 Nov 2014 15:47:08 -0500 > M Farkas-Dyck wrote: >> > > Fill out the checklist[0] already (just copy/paste it in your > mail-client and tick) ;) Who? "You" is a 2nd-person pronoun.

[dev] Re: Questions about sta.li

2014-11-27 Thread Henrique Lengler
Hi, Is there anything already done about it? I can't find it on the git repository. I'm very interested and I would like to help to bring sta.li to reality. Regards, -- Henrique Lengler

Re: [dev] K, a low-level procedural imperative programming language

2014-11-27 Thread FRIGN
On Thu, 27 Nov 2014 15:47:08 -0500 M Farkas-Dyck wrote: > Fill out the checklist[0] already (just copy/paste it in your mail-client and tick) ;) Cheers FRIGN [0]: http://colinm.org/language_checklist.html -- FRIGN

Re: [dev] K, a low-level procedural imperative programming language

2014-11-27 Thread M Farkas-Dyck
On 27/11/2014, Wander Nauta wrote: > What does your language have to offer? Is it safety? Expressiveness? > Productivity? Ease of use? • Unambiguous grammar • Low level • Tuples • Easy interface with C > Do K programs run faster than C programs? Not in general. > Also, what is a 'for loop afte

Re: [dev] K, a low-level procedural imperative programming language

2014-11-27 Thread pancake
c makes hidden heap allocations? Wat > On 27 Nov 2014, at 19:39, Wander Nauta wrote: > > What does your language have to offer? Is it safety? Expressiveness? > Productivity? Ease of use? Do K programs run faster than C programs? > > Also, what is a 'for loop afterthot' (sic), why are the oper

Re: [dev] Object-Oriented C for interface safety?

2014-11-27 Thread random832
On Thu, Nov 27, 2014, at 07:27, koneu wrote: > Greetings. > > The two things that really make OO languages worthwhile in my opinion > are polymorphism and inheritance. Doing polymorphism and data/code > hiding in C is easy enough with const function pointers. You can just > define public interface

Re: [dev] K, a low-level procedural imperative programming language

2014-11-27 Thread Wander Nauta
What does your language have to offer? Is it safety? Expressiveness? Productivity? Ease of use? Do K programs run faster than C programs? Also, what is a 'for loop afterthot' (sic), why are the operators all weird, why do you use parentheses where every C-like language uses braces and why are inte

[dev] Re: K, a low-level procedural imperative programming language

2014-11-27 Thread M Farkas-Dyck
On 27/11/2014, M Farkas-Dyck wrote: > This is very much a work in progress. In particular I not yet know how > to do arrays, modules/includes, or macros sanely. Or atomics.

[dev] K, a low-level procedural imperative programming language

2014-11-27 Thread M Farkas-Dyck
Given the comments on alternatives to C lately on dev@ I thought this a good time to introduce mine: http://k-lang.org/ The goal is a language appropriate for systems programs including kernels, sans some flaws of C. This likely means no hidden heap allocations. This is very much a work in progre

Re: [dev] Object-Oriented C for interface safety?

2014-11-27 Thread M Farkas-Dyck
On 27/11/2014, koneu wrote: > Of course each "class" can only implement one interface. Why? C lacking tuple types makes implementing more awkward but not impossible.

Re: [dev] Object-Oriented C for interface safety?

2014-11-27 Thread koneu
Greetings. The two things that really make OO languages worthwhile in my opinion are polymorphism and inheritance. Doing polymorphism and data/code hiding in C is easy enough with const function pointers. You can just define public interfaces in their own header like struct interface { v

Re: [dev] Object-Oriented C for interface safety?

2014-11-27 Thread Martti Kühne
On Wed, Nov 26, 2014 at 10:55 PM, pancake wrote: > Try Cello > I did try Cello. Cello turned out absolutely useless for me as interfacing it with other C standard types is a PITA / completely broken. After fiddling around for a while I got sick from what Cello does with code I would write and ga