<p>Hi gang</p><p>New York State specifically exempts ham as we are also
considered emergency vehicles to an extent. I don't know the law offhand but you
can find it by looking it up on New York States DMV web
site.</p><p>Regards</p><p>Quoting aprssig-request@tapr.org:<br />
<br />
> Send aprssig mailing list submissions to<br />
> aprssig@tapr.org<br />
><br />
> To subscribe or unsubscribe via the World Wide Web, visit<br />
> <a target="_blank"
href="https://www.tapr.org/cgi-bin/mailman/listinfo/aprssig">https://www.tapr.org/cgi-bin/mailman/listinfo/aprssig</a><br
/>
> or, via email, send a message with subject or body 'help' to<br />
> aprssig-request@tapr.org<br />
><br />
> You can reach the person managing the list at<br />
> aprssig-owner@tapr.org<br />
><br />
> When replying, please edit your Subject line so it is more specific<br />
> than "Re: Contents of aprssig digest..."<br />
><br />
><br />
> Today's Topics:<br />
><br />
> 1. Re: Somewhat OT - Seeking Ham-friendly mobile cell<br />
> banlegislation? (Gary)<br />
> 2. Re: Somewhat OT - Seeking Ham-friendly mobile cell<br />
> banlegislation? (Mark Fellhauer)<br />
> 3. Re: Programming Language Advice (Jeff N0JUH)<br />
> 4. Re: Programming Language Advice (Tapio Sokura)<br />
> 5. Re: Programming Language Advice (J.C. Wren)<br />
> 6. Re: Programming Language Advice (Chuck.Gooden@comcast.net)<br />
> 7. Re: Programming Language Advice (J.C. Wren)<br />
> 8. test.....please ignore. (Chuck Gooden)<br />
> 9. Re: Programming Language Advice (Ray Wells)<br />
> 10. Re: Programming Language Advice (Ray Wells)<br />
><br />
><br />
> ----------------------------------------------------------------------<br
/>
><br />
> Message: 1<br />
> Date: Sun, 18 Jan 2009 10:28:30 -0800<br />
> From: "Gary" <n6lrv@cox.net><br />
> Subject: Re: [aprssig] Somewhat OT - Seeking Ham-friendly mobile cell<br />
> banlegislation?<br />
> To: "'K7FTP'" <k7ftp@k7ftp.net>, "'TAPR APRS Mailing
List'"<br />
> <aprssig@tapr.org><br />
> Message-ID: <003601c9799a$90c4a260$6402a8c0@Gary><br />
> Content-Type: text/plain; charset="US-ASCII"<br />
><br />
> Check out California's new hands free law here;<br />
> <<a target="_blank"
href="http://www.leginfo.ca.gov/cgi-bin/waisgate?WAISdocID=3025707913+0+0+0&WAISaction=retrieve">http://www.leginfo.ca.gov/cgi-bin/waisgate?WAISdocID=3025707913+0+0+0&WAISaction=retrieve</a>><br
/>
> See vehicle codes 23123 thru 23125.<br />
> Much debate took place beforehand and some of it was the result of <br />
> idiotic legislators trying to ban<br />
> all communications devices while mobile until their eyes were opened <br
/>
> to the fact that many<br />
> utilities, municipal agencies, taxis, amateur operators, and much <br />
> more are not only protected<br />
> (somewhat) from such legislation but also not the cause for so many <br />
> traffic collisions that begin<br />
> with "distraction by cell phone" highlighting the need for this
law <br />
> to begin with. Even though the<br />
> law has been in effect for more than a year now I still see numerous <br
/>
> drivers every day on their<br />
> phones(the old fashioned way) while driving on the highway.<br />
><br />
> Most importantly, please do not confuse "wireless telephone"
with <br />
> the legacy "phone" term used in<br />
> radio as they are not the same thing. The legislation literally <br />
> refers to common carrier cellular<br />
> type phones commonly used by the masses to distract themselves while <br
/>
> driving their motor vehicle<br />
> into the rear of another motor vehicle.<br />
> Gary<br />
><br />
> -----Original Message-----<br />
> From: aprssig-bounces@tapr.org [mailto:aprssig-bounces@tapr.org] On <br />
> Behalf Of K7FTP<br />
> Sent: Friday, January 16, 2009 2:10 PM<br />
> To: TAPR APRS Mailing List<br />
> Subject: [aprssig] Somewhat OT - Seeking Ham-friendly mobile cell <br />
> banlegislation?<br />
><br />
> Can anyone point me to an example of enacted (yet ham-friendly) mobile
cell<br />
> phone ban legislation?<br />
><br />
> One of our wonderful nanny-state legislators wants to ban everything<br />
> including two-way radio except in an emergency.<br />
><br />
><br />
> _______________________________________________<br />
> aprssig mailing list<br />
> aprssig@tapr.org<br />
> <a target="_blank"
href="https://www.tapr.org/cgi-bin/mailman/listinfo/aprssig">https://www.tapr.org/cgi-bin/mailman/listinfo/aprssig</a><br
/>
><br />
><br />
><br />
><br />
> ------------------------------<br />
><br />
> Message: 2<br />
> Date: Sun, 18 Jan 2009 13:13:28 -0800<br />
> From: Mark Fellhauer <sparkfel@qwest.net><br />
> Subject: Re: [aprssig] Somewhat OT - Seeking Ham-friendly mobile cell<br />
> banlegislation?<br />
> To: TAPR APRS Mailing List <aprssig@tapr.org><br />
> Message-ID: <4.3.2.7.2.20090118130500.036735d0@pop.sxfl.qwest.net><br
/>
> Content-Type: text/plain; charset="us-ascii"; format=flowed<br />
><br />
><br />
> California also ammended their motor vehicle laws to ALLOW the placement
of<br />
> portable GPS receivers on the windshield. The restriction is that the
GPSr<br />
> be placed in the lower extreme right or left portion of the windscreen.<br
/>
><br />
> Twice now, once in Las Vegas and once in Phoenix, police cars (one<br />
> unmarked) have come up behind me while I was talking on my cell phone
(not<br />
> hands-free) while driving and given me a short blast on the siren and a<br
/>
> little flashing light action, but then have driven on by. Just a
friendly<br />
> reminder from them not to do that...<br />
><br />
> 73,<br />
><br />
> Mark<br />
> KC7BXS<br />
><br />
><br />
> At 10:28 AM 1/18/2009, Gary wrote:<br />
>> Check out California's new hands free law here;<br />
>> <<a target="_blank"
href="http://www.leginfo.ca.gov/cgi-bin/waisgate?WAISdocID=3025707913+0+0+0&WAISaction=retrieve">http://www.leginfo.ca.gov/cgi-bin/waisgate?WAISdocID=3025707913+0+0+0&WAISaction=retrieve</a>><br
/>
>> See vehicle codes 23123 thru 23125.<br />
><br />
><br />
><br />
><br />
> ------------------------------<br />
><br />
> Message: 3<br />
> Date: Sun, 18 Jan 2009 18:15:41 -0600<br />
> From: Jeff N0JUH <jefflists08@corrt.com><br />
> Subject: Re: [aprssig] Programming Language Advice<br />
> To: TAPR APRS Mailing List <aprssig@tapr.org><br />
> Message-ID: <4973C62D.7000800@corrt.com><br />
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed<br />
><br />
> Bill Vodall WA7NWP wrote:<br />
>> I really hope folks here aren't encouraging anybody new to scripting<br
/>
>> to start with PERL. That's a really bad idea.<br />
>><br />
>> PERL is an incredible language and I use it every day. It is
somewhat<br />
>> cross platform and that's good, but the excitement in the
programming<br />
>> world these days is Python and others.<br />
><br />
> I'll second this. If you are going to learn a new programming language,<br
/>
> want to do quick'n'dirty scripts, but also want to develop some serious<br
/>
> applications someday, python is the way to go. I've been using it for<br
/>
> over ten years: everything from shell script replacements to terrain<br />
> modeling (with graphics) to large web-based inventory systems. It's<br />
> easy to learn, has a huge set of libraries, makes for fast development,<br
/>
> scales very well and is very sound from a computer science POV.<br />
><br />
> Why do the big software companies use C and C++? For optimum<br />
> performance, mostly. But a number of them do their *prototypes* in<br />
> python first. Most of Google's search engine product was originally<br />
> developed in python. Most ham software would work just fine at python<br
/>
> speeds - you can still do critical modules in C/C++ and link to them<br />
> from python.<br />
><br />
> Is python the best for embedded systems or other small-footprint<br />
> applications? Not really. C and C++ rule there. Though programmers<br />
> who prefer a higher-level / fast prototyping approach should check out<br
/>
> lua (www.lua.org)<br />
><br />
> my two cents...<br />
><br />
> -- Jeff n0juh<br />
><br />
><br />
><br />
><br />
><br />
> ------------------------------<br />
><br />
> Message: 4<br />
> Date: Mon, 19 Jan 2009 02:43:31 +0200<br />
> From: Tapio Sokura <oh2kku@iki.fi><br />
> Subject: Re: [aprssig] Programming Language Advice<br />
> To: TAPR APRS Mailing List <aprssig@tapr.org><br />
> Message-ID: <4973CCB3.1040104@iki.fi><br />
> Content-Type: text/plain; charset=UTF-8<br />
><br />
> Ray Wells wrote:<br />
>> Thanks for all the additional replies. I think the only language I'm<br
/>
>> proficient in at the moment is profane, after all the syntax errors
from<br />
>> perl :-)<br />
><br />
> Two suggestions for learning and using perl: always begin your scripts<br
/>
> with "use strict;" and "use warnings;". They force you
to be a bit more<br />
> disciplined when coding and warn you of things that could lead to<br />
> trouble. Taint checks (-T command line parameter) are sometimes useful<br
/>
> as well.<br />
><br />
> Tapio<br />
><br />
><br />
><br />
> ------------------------------<br />
><br />
> Message: 5<br />
> Date: Sun, 18 Jan 2009 19:58:36 -0500<br />
> From: "J.C. Wren" <jcwren@jcwren.com><br />
> Subject: Re: [aprssig] Programming Language Advice<br />
> To: TAPR APRS Mailing List <aprssig@tapr.org><br />
> Message-ID:<br />
>
<17434f2e0901181658r69369bd1u8fca50f96fde4c38@mail.gmail.com><br />
> Content-Type: text/plain; charset="iso-8859-1"<br />
><br />
> And for Python scripts, the first line should be:<br />
> #!/bin/perl<br />
><br />
> On Sun, Jan 18, 2009 at 7:43 PM, Tapio Sokura <oh2kku@iki.fi>
wrote:<br />
><br />
>> Ray Wells wrote:<br />
>> > Thanks for all the additional replies. I think the only language
I'm<br />
>> > proficient in at the moment is profane, after all the syntax
errors from<br />
>> > perl :-)<br />
>><br />
>> Two suggestions for learning and using perl: always begin your
scripts<br />
>> with "use strict;" and "use warnings;". They force
you to be a bit more<br />
>> disciplined when coding and warn you of things that could lead to<br />
>> trouble. Taint checks (-T command line parameter) are sometimes
useful<br />
>> as well.<br />
>><br />
>> Tapio<br />
>><br />
>> _______________________________________________<br />
>> aprssig mailing list<br />
>> aprssig@tapr.org<br />
>> <a target="_blank"
href="https://www.tapr.org/cgi-bin/mailman/listinfo/aprssig">https://www.tapr.org/cgi-bin/mailman/listinfo/aprssig</a><br
/>
>><br />
> -------------- next part --------------<br />
> An HTML attachment was scrubbed...<br />
> URL: <br />
> <a target="_blank"
href="http://www.tapr.org/pipermail/aprssig/attachments/20090118/e1e12841/attachment.html">http://www.tapr.org/pipermail/aprssig/attachments/20090118/e1e12841/attachment.html</a><br
/>
><br />
> ------------------------------<br />
><br />
> Message: 6<br />
> Date: Mon, 19 Jan 2009 01:06:20 +0000 (UTC)<br />
> From: Chuck.Gooden@comcast.net<br />
> Subject: Re: [aprssig] Programming Language Advice<br />
> To: TAPR APRS Mailing List <aprssig@tapr.org><br />
> Message-ID:<br />
>
<846050346.4382291232327180332.JavaMail.root@sz0039a.emeryville.ca.mail.comcast.net><br
/>
><br />
> Content-Type: text/plain; charset="utf-8"<br />
><br />
><br />
><br />
><br />
> No that's not correct, for Python scripts you use:<br />
><br />
><br />
><br />
> #!/bin/python<br />
><br />
><br />
><br />
> For Perl scripts use:<br />
><br />
><br />
><br />
> #!/bin/perl<br />
><br />
><br />
><br />
><br />
> ----- Original Message -----<br />
> From: "J.C. Wren" <jcwren@jcwren.com><br />
> To: "TAPR APRS Mailing List" <aprssig@tapr.org><br />
> Sent: Sunday, January 18, 2009 6:58:36 PM GMT -06:00 US/Canada Central<br
/>
> Subject: Re: [aprssig] Programming Language Advice<br />
><br />
> And for Python scripts, the first line should be:<br />
><br />
><br />
> #!/bin/perl?<br />
> -------------- next part --------------<br />
> An HTML attachment was scrubbed...<br />
> URL: <br />
> <a target="_blank"
href="http://www.tapr.org/pipermail/aprssig/attachments/20090119/78affe8c/attachment-0001.htm">http://www.tapr.org/pipermail/aprssig/attachments/20090119/78affe8c/attachment-0001.htm</a><br
/>
><br />
> ------------------------------<br />
><br />
> Message: 7<br />
> Date: Sun, 18 Jan 2009 20:45:12 -0500<br />
> From: "J.C. Wren" <jcwren@jcwren.com><br />
> Subject: Re: [aprssig] Programming Language Advice<br />
> To: TAPR APRS Mailing List <aprssig@tapr.org><br />
> Message-ID:<br />
>
<17434f2e0901181745t2fc1b6ebpaa3ed9fa8869ab95@mail.gmail.com><br />
> Content-Type: text/plain; charset="iso-8859-1"<br />
><br />
> Ah say, ah say, that's sarcasm there, son, sarcasm</foghorn
leghorn><br />
> Can't stand Python. Out of the 40 or so languages I've ever used, COBOL
and<br />
> Python are the only two that I'd rather flip burgers than use.<br />
><br />
> On Sun, Jan 18, 2009 at 8:06 PM, <Chuck.Gooden@comcast.net> wrote:<br
/>
><br />
>> No that's not correct, for Python scripts you use:<br />
>><br />
>><br />
>><br />
>> #!/bin/python<br />
>><br />
>><br />
>><br />
>> For Perl scripts use:<br />
>><br />
>><br />
>><br />
>> #!/bin/perl<br />
>><br />
>><br />
>><br />
>><br />
>> ----- Original Message -----<br />
>> From: "J.C. Wren" <jcwren@jcwren.com><br />
>> To: "TAPR APRS Mailing List" <aprssig@tapr.org><br />
>> Sent: Sunday, January 18, 2009 6:58:36 PM GMT -06:00 US/Canada
Central<br />
>> Subject: Re: [aprssig] Programming Language Advice<br />
>><br />
>> And for Python scripts, the first line should be:<br />
>><br />
>> #!/bin/perl<br />
>><br />
>> _______________________________________________<br />
>> aprssig mailing list<br />
>> aprssig@tapr.org<br />
>> <a target="_blank"
href="https://www.tapr.org/cgi-bin/mailman/listinfo/aprssig">https://www.tapr.org/cgi-bin/mailman/listinfo/aprssig</a><br
/>
>><br />
>><br />
> -------------- next part --------------<br />
> An HTML attachment was scrubbed...<br />
> URL: <br />
> <a target="_blank"
href="http://www.tapr.org/pipermail/aprssig/attachments/20090118/605106ad/attachment-0001.htm">http://www.tapr.org/pipermail/aprssig/attachments/20090118/605106ad/attachment-0001.htm</a><br
/>
><br />
> ------------------------------<br />
><br />
> Message: 8<br />
> Date: Sun, 18 Jan 2009 19:52:48 -0600<br />
> From: Chuck Gooden <Chuck.Gooden@comcast.net><br />
> Subject: [aprssig] test.....please ignore.<br />
> To: TAPR APRS Mailing List <aprssig@tapr.org><br />
> Message-ID: <4973DCF0.2080801@comcast.net><br />
> Content-Type: text/plain; charset=UTF-8; format=flowed<br />
><br />
><br />
><br />
><br />
><br />
><br />
> ------------------------------<br />
><br />
> Message: 9<br />
> Date: Mon, 19 Jan 2009 12:20:03 +1100<br />
> From: Ray Wells <vk2tv@exemail.com.au><br />
> Subject: Re: [aprssig] Programming Language Advice<br />
> To: TAPR APRS Mailing List <aprssig@tapr.org><br />
> Message-ID: <4973D543.1070809@exemail.com.au><br />
> Content-Type: text/plain; charset=UTF-8; format=flowed<br />
><br />
> Methinks you missed the twisted humour.<br />
><br />
> Ray vk2tv<br />
><br />
> Chuck.Gooden@comcast.net wrote:<br />
>><br />
>> No that's not correct, for Python scripts you use:<br />
>><br />
>><br />
>><br />
>> #!/bin/python<br />
>><br />
>><br />
>><br />
>> For Perl scripts use:<br />
>><br />
>><br />
>><br />
>> #!/bin/perl<br />
>><br />
>><br />
>><br />
>><br />
>> ----- Original Message -----<br />
>> From: "J.C. Wren" <jcwren@jcwren.com><br />
>> To: "TAPR APRS Mailing List" <aprssig@tapr.org><br />
>> Sent: Sunday, January 18, 2009 6:58:36 PM GMT -06:00 US/Canada
Central<br />
>> Subject: Re: [aprssig] Programming Language Advice<br />
>><br />
>> And for Python scripts, the first line should be:<br />
>><br />
>><br />
>> #!/bin/perl<br />
>>
------------------------------------------------------------------------<br />
>><br />
>> _______________________________________________<br />
>> aprssig mailing list<br />
>> aprssig@tapr.org<br />
>> <a target="_blank"
href="https://www.tapr.org/cgi-bin/mailman/listinfo/aprssig">https://www.tapr.org/cgi-bin/mailman/listinfo/aprssig</a><br
/>
>><br />
><br />
><br />
><br />
><br />
> ------------------------------<br />
><br />
> Message: 10<br />
> Date: Mon, 19 Jan 2009 11:48:38 +1100<br />
> From: Ray Wells <vk2tv@exemail.com.au><br />
> Subject: Re: [aprssig] Programming Language Advice<br />
> To: TAPR APRS Mailing List <aprssig@tapr.org><br />
> Message-ID: <4973CDE6.1060006@exemail.com.au><br />
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed<br />
><br />
> Tapio Sokura wrote:<br />
>> Ray Wells wrote:<br />
>><br />
>>> Thanks for all the additional replies. I think the only language
I'm<br />
>>> proficient in at the moment is profane, after all the syntax errors
from<br />
>>> perl :-)<br />
>>><br />
>><br />
>> Two suggestions for learning and using perl: always begin your
scripts<br />
>> with "use strict;" and "use warnings;". They force
you to be a bit more<br />
>> disciplined when coding and warn you of things that could lead to<br />
>> trouble. Taint checks (-T command line parameter) are sometimes
useful<br />
>> as well.<br />
>><br />
>> Tapio<br />
>><br />
>> _______________________________________________<br />
>> aprssig mailing list<br />
>> aprssig@tapr.org<br />
>> <a target="_blank"
href="https://www.tapr.org/cgi-bin/mailman/listinfo/aprssig">https://www.tapr.org/cgi-bin/mailman/listinfo/aprssig</a><br
/>
>><br />
>><br />
> I'm using both of those, thanks.<br />
><br />
> Ray vk2tv<br />
><br />
><br />
><br />
> ------------------------------<br />
><br />
> _______________________________________________<br />
> aprssig mailing list<br />
> aprssig@tapr.org<br />
> <a target="_blank"
href="https://www.tapr.org/cgi-bin/mailman/listinfo/aprssig">https://www.tapr.org/cgi-bin/mailman/listinfo/aprssig</a><br
/>
><br />
><br />
> End of aprssig Digest, Vol 55, Issue 22<br />
> ***************************************<br />
><br />
><br />
<br />
</p>