Greg:
>
> Well, we may need to devise some tests to be sure this is still a
> problem, but in the past, Windows would deliver binary files in
> 128-byte chunks, meaning that the last chunk might have garbage at the
> end of it that was not actually produced by the program that sent it.
>
Am 2016-03-22 01:34, schrieb Gregory J. Ward:
Well, it's still not obvious to me, even after Randoph's explanation
(which used different calls). In any case, I was only trying to make
the point that Python isn't transparent, either.
An unknown language is never immediately transparent
I don’t think it’s as awful as that; Python is a widely-known, widely-used, and
well-documented language and freely available. I worry more about Perl,
because it is so easy to create write-only code in Perl and this becomes a
maintenance problem.
On the other hand some Unix commands are
Real quick:
> From: "Guglielmetti, Robert"
> Date: March 22, 2016 9:37:46 AM PDT
>
> Eh, I respectfully disagree, here. Languages like Python and Ruby are
> making it easy for meatheads like me to write functional cross-platform
> programs that can leverage
This is getting good...
On 3/22/16, 10:02 AM, "Gregory J. Ward" wrote:
>
>Thinking on it some more, the main issue I have with Python is probably
>the object-oriented structure, which moves it even further from a
>command-line interpreter. For me, the main benefit of
Removing some stuff to keep things from getting too drawn-out...
> From: Georg Mischler
> Subject: Re: [Radiance-dev] Python scripts for Radiance
> Date: March 22, 2016 4:49:39 AM PDT
>
> Am 2016-03-22 01:34, schrieb Gregory J. Ward:
> ...
> Where did you see a
Am 2016-03-22 01:34, schrieb Gregory J. Ward:
Getting old? That, I am!
Hehe, so am I!
Seriously, though, what's up with all the double-subscripts on string
arrays? Seems you always need string[0][0] to access a word, when I
would expect just one subscript unless you want a character.