Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.forth > #42493 > unrolled thread

CATCH and THROW

Started byMark Wills <markwills1970@gmail.com>
First post2015-10-09 05:46 -0700
Last post2015-10-10 21:19 -1000
Articles 3 on this page of 23 — 10 participants

Back to article view | Back to comp.lang.forth


Contents

  CATCH and THROW Mark Wills <markwills1970@gmail.com> - 2015-10-09 05:46 -0700
    Re: CATCH and THROW anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2015-10-09 16:05 +0000
      Re: CATCH and THROW "Elizabeth D. Rather" <erather@forth.com> - 2015-10-09 08:30 -1000
        Re: CATCH and THROW JennyB <jennybrien@googlemail.com> - 2015-10-09 12:19 -0700
          Re: CATCH and THROW Mark Wills <markwills1970@gmail.com> - 2015-10-09 12:30 -0700
    Re: CATCH and THROW "Rod Pemberton" <boo@fasdfrewar.cdm> - 2015-10-09 23:21 -0400
      Re: CATCH and THROW Paul Rubin <no.email@nospam.invalid> - 2015-10-09 20:37 -0700
      Re: CATCH and THROW Mark Wills <markwills1970@gmail.com> - 2015-10-10 01:16 -0700
        Re: CATCH and THROW Gerry Jackson <gerry@jackson9000.fsnet.co.uk> - 2015-10-10 19:18 +0100
      Re: CATCH and THROW "HAA" <someone@microsoft.com> - 2015-10-11 12:18 +1000
        Re: CATCH and THROW hughaguilar96@gmail.com - 2015-10-10 23:21 -0700
          Re: CATCH and THROW rickman <gnuarm@gmail.com> - 2015-10-11 02:32 -0400
            Re: CATCH and THROW Paul Rubin <no.email@nospam.invalid> - 2015-10-10 23:51 -0700
              Re: CATCH and THROW rickman <gnuarm@gmail.com> - 2015-10-11 04:16 -0400
                Re: CATCH and THROW Paul Rubin <no.email@nospam.invalid> - 2015-10-11 23:27 -0700
                  Re: CATCH and THROW rickman <gnuarm@gmail.com> - 2015-10-12 02:39 -0400
                    Re: CATCH and THROW "Elizabeth D. Rather" <erather@forth.com> - 2015-10-11 21:26 -1000
                Re: CATCH and THROW "Elizabeth D. Rather" <erather@forth.com> - 2015-10-11 21:22 -1000
          Re: CATCH and THROW "Rod Pemberton" <boo@fasdfrewar.cdm> - 2015-10-12 01:29 -0400
            Re: CATCH and THROW rickman <gnuarm@gmail.com> - 2015-10-12 02:23 -0400
              Re: CATCH and THROW "Rod Pemberton" <boo@fasdfrewar.cdm> - 2015-10-12 19:52 -0400
                Re: CATCH and THROW rickman <gnuarm@gmail.com> - 2015-10-12 21:14 -0400
        Re: CATCH and THROW "Elizabeth D. Rather" <erather@forth.com> - 2015-10-10 21:19 -1000

Page 2 of 2 — ← Prev page 1 [2]


#42610

From"Rod Pemberton" <boo@fasdfrewar.cdm>
Date2015-10-12 19:52 -0400
Message-ID<op.x6e29n12yfako5@localhost>
In reply to#42587
On Mon, 12 Oct 2015 02:23:40 -0400, rickman <gnuarm@gmail.com> wrote:

> On 10/12/2015 1:29 AM, Rod Pemberton wrote:
>> On Sun, 11 Oct 2015 02:21:06 -0400, <hughaguilar96@gmail.com> wrote:

>>> my LC53 encryption-cracking program does this.
>>
>> Aren't you an U.S. citizen?
>>
>> Cracking is illegal under the DMCA.
>>
>> You need to have authority granted to
>> you from the copyright holder of LC53.
>> Even though that is you, you might
>> want to put it in writing just in
>> case they don't believe you ...
>
> Cracking encryption is not illegal under
> the DMCA.  Cracking encryption used to
> protect copyright is illegal.

Just what isn't automatically copyrighted under
state laws, and/or the Berne convention, upon
creation?  Everything is.  I.e., whatever he
decides to encrypt is copyrighted automatically.
Therefore, any cracking falls under the DMCA.
So, if he decides to crack encryption, even his
own, he must specificly obtain legal permission.
Per DMCA, Section 1201(a)(3)(A), you must be
authorized to decrypt.  That section does not
exclude the copyright holder from obtaining
authorization.

But, I'm not a lawyer ...


Rod Pemberton


-- 
Just how many texting and calendar apps does humanity need?
Just how many food articles from neurotic millenials do we need?

[toc] | [prev] | [next] | [standalone]


#42613

Fromrickman <gnuarm@gmail.com>
Date2015-10-12 21:14 -0400
Message-ID<mvhlqb$9r6$5@dont-email.me>
In reply to#42610
On 10/12/2015 7:52 PM, Rod Pemberton wrote:
> On Mon, 12 Oct 2015 02:23:40 -0400, rickman <gnuarm@gmail.com> wrote:
>
>> On 10/12/2015 1:29 AM, Rod Pemberton wrote:
>>> On Sun, 11 Oct 2015 02:21:06 -0400, <hughaguilar96@gmail.com> wrote:
>
>>>> my LC53 encryption-cracking program does this.
>>>
>>> Aren't you an U.S. citizen?
>>>
>>> Cracking is illegal under the DMCA.
>>>
>>> You need to have authority granted to
>>> you from the copyright holder of LC53.
>>> Even though that is you, you might
>>> want to put it in writing just in
>>> case they don't believe you ...
>>
>> Cracking encryption is not illegal under
>> the DMCA.  Cracking encryption used to
>> protect copyright is illegal.
>
> Just what isn't automatically copyrighted under
> state laws, and/or the Berne convention, upon
> creation?  Everything is.  I.e., whatever he
> decides to encrypt is copyrighted automatically.
> Therefore, any cracking falls under the DMCA.
> So, if he decides to crack encryption, even his
> own, he must specificly obtain legal permission.
> Per DMCA, Section 1201(a)(3)(A), you must be
> authorized to decrypt.  That section does not
> exclude the copyright holder from obtaining
> authorization.
>
> But, I'm not a lawyer ...

Exactly...

-- 

Rick

[toc] | [prev] | [next] | [standalone]


#42568

From"Elizabeth D. Rather" <erather@forth.com>
Date2015-10-10 21:19 -1000
Message-ID<192dnazjru34kIfLnZ2dnUU7-Yf46u6z@supernews.com>
In reply to#42557
On 10/10/15 4:18 PM, HAA wrote:
> Rod Pemberton wrote:
>>
>> Um, what are CATCH and THROW?  Why are they needed?
>
> It's for programmers who believe they know where a program
> will go wrong.

Basically, it's a mechanism to allow programmers to specify responses to 
possible error conditions. There are three likely categories: programmer 
errors, user interface errors, and equipment errors. All can be checked 
for, and appropriate responses programmed. Yes, it's like setjmp and 
longjmp in C.

Until Forth94, the only tool we had was blunt instruments: ABORT or 
ABORT" (without or with error messages, respectively). CATCH/THROW 
allows you to tune your error checking much more finely. If you're 
dealing with recalcitrant hardware, for example, you might find it 
useful to do a reset or retries. If it's user interface, you can reset 
the user interface to request better input. If it's a programmer error, 
you can say more about what it is and where it came from.

Read any Standard since Forth94 for more details.

Cheers,
Elizabeth

-- 
==================================================
Elizabeth D. Rather   (US & Canada)   800-55-FORTH
FORTH Inc.                         +1 310.999.6784
5959 West Century Blvd. Suite 700
Los Angeles, CA 90045
http://www.forth.com

"Forth-based products and Services for real-time
applications since 1973."
==================================================

[toc] | [prev] | [standalone]


Page 2 of 2 — ← Prev page 1 [2]

Back to top | Article view | comp.lang.forth


csiph-web