front end gfx for a redpitaya VNA

2021-10-23 Thread Gene Heskett
Greetings all; I have acquired the linux version of the front end for a redpitaya Vector Network Analyzer. Putting it on an rpi4b running raspbian buster, it gets to line 32 and bails out with this error: pi@rpi4:/media/pi/workspace/vna-linux-tool $ python3 ./vna.py Traceback (most recent

front end gfx for a redpitaya VNA

2021-10-23 Thread Gene Heskett
Greetings all; I have acquired the linux version of the front end for a redpitaya Vector Network Analyzer. Putting it on an rpi4b running raspbian buster, it gets to line 32 and bails out with this error: pi@rpi4:/media/pi/workspace/vna-linux-tool $ python3 ./vna.py Traceback (most recent

Re: Front end

2020-01-01 Thread James Lu
I would use software like Airtable. You set the columns, Airtable produces a type-checked form. Every spreadsheet also comes with its own API, so you can exfiltrate the data programmatically easily. On Sat, Dec 28, 2019, 10:36 L A Smit wrote: > Hi > > Don't know if this is the correct subject bu

Re: Front end

2019-12-28 Thread Terry Reedy
On 12/28/2019 5:52 AM, L A Smit wrote: Hi Don't know if this is the correct subject but i want a program like an invoice, You make an invoice and save it and the next one is ready to use. I am completely new to programming and want this program for myself. I want to use python to do it. Hav

Front end

2019-12-28 Thread L A Smit
Hi Don't know if this is the correct subject but i want a program like an invoice, You make an invoice and save it and the next one is ready to use. I am completely new to programming and want this program for myself. I want to use python to do it. Have already build the program but don't k

JOB | Front End Architect (London, UK)

2019-09-23 Thread James Tobin
Hello, I'm working with an employer that is looking to hire a permanent front end architect to join their London office. You should have experience with Javascript and frameworks such as (but not only) React. Consequently, I had hoped that some members of this mailing list may like to di

Re: Python Front-end to GCC

2013-11-15 Thread sharath . cs . smp
On Sunday, 20 October 2013 10:56:46 UTC-7, Philip Herron wrote: > Hey, > > > > I've been working on GCCPY since roughly november 2009 at least in its > > concept. It was announced as a Gsoc 2010 project and also a Gsoc 2011 > > project. I was mentored by Ian Taylor who has been an extremely b

Re: Python Front-end to GCC

2013-11-01 Thread Albert van der Horst
In article , Chris Kaynor wrote: >-=-=-=-=-=- >Global: > >int arr[10]; >int main() >{ > int i; > for (i = 0; i < 10; i++) { >printf("arr[%d] = %d\n", i, arr[i]); >} >printf("\n"); >return 0; >} > >As for a reference: >http://stackoverflow.com/questions/1831290/static-variable-i

[OT] Re: Python Front-end to GCC

2013-10-29 Thread Antoine Pitrou
Steven D'Aprano pearwood.info> writes: > > On Fri, 25 Oct 2013 21:36:42 +0100, Mark Lawrence wrote: > > > Mind you, the thought of a bot with a Ph.D. is mind boggling. > > You can buy degrees on the Internet quite cheaply: > > http://en.wikipedia.org/wiki/List_of_animals_with_fraudulent_diplom

Re: Python Front-end to GCC

2013-10-28 Thread Neil Cerutti
On 2013-10-28, Chris Angelico wrote: > On Tue, Oct 29, 2013 at 1:21 AM, Grant Edwards > wrote: >> On 2013-10-26, Mark Lawrence wrote: >>> On 26/10/2013 22:25, Mark Janssen wrote: >>> >>> Please give it a rest Mark, nobody is falling for your pseudo >>> babel. >> >> I think you do him a disservi

Re: Python Front-end to GCC

2013-10-28 Thread Chris Angelico
On Tue, Oct 29, 2013 at 1:21 AM, Grant Edwards wrote: > On 2013-10-26, Mark Lawrence wrote: >> On 26/10/2013 22:25, Mark Janssen wrote: >> >> Please give it a rest Mark, nobody is falling for your pseudo babel. > > I think you do him a disservice. I'm pretty sure it's genuine, > bona-fide, 24K,

Re: Python Front-end to GCC

2013-10-28 Thread Grant Edwards
On 2013-10-26, Mark Lawrence wrote: > On 26/10/2013 22:25, Mark Janssen wrote: > > Please give it a rest Mark, nobody is falling for your pseudo babel. I think you do him a disservice. I'm pretty sure it's genuine, bona-fide, 24K, dyed-in-the-wool, 99 and 44/100 pure babble. -- Grant Edwards

Re: Python Front-end to GCC

2013-10-27 Thread rusi
On Monday, October 28, 2013 3:44:14 AM UTC+5:30, zipher wrote: > Otherwise, most of this, while sloppy, still stands. Yes All your quotes are unattributed So your discussion is both sloppy and meaningless -- https://mail.python.org/mailman/listinfo/python-list

Re: Python Front-end to GCC

2013-10-27 Thread Mark Janssen
> I see the big man stepping in to answer for his homies After re-reading the discussion, I wish to retract what I'm saying here and apologize to John who seems like a decent guy. >, but while his > explanation satisfies their question of "well why do these magic > values get used then, if what M

Re: Python Front-end to GCC

2013-10-26 Thread Mark Janssen
> What a mess of a discussion. I see the big man stepping in to answer for his homies, but while his explanation satisfies their question of "well why do these magic values get used then, if what Mark says is true?", it doesn't address the real confusion: What is the difference between "script" c

Re: Python Front-end to GCC

2013-10-26 Thread Mark Lawrence
On 26/10/2013 22:25, Mark Janssen wrote: Please give it a rest Mark, nobody is falling for your pseudo babel. -- Python is the second best programming language in the world. But the best has yet to be invented. Christian Tismer Mark Lawrence -- https://mail.python.org/mailman/listinfo/python-

Re: Python Front-end to GCC

2013-10-26 Thread Mark Lawrence
On 26/10/2013 22:33, Mark Janssen wrote: Apologies will be accepted on the list. BTW, I can't resist pointing out that you guys are like a cup already full of (black) coffee -- too full to allow the pure water of clarity to enter. (cf. Buddhism) .. (boom) MarkJanssen Tacoma, Washington

Re: Python Front-end to GCC

2013-10-26 Thread John Nagle
On 10/25/2013 12:18 PM, Mark Janssen wrote: >> As for the hex value for Nan who really gives a toss? The whole point is >> that you initialise to something that you do not expect to see. Do you not >> have a text book that explains this concept? > > No, I don't think there is a textbook that exp

Re: Python Front-end to GCC

2013-10-26 Thread Mark Janssen
> Apologies will be accepted on the list. BTW, I can't resist pointing out that you guys are like a cup already full of (black) coffee -- too full to allow the pure water of clarity to enter. (cf. Buddhism) .. (boom) MarkJanssen Tacoma, Washington -- https://mail.python.org/mailman/listin

Re: Python Front-end to GCC

2013-10-26 Thread Mark Janssen
7;t >>> sufficient. >> >> A C program is just syntax also. How does the compiler generate >> executable machine code? Extrapolate into a Python front-end to C. > > Did you even read the paragraph you quoted above? The BNF specification > does NOT completely desc

Re: Python Front-end to GCC

2013-10-25 Thread Steven D'Aprano
On Fri, 25 Oct 2013 21:36:42 +0100, Mark Lawrence wrote: > Mind you, the thought of a bot with a Ph.D. is mind boggling. You can buy degrees on the Internet quite cheaply: http://en.wikipedia.org/wiki/List_of_animals_with_fraudulent_diplomas PhD's are more expensive, which leads me to think th

Re: Python Front-end to GCC

2013-10-25 Thread Chris Angelico
On Sat, Oct 26, 2013 at 8:37 AM, Mark Janssen wrote: > On Fri, Oct 25, 2013 at 2:07 PM, Ned Batchelder > wrote: >> (Offlist) You responded on-list to a private email that was even tagged as off-list. Please be more careful and courteous. Anyway, IEEE floating-point makes it pretty clear that a

Re: Python Front-end to GCC

2013-10-25 Thread xDog Walker
On Friday 2013 October 25 14:11, Mark Lawrence wrote: > Will you please do yourself a favour and get a new dealer before you do > some real damage, the batch you're currently on is definitely contaminated. Meet Mark Janssen: http://sourceforge.net/apps/mediawiki/pangaia/index.php?title=User:Avera

Re: Python Front-end to GCC

2013-10-25 Thread Mark Lawrence
On 25/10/2013 22:37, Mark Janssen wrote: I'm still waiting on the binary-digit lexer, Ned. The whole Python world is still waiting on your response to this http://code.activestate.com/lists/python-ideas/19908/. You were asked three times originally to respond. I've referenced this twice

Re: Python Front-end to GCC

2013-10-25 Thread Mark Janssen
On Fri, Oct 25, 2013 at 2:07 PM, Ned Batchelder wrote: > (Offlist) > > Mark, these conversations would go much more smoothly if you would make > direct statements about technical points. Your messages are usually > insinuating questions, or personal insults. Yes, thank you. That is correct. >

Re: Python Front-end to GCC

2013-10-25 Thread Mark Lawrence
On 25/10/2013 22:02, Mark Janssen wrote: But OTOH, it can also be explained away entirely by (as you previously noted) the Dunning-Kruger effect, with the same uninformed responses trotted out to everything. It was rusi who first mentioned this, I merely replied in my normal dead pan way. Slig

Re: Python Front-end to GCC

2013-10-25 Thread Mark Janssen
>> But OTOH, it can also be explained away entirely by (as you previously >> noted) the Dunning-Kruger effect, with the same uninformed responses >> trotted out to everything. > > It was rusi who first mentioned this, I merely replied in my normal dead pan > way. > > Slight aside, I spelt your surn

Re: Python Front-end to GCC

2013-10-25 Thread Mark Lawrence
On 25/10/2013 21:48, Tim Delaney wrote: But OTOH, it can also be explained away entirely by (as you previously noted) the Dunning-Kruger effect, with the same uninformed responses trotted out to everything. It was rusi who first mentioned this, I merely replied in my normal dead pan way. Sli

Re: Python Front-end to GCC

2013-10-25 Thread Tim Delaney
On 26 October 2013 07:36, Mark Lawrence wrote: > I can't see it being a bot on the grounds that a bot wouldn't be smart > enough to snip a URL that referred to itself as a quack. > My thought based on some of the responses is that they seem auto-generated, then tweaked - so not a bot per-se, but

Re: Python Front-end to GCC

2013-10-25 Thread Mark Lawrence
On 25/10/2013 21:29, Mark Janssen wrote: We've been discussing *DEBUGGING*. Are you making it LOUD and *clear* that you don't know what you're talking about? Input: Yes/no no Now please explain what you do not understand about the data below that's been written by Oscar Benjamin, myself an

Re: Python Front-end to GCC

2013-10-25 Thread Mark Lawrence
On 25/10/2013 21:11, Tim Delaney wrote: On 26 October 2013 06:18, Mark Janssen mailto:dreamingforw...@gmail.com>> wrote: > As for the hex value for Nan who really gives a toss? The whole point is > that you initialise to something that you do not expect to see. Do you not

Re: Python Front-end to GCC

2013-10-25 Thread Tim Delaney
On 26 October 2013 06:18, Mark Janssen wrote: > > As for the hex value for Nan who really gives a toss? The whole point is > > that you initialise to something that you do not expect to see. Do you > not > > have a text book that explains this concept? > > No, I don't think there is a textbook

Re: Python Front-end to GCC

2013-10-25 Thread Mark Janssen
>>> We've been discussing *DEBUGGING*. >> >> Are you making it LOUD and *clear* that you don't know what you're >> talking about? > > Input: Yes/no > > no > > Now please explain what you do not understand about the data below that's > been written by Oscar Benjamin, myself and Ned Batchelder, spec

Re: Python Front-end to GCC

2013-10-25 Thread Mark Janssen
>>> As for the hex value for Nan who really gives a toss? The whole point is >>> that you initialise to something that you do not expect to see. Do you >>> not have a text book that explains this concept? >> >> No, I don't think there is a textbook that explains such a concept of >> initializing

Re: Python Front-end to GCC

2013-10-25 Thread Mark Lawrence
On 25/10/2013 20:18, Mark Janssen wrote: As for the hex value for Nan who really gives a toss? The whole point is that you initialise to something that you do not expect to see. Do you not have a text book that explains this concept? No, I don't think there is a textbook that explains such a

Re: Python Front-end to GCC

2013-10-25 Thread rusi
On Saturday, October 26, 2013 12:39:09 AM UTC+5:30, zipher wrote: > On Fri, Oct 25, 2013 at 11:59 AM, rusi wrote: > > > > I dont see how thats any more relevant than: > > Whats the hex value of the add instruction? > > > You "don't see". That is correct. Btw, I believe the hex value for > the

Re: Python Front-end to GCC

2013-10-25 Thread Mark Janssen
> As for the hex value for Nan who really gives a toss? The whole point is > that you initialise to something that you do not expect to see. Do you not > have a text book that explains this concept? No, I don't think there is a textbook that explains such a concept of initializing memory to anyt

Re: Python Front-end to GCC

2013-10-25 Thread Grant Edwards
On 2013-10-25, Mark Janssen wrote: > OTOH why in particular would you want to initialise them with zeros? I > often initialise arrays to nan which is useful for debugging. >>> >>> Is this some kind of joke? What has this list become? >> >> It's a useful debugging technique to initialize m

Re: Python Front-end to GCC

2013-10-25 Thread Mark Janssen
On Fri, Oct 25, 2013 at 11:59 AM, rusi wrote: > On Saturday, October 26, 2013 12:15:43 AM UTC+5:30, zipher wrote: >> Clearly the python list has been taken over by TheKooks. Notice he >> did not respond to the request. Since we are talking about digital >> computers (with digital memory), I'm re

Re: Python Front-end to GCC

2013-10-25 Thread Mark Lawrence
On 25/10/2013 19:45, Mark Janssen wrote: OTOH why in particular would you want to initialise them with zeros? I often initialise arrays to nan which is useful for debugging. Is this some kind of joke? What has this list become? It's a useful debugging technique to initialize memory to distin

Re: Python Front-end to GCC

2013-10-25 Thread rusi
On Saturday, October 26, 2013 12:15:43 AM UTC+5:30, zipher wrote: > Clearly the python list has been taken over by TheKooks. Notice he > did not respond to the request. Since we are talking about digital > computers (with digital memory), I'm really curious what the hex value > for NaN is to init

Re: Python Front-end to GCC

2013-10-25 Thread Mark Janssen
>> OTOH why in particular would you want to initialise them with zeros? I >> often initialise arrays to nan which is useful for debugging. Is this some kind of joke? What has this list become? >>> >>> It's a useful debugging technique to initialize memory to distinctive >>> value

Re: Python Front-end to GCC

2013-10-25 Thread Mark Lawrence
On 25/10/2013 19:26, Mark Janssen wrote: OTOH why in particular would you want to initialise them with zeros? I often initialise arrays to nan which is useful for debugging. Is this some kind of joke? What has this list become? It's a useful debugging technique to initialize memory to distin

Re: Python Front-end to GCC

2013-10-25 Thread Mark Janssen
OTOH why in particular would you want to initialise them with zeros? I often initialise arrays to nan which is useful for debugging. >> >> Is this some kind of joke? What has this list become? > > It's a useful debugging technique to initialize memory to distinctive values > that should

Re: Python Front-end to GCC

2013-10-25 Thread Ned Batchelder
On 10/25/13 7:55 AM, Mark Janssen wrote: On Thu, Oct 24, 2013 at 8:40 PM, Mark Lawrence wrote: On 22/10/2013 18:37, Oscar Benjamin wrote: OTOH why in particular would you want to initialise them with zeros? I often initialise arrays to nan which is useful for debugging. Is this some kind of j

Re: Python Front-end to GCC

2013-10-25 Thread Mark Lawrence
On 25/10/2013 12:55, Mark Janssen wrote: On Thu, Oct 24, 2013 at 8:40 PM, Mark Lawrence wrote: On 22/10/2013 18:37, Oscar Benjamin wrote: OTOH why in particular would you want to initialise them with zeros? I often initialise arrays to nan which is useful for debugging. Is this some kind of

Re: Python Front-end to GCC

2013-10-25 Thread Dan Sommers
On Fri, 25 Oct 2013 04:55:43 -0700, Mark Janssen wrote: > On Thu, Oct 24, 2013 at 8:40 PM, Mark Lawrence > wrote: >> On 22/10/2013 18:37, Oscar Benjamin wrote: >>> OTOH why in particular would you want to initialise them with zeros? >>> I often initialise arrays to nan which is useful for debug

Re: Python Front-end to GCC

2013-10-25 Thread Mark Janssen
On Thu, Oct 24, 2013 at 8:40 PM, Mark Lawrence wrote: > On 22/10/2013 18:37, Oscar Benjamin wrote: >> OTOH why in particular would you want to initialise them with zeros? I >> often initialise arrays to nan which is useful for debugging. Is this some kind of joke? What has this list become? --

Re: Python Front-end to GCC

2013-10-23 Thread Stefan Behnel
Antoine Pitrou, 22.10.2013 10:55: > Philip Herron writes: >> Its interesting a few things come up what about: >> exec and eval. I didn't really have a good answer for this at my talk at >> PYCon IE 2013 but i am going to say no. I am >> not going to implement these. Partly because eval and exec at

Re: Python Front-end to GCC

2013-10-23 Thread John Nagle
On 10/23/2013 12:25 AM, Philip Herron wrote: > On Wednesday, 23 October 2013 07:48:41 UTC+1, John Nagle wrote: >> On 10/20/2013 3:10 PM, victorgarcia...@gmail.com wrote: >> >>> On Sunday, October 20, 2013 3:56:46 PM UTC-2, Philip Herron >>> wrote: > Nagle replies: >> Documentation can be fo

Re: Python Front-end to GCC

2013-10-23 Thread Mark Lawrence
On 23/10/2013 08:25, Philip Herron wrote: Personally I have no interest in your project but do wish you the best of luck with your endeavours. However I do have a personnal interest in my eyesite, which gets strained by reading posts such as yours. In order to assist me in looking after my

Re: Python Front-end to GCC

2013-10-23 Thread Philip Herron
On Wednesday, 23 October 2013 07:48:41 UTC+1, John Nagle wrote: > On 10/20/2013 3:10 PM, victorgarcia...@gmail.com wrote: > > > On Sunday, October 20, 2013 3:56:46 PM UTC-2, Philip Herron wrote: > > >> I've been working on GCCPY since roughly november 2009 at least in its > > >> concept. It was

Re: Python Front-end to GCC

2013-10-22 Thread John Nagle
On 10/20/2013 3:10 PM, victorgarcia...@gmail.com wrote: > On Sunday, October 20, 2013 3:56:46 PM UTC-2, Philip Herron wrote: >> I've been working on GCCPY since roughly november 2009 at least in its >> concept. It was announced as a Gsoc 2010 project and also a Gsoc 2011 >> project. I was mentored

Re: Python Front-end to GCC

2013-10-22 Thread Chris Angelico
On Wed, Oct 23, 2013 at 9:11 AM, Piet van Oostrum wrote: > Mark Janssen writes: > Is your language Turing complete? >>> >>> 1) No, it's not. >>> 2) So what? That should make it easier to compile to C, if anything. >>> 3) Don't change the subject. >> >> Well, if your language is not

Re: Python Front-end to GCC

2013-10-22 Thread Mark Lawrence
On 23/10/2013 05:05, Michael Torrie wrote: On 10/22/2013 12:28 PM, Mark Janssen wrote: Thank you. You may be seated. Ranting Rick, is that you? I think that's unfair, rr can be very helpful when discussing IDLE type issues. In comparison all that appears to have eminated from Tacoma, Wa

Re: Python Front-end to GCC

2013-10-22 Thread Mark Lawrence
On 23/10/2013 02:36, alex23 wrote: On 23/10/2013 4:40 AM, Ned Batchelder wrote: I've tried to be polite, and I've tried to be helpful, but I'm sorry: either you don't understand a lot of the terms you are throwing around, or you aren't disciplined enough to focus on a topic long enough to explai

Re: Python Front-end to GCC

2013-10-22 Thread Michael Torrie
On 10/22/2013 12:28 PM, Mark Janssen wrote: > Thank you. You may be seated. Ranting Rick, is that you? -- https://mail.python.org/mailman/listinfo/python-list

Re: Python Front-end to GCC

2013-10-22 Thread rusi
On Wednesday, October 23, 2013 7:06:40 AM UTC+5:30, alex23 wrote: > On 23/10/2013 4:40 AM, Ned Batchelder wrote: > > > I've tried to be polite, and I've tried to be helpful, but I'm sorry: > > either you don't understand a lot of the terms you are throwing around, > > or you aren't disciplined eno

Re: Python Front-end to GCC

2013-10-22 Thread alex23
On 23/10/2013 4:40 AM, Ned Batchelder wrote: I've tried to be polite, and I've tried to be helpful, but I'm sorry: either you don't understand a lot of the terms you are throwing around, or you aren't disciplined enough to focus on a topic long enough to explain yourself. Either way, I don't kno

Re: Python Front-end to GCC

2013-10-22 Thread Grant Edwards
On 2013-10-22, Mark Janssen wrote: >>> Is your language Turing complete? >>> >> >> 1) No, it's not. >> 2) So what? That should make it easier to compile to C, if anything. >> 3) Don't change the subject. > > Well, if your language is not Turing complete, it is not clear that > you will be abl

Re: Python Front-end to GCC

2013-10-22 Thread Piet van Oostrum
Mark Janssen writes: >>> Is your language Turing complete? >>> >> >> 1) No, it's not. >> 2) So what? That should make it easier to compile to C, if anything. >> 3) Don't change the subject. > > Well, if your language is not Turing complete, it is not clear that > you will be able to compile

Re: Python Front-end to GCC

2013-10-22 Thread Chris Angelico
On Wed, Oct 23, 2013 at 4:27 AM, Steven D'Aprano wrote: > On Tue, 22 Oct 2013 23:20:52 +1100, Chris Angelico wrote: > >> Considering that rapiding took about 1200ms (ish - again, cold cache) >> previously, adding even just 250ms is noticeable. > > Please excuse my skepticism, but in my experience,

Re: Python Front-end to GCC

2013-10-22 Thread Grant Edwards
On 2013-10-22, Grant Edwards wrote: > C initializes to defined zero values. For most machines in use today, > those values _happen_ to be all-bits-zero. > > This makes the implementation trivial: chuck them all into some > pre-defined section (e.g. ".bss"), and then on startup, you zero-out > al

Re: Python Front-end to GCC

2013-10-22 Thread Neil Cerutti
On 2013-10-22, Mark Lawrence wrote: > On 22/10/2013 20:27, Neil Cerutti wrote: >> On 2013-10-22, Piet van Oostrum wrote: >>> Neil Cerutti writes: Context-sensitive grammars can be parse, too. >>> >>> That's not English. Do you mean "parsed"? >> >> Thanks, yes, I meant parsed. >> >>> But con

Re: Python Front-end to GCC

2013-10-22 Thread Mark Lawrence
On 22/10/2013 20:27, Neil Cerutti wrote: On 2013-10-22, Piet van Oostrum wrote: Neil Cerutti writes: Context-sensitive grammars can be parse, too. That's not English. Do you mean "parsed"? Thanks, yes, I meant parsed. But context-sentitive grammars cannot be specified by BNF. Yes. I t

Re: Python Front-end to GCC

2013-10-22 Thread Mark Lawrence
On 22/10/2013 20:20, Piet van Oostrum wrote: Neil Cerutti writes: Context-sensitive grammars can be parse, too. That's not English. Do you mean "parsed"? But context-sentitive grammars cannot be specified by BNF. That's not English. Do you mean "context-sensitive"? :) -- Python is the

Re: Python Front-end to GCC

2013-10-22 Thread Neil Cerutti
On 2013-10-22, Piet van Oostrum wrote: > Neil Cerutti writes: >> Context-sensitive grammars can be parse, too. > > That's not English. Do you mean "parsed"? Thanks, yes, I meant parsed. > But context-sentitive grammars cannot be specified by BNF. Yes. I thought Mark might have had a misconcep

Re: Python Front-end to GCC

2013-10-22 Thread Piet van Oostrum
Neil Cerutti writes: > > Context-sensitive grammars can be parse, too. > That's not English. Do you mean "parsed"? But context-sentitive grammars cannot be specified by BNF. -- Piet van Oostrum WWW: http://pietvanoostrum.com/ PGP key: [8DAE142BE17999C4] -- https://mail.python.org/mailman/lis

Re: Python Front-end to GCC

2013-10-22 Thread Ned Batchelder
On 10/22/13 1:50 PM, Mark Janssen wrote: So which of you is confused? I ask that in the inclusive (not exclusive OR) sense ;^) <-- face says "both". Could you please be less snarky? We're trying to communicate here, and it is not at all clear yet who is confused and who is not. If you ar

Re: Python Front-end to GCC

2013-10-22 Thread Grant Edwards
On 2013-10-22, Neil Cerutti wrote: > On 2013-10-22, Steven D'Aprano wrote: >> On Tue, 22 Oct 2013 14:04:57 +, Dave Angel wrote: >>> but here you go on to say the C code is unsafely skipping >>> initialization, which is not the case. >> >> Are you talking generically, or specifically about the

Re: Python Front-end to GCC

2013-10-22 Thread Mark Lawrence
On 22/10/2013 19:40, rusi wrote: On Tuesday, October 22, 2013 11:53:22 PM UTC+5:30, Ned Batchelder wrote: A BNF doesn't provide enough information to compile a program to C. That's all I'm trying to help you understand. If you don't agree, then we have to talk about the meaning of the words BNF

Re: Python Front-end to GCC

2013-10-22 Thread Grant Edwards
On 2013-10-22, Steven D'Aprano wrote: > On Tue, 22 Oct 2013 16:53:07 +, Frank Miles wrote: > > [snip C code] >> What you're missing is that arr[] is an automatic variable. Put a >> "static" in front of it, or move it outside the function (to become >> global) and you'll see the difference. >

Re: Python Front-end to GCC

2013-10-22 Thread MRAB
On 22/10/2013 19:22, Mark Janssen wrote: Okay. The purpose of BNF (at least as I envision it) is to produce/specify a *context-free* "grammar". A lexer parses the tokens specified in the BNF into an Abstract Syntax Tree. If one can produce such a tree for any given source, the language, in the

Re: Python Front-end to GCC

2013-10-22 Thread rusi
On Tuesday, October 22, 2013 11:53:22 PM UTC+5:30, Ned Batchelder wrote: > A BNF doesn't provide enough information to compile a program to C. > That's all I'm trying to help you understand. If you don't agree, then > we have to talk about the meaning of the words BNF, compile, program, and C.

Re: Python Front-end to GCC

2013-10-22 Thread Ned Batchelder
On 10/22/13 2:22 PM, Mark Janssen wrote: Okay. The purpose of BNF (at least as I envision it) is to produce/specify a *context-free* "grammar". A lexer parses the tokens specified in the BNF into an Abstract Syntax Tree. If one can produce such a tree for any given source, the language, in the

Re: Python Front-end to GCC

2013-10-22 Thread Ned Batchelder
On 10/22/13 2:16 PM, Mark Janssen wrote: So which of you is confused? I ask that in the inclusive (not exclusive OR) sense ;^) <-- face says "both". Could you please be less snarky? Okay. The purpose of BNF (at least as I envision it) is to produce/specify a *context-free* "grammar". A

Re: Python Front-end to GCC

2013-10-22 Thread Mark Janssen
>> Is your language Turing complete? >> > > 1) No, it's not. > 2) So what? That should make it easier to compile to C, if anything. > 3) Don't change the subject. Well, if your language is not Turing complete, it is not clear that you will be able to compile it at all. That's the difference

Re: Python Front-end to GCC

2013-10-22 Thread Mark Janssen
>> Okay. The purpose of BNF (at least as I envision it) is to >> produce/specify a *context-free* "grammar". A lexer parses the tokens >> specified in the BNF into an Abstract Syntax Tree. If one can produce >> such a tree for any given source, the language, in theory, can be >> compiled by GCC

Re: Python Front-end to GCC

2013-10-22 Thread Neil Cerutti
On 2013-10-22, Mark Janssen wrote: >>> So which of you is confused? I ask that in the inclusive (not >>> exclusive OR) sense ;^) <-- face says "both". >> >> Could you please be less snarky? We're trying to communicate here, and it >> is not at all clear yet who is confused and who is not.

Re: Python Front-end to GCC

2013-10-22 Thread Mark Janssen
So which of you is confused? I ask that in the inclusive (not exclusive OR) sense ;^) <-- face says "both". >>> >>> Could you please be less snarky? >> >> Okay. The purpose of BNF (at least as I envision it) is to >> produce/specify a *context-free* "grammar". A lexer parses the t

Re: Python Front-end to GCC

2013-10-22 Thread MRAB
On 22/10/2013 18:50, Mark Janssen wrote: So which of you is confused? I ask that in the inclusive (not exclusive OR) sense ;^) <-- face says "both". Could you please be less snarky? We're trying to communicate here, and it is not at all clear yet who is confused and who is not. If you a

Re: Python Front-end to GCC

2013-10-22 Thread rusi
omputer science > point of view is a app that will take a language specification in BNF > (complete with keywords and all) and output C code which is then > compiled to an executable as normal. This is how a front-end should > be designed. A middle-layer for translating common languag

Re: Python Front-end to GCC

2013-10-22 Thread Skip Montanaro
On Tue, Oct 22, 2013 at 12:50 PM, Mark Janssen wrote: > Okay. The purpose of BNF (at least as I envision it) is to > produce/specify a *context-free* "grammar". A lexer parses the tokens > specified in the BNF into an Abstract Syntax Tree. If one can produce > such a tree for any given source,

Re: Python Front-end to GCC

2013-10-22 Thread Mark Janssen
>> So which of you is confused? I ask that in the inclusive (not >> exclusive OR) sense ;^) <-- face says "both". > > Could you please be less snarky? We're trying to communicate here, and it > is not at all clear yet who is confused and who is not. If you are > interested in discussing tec

Re: Python Front-end to GCC

2013-10-22 Thread MRAB
On 22/10/2013 18:23, Steven D'Aprano wrote: On Tue, 22 Oct 2013 16:53:07 +, Frank Miles wrote: [snip C code] What you're missing is that arr[] is an automatic variable. Put a "static" in front of it, or move it outside the function (to become global) and you'll see the difference. Ah, th

Re: Python Front-end to GCC

2013-10-22 Thread Neil Cerutti
On 2013-10-22, Steven D'Aprano wrote: > On Tue, 22 Oct 2013 16:53:07 +, Frank Miles wrote: > > [snip C code] >> What you're missing is that arr[] is an automatic variable. Put a >> "static" in front of it, or move it outside the function (to become >> global) and you'll see the difference. >

Re: Python Front-end to GCC

2013-10-22 Thread Chris Kaynor
On Tue, Oct 22, 2013 at 10:23 AM, Steven D'Aprano < steve+comp.lang.pyt...@pearwood.info> wrote: > On Tue, 22 Oct 2013 16:53:07 +, Frank Miles wrote: > > [snip C code] > > What you're missing is that arr[] is an automatic variable. Put a > > "static" in front of it, or move it outside the fun

Re: Python Front-end to GCC

2013-10-22 Thread Steven D'Aprano
On Tue, 22 Oct 2013 23:20:52 +1100, Chris Angelico wrote: > Considering that rapiding took about 1200ms (ish - again, cold cache) > previously, adding even just 250ms is noticeable. Please excuse my skepticism, but in my experience, that would probably mean in practice: ... rapiding took about

Re: Python Front-end to GCC

2013-10-22 Thread Piet van Oostrum
BNF is used to produce parsers. But a parser isn't >>>> sufficient. >>> >>> A C program is just syntax also. How does the compiler generate >>> executable machine code? Extrapolate into a Python front-end to C. > > [Dave Angel responds:] >> Did you e

Re: Python Front-end to GCC

2013-10-22 Thread Steven D'Aprano
On Tue, 22 Oct 2013 16:53:07 +, Frank Miles wrote: [snip C code] > What you're missing is that arr[] is an automatic variable. Put a > "static" in front of it, or move it outside the function (to become > global) and you'll see the difference. Ah, that makes sense. Thanks to everyone who cor

Re: Python Front-end to GCC

2013-10-22 Thread Neil Cerutti
On 2013-10-22, Steven D'Aprano wrote: > On Tue, 22 Oct 2013 14:04:57 +, Dave Angel wrote: >> but here you go on to say the C code is unsafely skipping >> initialization, which is not the case. > > Are you talking generically, or specifically about the C code > referenced in the link I gave? >

Re: Python Front-end to GCC

2013-10-22 Thread Steven D'Aprano
rsers. But >>>> a parser isn't sufficient. >>> >>> A C program is just syntax also. How does the compiler generate >>> executable machine code? Extrapolate into a Python front-end to C. > > [Dave Angel responds:] >> Did you even read the

Re: Python Front-end to GCC

2013-10-22 Thread Frank Miles
On Tue, 22 Oct 2013 16:40:32 +, Steven D'Aprano wrote: > On Tue, 22 Oct 2013 15:39:42 +, Grant Edwards wrote: > >>> No, I was thinking of an array. Arrays aren't automatically >>> initialised in C. >> >> If they are static or global, then _yes_they_are_. They are zeroed. > > Not that I

Re: Python Front-end to GCC

2013-10-22 Thread Chris Kaynor
On Tue, Oct 22, 2013 at 9:40 AM, Steven D'Aprano < steve+comp.lang.pyt...@pearwood.info> wrote: > On Tue, 22 Oct 2013 15:39:42 +, Grant Edwards wrote: > > >> No, I was thinking of an array. Arrays aren't automatically initialised > >> in C. > > > > If they are static or global, then _yes_they_

Re: Python Front-end to GCC

2013-10-22 Thread Mark Lawrence
On 22/10/2013 17:40, Steven D'Aprano wrote: On Tue, 22 Oct 2013 15:39:42 +, Grant Edwards wrote: No, I was thinking of an array. Arrays aren't automatically initialised in C. If they are static or global, then _yes_they_are_. They are zeroed. Not that I don't believe you, but do you ha

Re: Python Front-end to GCC

2013-10-22 Thread Steven D'Aprano
On Tue, 22 Oct 2013 15:39:42 +, Grant Edwards wrote: >> No, I was thinking of an array. Arrays aren't automatically initialised >> in C. > > If they are static or global, then _yes_they_are_. They are zeroed. Not that I don't believe you, but do you have a reference for this? Because I kee

Re: Python Front-end to GCC

2013-10-22 Thread Benjamin Kaplan
>>> for a program? BNF is used to produce parsers. But a parser isn't >>>> sufficient. >>> >>> A C program is just syntax also. How does the compiler generate >>> executable machine code? Extrapolate into a Python front-end to C. > > [Dave Ange

Re: Python Front-end to GCC

2013-10-22 Thread Mark Lawrence
On 22/10/2013 16:46, Ned Batchelder wrote: Could you please be less snarky? We're trying to communicate here, and it is not at all clear yet who is confused and who is not. If you are interested in discussing technical topics, then discuss them. --Ned. Well put, particularly when consideri

Re: Python Front-end to GCC

2013-10-22 Thread Antoine Pitrou
Steven D'Aprano pearwood.info> writes: > > On Tue, 22 Oct 2013 08:55:15 +, Antoine Pitrou wrote: > > > If you don't implement exec() and eval() then people won't be able to > > use namedtuples, which are a common datatype factory. > > Philip could always supply his own implementation of nam

Re: Python Front-end to GCC

2013-10-22 Thread Ned Batchelder
isn't sufficient. A C program is just syntax also. How does the compiler generate executable machine code? Extrapolate into a Python front-end to C. [Dave Angel responds:] Did you even read the paragraph you quoted above? The BNF specification does NOT completely describe a language, it only d

  1   2   >