Am I not seeing the Error?

[Joel Goldstick]

On Mon, Aug 12, 2013 at 4:16 PM, Devyn Collier Johnson
<devyncjohnson at gmail.com> wrote:
>
> On 08/12/2013 12:56 PM, Joel Goldstick wrote:
>>
>> On Mon, Aug 12, 2013 at 11:47 AM, Roy Smith <roy at panix.com> wrote:
>>>
>>> I can't quite sort out the multiple quoting levels, but somebody said:
>>>
>>>>>> Programming like that is called trolling. A programmer that uses
>>>>>> trolling is called a troll. A troll can also refer to such a line
>>>>>> of code itself. My scripts contain a lot of trolls. It is easier
>>>>>> for me to read trolls than "typical" coding styles.
>>>
>>> Please tell me this is all just an elaborate joke.
>>
>> I was thinking something similar Roy.  Devyn, you may think you code
>> differently, but you don't.  You have a half of dozen people trying to
>> show you how your style causes confusion between what you think you
>> are writing and what you actually coded.  There is plenty of room in
>> coding for personal expression, but what you call 'trolling' is not
>> that.  If you like semicolons, use another language that needs them.
>> I think you think it is some version of premature optimization.  Since
>> you are a novice at the language, stick with the standards, and learn
>> to embrace them.  Ultimately standard coding styles has nothing to do
>> with code optimization.  It has to do with readability.  Although this
>> is a small example, you can see that if several people get involved
>> debugging it, the first thing that gets in the way is your
>> non-standard coding style.  If you want to code alone your whole life,
>> do as you like.  But the time spent reading and fixing code in the
>> lifetime of any useful software system is greater than the time spent
>> creating the original code.
>>>
>>> --
>>> http://mail.python.org/mailman/listinfo/python-list
>>
>>
>>
>
> I know using semicolons will not optimize the code, but it is actually
> easier for me to read. I can handle such code better than spacing it out.

Except it doesn't make it easier to read.


JOB_WRITEURGFILES =
multiprocessing.Process(write2file('./mem/ENGINE_PID', ENGINEPID);
write2file(SENTEMPPATH, ''); write2file(INPUTMEM, ''));
JOB_WRITEURGFILES.start()

As I understand it the above line of code caused you problems.  I
don't know what muliprocessing.Process() is supposed to have as
arguments, but I don't think is can have arguments with semicolons,
unless they appeared in a string.

So your semicolons, that you insist make your code easier to read,
have made code that doesn't work, and you don't know why.  All I am
saying is you are stating a fact not in evidence.  You only think the
semicolons are useful because you haven't taken the time to read and
write enough python code to appreciate that they are not only not
helpful, but they serve no useful purpose.  Sure, they allow you to
put several statements on a single line.  But that isn't what you were
doing.

good luck.  I can see you are interested.  keep at it.




>
> DCJ
> --
> http://mail.python.org/mailman/listinfo/python-list



-- 
Joel Goldstick
http://joelgoldstick.com