Re: Baby X is bor nagain

On 27/06/2024 23:24, Ben Bacarisse wrote:

bart <bc@freeuk.com> writes:
 

On 26/06/2024 13:15, Ben Bacarisse wrote:

bart <bc@freeuk.com> writes:
>

On 25/06/2024 16:12, David Brown wrote:

...

I /do/ use Python.  I use it when it is an appropriate language to use,
   which is very different circumstances from when I use C (or
C++). Different tools for different tasks.

>
And yet neither of you are interested in answering my question, which was
why its simplistic bytecode compiler is acceptable in this scenario, but
would be considered useless if applied to C code.

You throw out a lot of these sorts of question, by which I mean
questions that you either /do/ know the answers to or which you /should/
know the answers to.
If a software engineering student asked me this sort of "challenge"
question it would immediately become homework: come up with at least two
scenarios in which a simplistic C bytecode compiler would be an
unacceptable tool to use, and two in which Python with a trivial
bytecode compiler would be an acceptable tool to use.  In each case
explain why.  Anyone who could not would get marked down on the course.

>
I'm not sure what you're implying here.

 If you are not sure what I'm saying (and you think it worth finding out)
then you could ask some questions /about what I said/.  I was trying to
avoid implying anything, so please consider only what I actually said.
However, I can't easily explain it if you don't say what parts you
didn't follow.
 The basics are simple: you asked a question.  I think you aught to be
able to answer it yourself.  Can you answer your own question and
explain why those different kinds of tool might be appropriate in
certain scenarios?  If you now follow what I'm saying but can't answer
your own question, can you say why you can't?
 

Isn't it about the tradeoff between ease of development, vs speed of execution?