NetRexx Compiler Deficiency -- leading wrong syntax not recognized properly

[Thomas.Schneider.Wien]

  Hello there,
    whilst we are on the issues of 'Netrexx bugs':

1.) It is a pity, that in the year 2010 neither ibm-netrexx nor REXXLA
does allow *attached files*
fto communicate a problem (*personal opinion*) :-(

2.) This would simplify the reporting of problems or distributing
example programs of a reasonable length
a lot (*personal opinion*) :-)

3.) The objective of this mail is to show you a*small* deficiency of the
*current :NetRexx Compiler*

When a *wrong* syntax (as in the example below) is used, a totally
misleading error message is given!

Note, for instance, that NetRexxC reports:

Error: 'Class nrcdoc' instruction has already been implied for this program

whilst the (*my*) error is much more trivial:

    (the *********************************************/ at the end of an
already closed comment)

As I did learn that by my own faults, I can live with this ...

but maybe it should be corrected in NetRexx 3 ??

Tom.
================================================================================

/**
  * nrcdoc.nrx: a small implementation of NetRexx documentation tool
  * @author Th. Schneider, www.thsitc.com, all rights reserved
  */
/**
  * @History
  * 16.08.2010 : Original (trial) version
  */*****************************************************/

import com.thsitc.rey.rt.

class nrcdoc uses ReyFile, ReyMsg, ReyFunc, ReyTime

properties private static

    version='0.2'
    ix = int 0
    FD_in_file = ReyFile Null
    in_file = Rexx ''

    file_list = Rexx ''
    extensions  = Rexx ''
    file_stem = Rexx '' /* the Stem returned by FileList */

    recursive= boolean 1 /* flag whether recursive is wanted */
    n_nrx        = int 0 -- total number of NetRexx Sources
    n_documented = int 0 -- total number of documented files
    n_java       = int 0 -- total num

    recursive=boolean 0 -- flag wether directory recursion should be used

method main(args=String[]) public static
    arg=Rexx(args) -- program arguments as single string
    arg=arg -- avoid NetRexx warning

    t1=time('R')

    arg=arg.changestr(' since ',' SINCE ') /* as we do not have a parse
caseless in NetRexx */

    init_info('nrcdoc','NEW')  /* LOG-File of last 'nrcdoc' command */
    info('NRCDOC vs. 'version)

    if arg='' then do
       info(' ')
       info('NRCDOC builds a JavaDoc style documentation for all NetRexx')
       info('       programs of a given directory and all of it\'s')
       info('       subdirectories (unless option NOREC is used')
       info(' ')
       info('short invocation:')
       info(' ')
       info('NRCDOC file-list [-option1 ...]')
       info('')
       info('Option -NOREC suppresses the recursive execution of all
subdirectories')
       info(' ')

       file_list=arg -- process givenALL files of ALL subdirectories
       -- options still not processed
       yes_no=askfor('Should directories be recursed','yes/no')
       -- ReyMsg.debug('yes_no is:' yes_no)

       if yes_no='yes' then recursive=1
       else recursive = 0
   end
   else do
      parse arg . ' -' option
      option = option.upper()
      select case option
         when '' then nop
         when 'NOREC' then recursive=0
         otherwise ReyMsg.abort('illegal option: 'option)
      end

   end


   nf = 0

   /* we are interested in ALL Files here */
   extensions='nrx' -- we are ONLY interested in NetRexx files

   if recursive=0 then dir_name='' -- only current directory
   else dir_name='*'               -- indicates current directory and
all sub-directories

   /* note that FileList does now return the FULL file-name */
   file_stem=ReyFile.FileList(file_list,dir_name,extensions) /* expand
filelist */

   /* note that file_stem is a STEM! */
    n_files=file_stem[0]
    if n_files=0 then do
      info0(n_files 'selected, NO action.')
      exit 0
    end

    n_processed=0
    nrx_name_list=''
    java_name_list=''
    keep_name=list=''

    loop ix = 1 to n_files

       in_file = file_stem[ix]
       ReyMsg.info('File: ' infile 'will be documented')

       FD_in_file=ReyFile.FD(in_file)

       ft = ReyFile.FileType(in_file).lower() -- must convert to
lowercase for Case statement
       if ft \='nrx' then iterate -- only NetRexx Files will be processed
       mod_name=ReyFile.file_name(ft) -- the module-name
       nrx_name=in_file               -- the full nextrexx name
       java_name=ReyFile.FileIdd(mod_name,'java')
       keep_name=ReyFile.FileId(mod_name,'java.keep')
       info('NetRexx Module:' mod_name)
       info('NetRexx Keep file:' keep_name)
       info('Associated Java File (after renaming):' java_name)
       n_nrx=n_nrx + 1
    end--loop ix

    ReyMsg.info0(n_nrx 'NetRexx source programs will be processed.')

    t2=time('E')
    t=Rexx(t2-t1).format(7,5).strip('L').strip('T','0')

    info('')
    info('NRCDOC used' t 'seconds ('n_nrx 'NetRexx Programs')
    info('LOGFILE in nrcdoc.log')

    ReyMsg.closeLog()
    exit 0

NetRexx portable processor, version 2.05
Copyright (c) IBM Corporation, 2005.  All rights reserved.
Program nrcdoc.nrx
  12 +++ class nrcdoc uses ReyFile, ReyMsg, ReyFunc, ReyTime
     +++       ^^^^^^
     +++ Error: 'Class nrcdoc' instruction has already been implied for
this program
Compilation of 'nrcdoc.nrx' failed [2 classes, one error]

--
Thomas Schneider Projects ReyC & LOGOS on www.KENAI.com
_______________________________________________
Ibm-netrexx mailing list
[hidden email]

[George Hovey-2]

Yes, this message could be expressed in a way more helpful to the newbie :).

There are communications here (other than hand wringing) worth preserving for the day when NetRexx source becomes available.   Would it be desirable to define some ad hoc means of preserving suggestions for improvements for use on that happy day?  There have been a number of these.

On Thu, Aug 19, 2010 at 9:24 AM, Thomas Schneider <[hidden email]> wrote:

 Hello there,
  whilst we are on the issues of 'Netrexx bugs':

1.) It is a pity, that in the year 2010 neither ibm-netrexx nor REXXLA does allow *attached files*
fto communicate a problem (*personal opinion*) :-(

2.) This would simplify the reporting of problems or distributing example programs of a reasonable length
a lot (*personal opinion*) :-)

3.) The objective of this mail is to show you a*small* deficiency of the *current :NetRexx Compiler*

When a *wrong* syntax (as in the example below) is used, a totally misleading error message is given!

Note, for instance, that NetRexxC reports:

Error: 'Class nrcdoc' instruction has already been implied for this program

whilst the (*my*) error is much more trivial:

  (the *********************************************/ at the end of an already closed comment)

As I did learn that by my own faults, I can live with this ...

but maybe it should be corrected in NetRexx 3 ??

Tom.
================================================================================

/**
 * nrcdoc.nrx: a small implementation of NetRexx documentation tool
 * @author Th. Schneider, www.thsitc.com, all rights reserved
 */
/**
 * @History
 * 16.08.2010 : Original (trial) version
 */*****************************************************/

import com.thsitc.rey.rt.

class nrcdoc uses ReyFile, ReyMsg, ReyFunc, ReyTime

properties private static

  version='0.2'
  ix = int 0
  FD_in_file = ReyFile Null
  in_file = Rexx ''

  file_list = Rexx ''
  extensions  = Rexx ''
  file_stem = Rexx '' /* the Stem returned by FileList */

  recursive= boolean 1 /* flag whether recursive is wanted */
  n_nrx        = int 0 -- total number of NetRexx Sources
  n_documented = int 0 -- total number of documented files
  n_java       = int 0 -- total num

  recursive=boolean 0 -- flag wether directory recursion should be used

method main(args=String[]) public static
  arg=Rexx(args) -- program arguments as single string
  arg=arg -- avoid NetRexx warning

  t1=time('R')

  arg=arg.changestr(' since ',' SINCE ') /* as we do not have a parse caseless in NetRexx */

  init_info('nrcdoc','NEW')  /* LOG-File of last 'nrcdoc' command */
  info('NRCDOC vs. 'version)

  if arg='' then do
     info(' ')
     info('NRCDOC builds a JavaDoc style documentation for all NetRexx')
     info('       programs of a given directory and all of it\'s')
     info('       subdirectories (unless option NOREC is used')
     info(' ')
     info('short invocation:')
     info(' ')
     info('NRCDOC file-list [-option1 ...]')
     info('')
     info('Option -NOREC suppresses the recursive execution of all subdirectories')
     info(' ')

     file_list=arg -- process givenALL files of ALL subdirectories
     -- options still not processed
     yes_no=askfor('Should directories be recursed','yes/no')
     -- ReyMsg.debug('yes_no is:' yes_no)

     if yes_no='yes' then recursive=1
     else recursive = 0
 end
 else do
    parse arg . ' -' option
    option = option.upper()
    select case option
       when '' then nop
       when 'NOREC' then recursive=0
       otherwise ReyMsg.abort('illegal option: 'option)
    end

 end


 nf = 0

 /* we are interested in ALL Files here */
 extensions='nrx' -- we are ONLY interested in NetRexx files

 if recursive=0 then dir_name='' -- only current directory
 else dir_name='*'               -- indicates current directory and all sub-directories

 /* note that FileList does now return the FULL file-name */
 file_stem=ReyFile.FileList(file_list,dir_name,extensions) /* expand filelist */

 /* note that file_stem is a STEM! */
  n_files=file_stem[0]
  if n_files=0 then do
    info0(n_files 'selected, NO action.')
    exit 0
  end

  n_processed=0
  nrx_name_list=''
  java_name_list=''
  keep_name=list=''

  loop ix = 1 to n_files

     in_file = file_stem[ix]
     ReyMsg.info('File: ' infile 'will be documented')

     FD_in_file=ReyFile.FD(in_file)

     ft = ReyFile.FileType(in_file).lower() -- must convert to lowercase for Case statement
     if ft \='nrx' then iterate -- only NetRexx Files will be processed
     mod_name=ReyFile.file_name(ft) -- the module-name
     nrx_name=in_file               -- the full nextrexx name
     java_name=ReyFile.FileIdd(mod_name,'java')
     keep_name=ReyFile.FileId(mod_name,'java.keep')
     info('NetRexx Module:' mod_name)
     info('NetRexx Keep file:' keep_name)
     info('Associated Java File (after renaming):' java_name)
     n_nrx=n_nrx + 1
  end--loop ix

  ReyMsg.info0(n_nrx 'NetRexx source programs will be processed.')

  t2=time('E')
  t=Rexx(t2-t1).format(7,5).strip('L').strip('T','0')

  info('')
  info('NRCDOC used' t 'seconds ('n_nrx 'NetRexx Programs')
  info('LOGFILE in nrcdoc.log')

  ReyMsg.closeLog()
  exit 0

NetRexx portable processor, version 2.05
Copyright (c) IBM Corporation, 2005.  All rights reserved.
Program nrcdoc.nrx
 12 +++ class nrcdoc uses ReyFile, ReyMsg, ReyFunc, ReyTime
   +++       ^^^^^^
   +++ Error: 'Class nrcdoc' instruction has already been implied for this program
Compilation of 'nrcdoc.nrx' failed [2 classes, one error]

--
Thomas Schneider Projects ReyC & LOGOS on www.KENAI.com
_______________________________________________
Ibm-netrexx mailing list
[hidden email]

_______________________________________________
Ibm-netrexx mailing list
[hidden email]

[measel]

#3) If you specify a "main" then do it like this:

class bsController
...
...

method main(eparg = String[], epprt = java.io.PrintStream) public static
         
        bsController(eparg, epprt)
       
method bsController(arg = String[], prtWrt = java.io.PrintStream)
signals InterruptedException      
        fd = SimpleDateFormat("MM/dd/yy hh:mm:ss a z")
...

-----Original Message-----
From: [hidden email]
[mailto:[hidden email]] On Behalf Of Thomas
Schneider
Sent: Thursday, August 19, 2010 8:25 AM
To: IBM Netrexx
Subject: [Ibm-netrexx] NetRexx Compiler Deficiency -- leading wrong
syntax not recognized properly


  Hello there,
    whilst we are on the issues of 'Netrexx bugs':

1.) It is a pity, that in the year 2010 neither ibm-netrexx nor REXXLA
does allow *attached files*
fto communicate a problem (*personal opinion*) :-(

2.) This would simplify the reporting of problems or distributing
example programs of a reasonable length
a lot (*personal opinion*) :-)

3.) The objective of this mail is to show you a*small* deficiency of the

*current :NetRexx Compiler*

When a *wrong* syntax (as in the example below) is used, a totally
misleading error message is given!

Note, for instance, that NetRexxC reports:

Error: 'Class nrcdoc' instruction has already been implied for this
program

whilst the (*my*) error is much more trivial:

    (the *********************************************/ at the end of an

already closed comment)

As I did learn that by my own faults, I can live with this ...

but maybe it should be corrected in NetRexx 3 ??

Tom.
========================================================================
========

/**
  * nrcdoc.nrx: a small implementation of NetRexx documentation tool
  * @author Th. Schneider, www.thsitc.com, all rights reserved
  */
/**
  * @History
  * 16.08.2010 : Original (trial) version
  */*****************************************************/

import com.thsitc.rey.rt.

class nrcdoc uses ReyFile, ReyMsg, ReyFunc, ReyTime

properties private static

    version='0.2'
    ix = int 0
    FD_in_file = ReyFile Null
    in_file = Rexx ''

    file_list = Rexx ''
    extensions  = Rexx ''
    file_stem = Rexx '' /* the Stem returned by FileList */

    recursive= boolean 1 /* flag whether recursive is wanted */
    n_nrx        = int 0 -- total number of NetRexx Sources
    n_documented = int 0 -- total number of documented files
    n_java       = int 0 -- total num

    recursive=boolean 0 -- flag wether directory recursion should be
used

method main(args=String[]) public static
    arg=Rexx(args) -- program arguments as single string
    arg=arg -- avoid NetRexx warning

    t1=time('R')

    arg=arg.changestr(' since ',' SINCE ') /* as we do not have a parse
caseless in NetRexx */

    init_info('nrcdoc','NEW')  /* LOG-File of last 'nrcdoc' command */
    info('NRCDOC vs. 'version)

    if arg='' then do
       info(' ')
       info('NRCDOC builds a JavaDoc style documentation for all
NetRexx')
       info('       programs of a given directory and all of it\'s')
       info('       subdirectories (unless option NOREC is used')
       info(' ')
       info('short invocation:')
       info(' ')
       info('NRCDOC file-list [-option1 ...]')
       info('')
       info('Option -NOREC suppresses the recursive execution of all
subdirectories')
       info(' ')

       file_list=arg -- process givenALL files of ALL subdirectories
       -- options still not processed
       yes_no=askfor('Should directories be recursed','yes/no')
       -- ReyMsg.debug('yes_no is:' yes_no)

       if yes_no='yes' then recursive=1
       else recursive = 0
   end
   else do
      parse arg . ' -' option
      option = option.upper()
      select case option
         when '' then nop
         when 'NOREC' then recursive=0
         otherwise ReyMsg.abort('illegal option: 'option)
      end

   end


   nf = 0

   /* we are interested in ALL Files here */
   extensions='nrx' -- we are ONLY interested in NetRexx files

   if recursive=0 then dir_name='' -- only current directory
   else dir_name='*'               -- indicates current directory and
all sub-directories

   /* note that FileList does now return the FULL file-name */
   file_stem=ReyFile.FileList(file_list,dir_name,extensions) /* expand
filelist */

   /* note that file_stem is a STEM! */
    n_files=file_stem[0]
    if n_files=0 then do
      info0(n_files 'selected, NO action.')
      exit 0
    end

    n_processed=0
    nrx_name_list=''
    java_name_list=''
    keep_name=list=''

    loop ix = 1 to n_files

       in_file = file_stem[ix]
       ReyMsg.info('File: ' infile 'will be documented')

       FD_in_file=ReyFile.FD(in_file)

       ft = ReyFile.FileType(in_file).lower() -- must convert to
lowercase for Case statement
       if ft \='nrx' then iterate -- only NetRexx Files will be
processed
       mod_name=ReyFile.file_name(ft) -- the module-name
       nrx_name=in_file               -- the full nextrexx name
       java_name=ReyFile.FileIdd(mod_name,'java')
       keep_name=ReyFile.FileId(mod_name,'java.keep')
       info('NetRexx Module:' mod_name)
       info('NetRexx Keep file:' keep_name)
       info('Associated Java File (after renaming):' java_name)
       n_nrx=n_nrx + 1
    end--loop ix

    ReyMsg.info0(n_nrx 'NetRexx source programs will be processed.')

    t2=time('E')
    t=Rexx(t2-t1).format(7,5).strip('L').strip('T','0')

    info('')
    info('NRCDOC used' t 'seconds ('n_nrx 'NetRexx Programs')
    info('LOGFILE in nrcdoc.log')

    ReyMsg.closeLog()
    exit 0

NetRexx portable processor, version 2.05
Copyright (c) IBM Corporation, 2005.  All rights reserved.
Program nrcdoc.nrx
  12 +++ class nrcdoc uses ReyFile, ReyMsg, ReyFunc, ReyTime
     +++       ^^^^^^
     +++ Error: 'Class nrcdoc' instruction has already been implied for
this program
Compilation of 'nrcdoc.nrx' failed [2 classes, one error]

--
Thomas Schneider Projects ReyC & LOGOS on www.KENAI.com
_______________________________________________
Ibm-netrexx mailing list
[hidden email]


_______________________________________________
Ibm-netrexx mailing list
[hidden email]

[Aviatrexx]

On 8/19/10 13:24 Thomas Schneider said:
>
> 1.) It is a pity, that in the year 2010 neither ibm-netrexx nor REXXLA
> does allow *attached files*
> fto communicate a problem (*personal opinion*) :-(

Tom, does the adage "Don't look a gift horse in the mouth" mean
anything to you?  (This refers to the fact that a horse's teeth
continue to erupt and thus provide a rough measure of its age.  In
other words, if someone were to be so generous as to give you a horse,
you shouldn't complain about it being an older one.)

All of the resources required to provide the IBM-NetRexx listserver to
you (and the rest of us) are given free of charge by IBM and the
patient (and these days, long-suffering) list administrator who
watches over it for us.

The same is true for the RexxLA members' private discussion
listserver.  It runs on an IBM x220 server that I bought and donated
to RexxLA, the Internet connectivity is donated by SafeData, and it is
being administered by another long-suffering volunteer.

If Ths-ITC would contribute 20 Euros a month to pay for all the free
advertising that you have been placing on these lists, we might be
able to afford to fund someone to implement and support a more robust
discussion forum that allows you to post attachments.

When can we expect your check?  We also accept PayPal.

-Chip-
_______________________________________________
Ibm-netrexx mailing list
[hidden email]

[Thomas.Schneider.Wien]

  Ok, I got the message, Chip ;-)
My teeth have been looking like that of a horse anyway since I'm born
(genetic property I got from my husband)
I will try to *not propose* naymory anything which seems to be so easy
for me, but obviously isn't so easy.

and sorry, no money, as no sales...
I will keep in touch with those lists anyway, but will stick myself even
*more strongly* to the rules imposed:

Don't try to change anything of the behaviour as it is ! <grin>

Thomas.
Am 20.08.2010 09:56, schrieb Chip Davis:

> On 8/19/10 13:24 Thomas Schneider said:
>>
>> 1.) It is a pity, that in the year 2010 neither ibm-netrexx nor
>> REXXLA does allow *attached files*
>> fto communicate a problem (*personal opinion*) :-(
>
> Tom, does the adage "Don't look a gift horse in the mouth" mean
> anything to you?  (This refers to the fact that a horse's teeth
> continue to erupt and thus provide a rough measure of its age.  In
> other words, if someone were to be so generous as to give you a horse,
> you shouldn't complain about it being an older one.)
>
> All of the resources required to provide the IBM-NetRexx listserver to
> you (and the rest of us) are given free of charge by IBM and the
> patient (and these days, long-suffering) list administrator who
> watches over it for us.
>
> The same is true for the RexxLA members' private discussion
> listserver.  It runs on an IBM x220 server that I bought and donated
> to RexxLA, the Internet connectivity is donated by SafeData, and it is
> being administered by another long-suffering volunteer.
>
> If Ths-ITC would contribute 20 Euros a month to pay for all the free
> advertising that you have been placing on these lists, we might be
> able to afford to fund someone to implement and support a more robust
> discussion forum that allows you to post attachments.
>
> When can we expect your check?  We also accept PayPal.
>
> -Chip-
> _______________________________________________
> Ibm-netrexx mailing list
> [hidden email]
>
>

--
Thomas Schneider Projects ReyC & LOGOS on www.KENAI.com
_______________________________________________
Ibm-netrexx mailing list
[hidden email]

[Thomas.Schneider.Wien]

  Hello Chip again,
    as a *return* for the chances to make my *free* advertisements at
those lists, I gave the REXX Community Rexx2Nrx
as a *free* product anyway. Look at the statististics (the green Button
at the bottom of www.Rexx2Nrx.com) for the number of
accesses since published.
    I do NOT know, how many source lines have been converted, But I
think it has been a fair play for both parties.
Issue closed from my side.
TOM.
PS: And I will be even MORE careful to NOT open any issues here when not
absolutely needed :-(

Am 20.08.2010 09:56, schrieb Chip Davis:

> On 8/19/10 13:24 Thomas Schneider said:
>>
>> 1.) It is a pity, that in the year 2010 neither ibm-netrexx nor
>> REXXLA does allow *attached files*
>> fto communicate a problem (*personal opinion*) :-(
>
> Tom, does the adage "Don't look a gift horse in the mouth" mean
> anything to you?  (This refers to the fact that a horse's teeth
> continue to erupt and thus provide a rough measure of its age.  In
> other words, if someone were to be so generous as to give you a horse,
> you shouldn't complain about it being an older one.)
>
> All of the resources required to provide the IBM-NetRexx listserver to
> you (and the rest of us) are given free of charge by IBM and the
> patient (and these days, long-suffering) list administrator who
> watches over it for us.
>
> The same is true for the RexxLA members' private discussion
> listserver.  It runs on an IBM x220 server that I bought and donated
> to RexxLA, the Internet connectivity is donated by SafeData, and it is
> being administered by another long-suffering volunteer.
>
> If Ths-ITC would contribute 20 Euros a month to pay for all the free
> advertising that you have been placing on these lists, we might be
> able to afford to fund someone to implement and support a more robust
> discussion forum that allows you to post attachments.
>
> When can we expect your check?  We also accept PayPal.
>
> -Chip-
> _______________________________________________
> Ibm-netrexx mailing list
> [hidden email]
>
>

--
Thomas Schneider Projects ReyC & LOGOS on www.KENAI.com
_______________________________________________
Ibm-netrexx mailing list
[hidden email]

[alansam]

On 20 August 2010 00:56, Chip Davis <[hidden email]> wrote:

On 8/19/10 13:24 Thomas Schneider said:

1.) It is a pity, that in the year 2010 neither ibm-netrexx nor REXXLA does allow *attached files*
fto communicate a problem (*personal opinion*) :-(

Tom, does the adage "Don't look a gift horse in the mouth" mean anything to you?  (This refers to the fact that a horse's teeth continue to erupt and thus provide a rough measure of its age.  In other words, if someone were to be so generous as to give you a horse, you shouldn't complain about it being an older one.)

Added to which; in this Intertubes age it's not beyond the wit of man to deposit said attachment on a public web server (www.dropbox.com, www.idrive.com, one.ubuntu.com etc. Or even www.thsitc.com) and then just post URL links to them in the message.  That way other member's mailboxes don't fill up with monster file attachments.  (Inbox space isn't free either, even if it's just quota limits.)

Alan.
--
Can't tweet, won't tweet!

_______________________________________________
Ibm-netrexx mailing list
[hidden email]

[Thomas.Schneider.Wien]

Hello Alan & all,
   I will *change* my personal behaviour and will use URL's in the future ...
  
   I am using attached files a lot, but *do understand* your concerns, and will folow this advise.

Issue of attached files closed.

For the *NetRexx Compiler Deficiency* with incorrect syntax preceeding the first NetRexx statement:

issue open for the maintainers of the NetRexxC compiler,
But issue also closed from my side!
Tom.

PS: and I will try to do my best to only rais 1 issue by topic and not 3 concurrently.
I'm still able to learn (or, at least, am trying to do so ...) ===========================================================================:
Am 20.08.2010 18:07, schrieb Alan Sampson:

On 20 August 2010 00:56, Chip Davis <[hidden email]> wrote:

On 8/19/10 13:24 Thomas Schneider said:

1.) It is a pity, that in the year 2010 neither ibm-netrexx nor REXXLA does allow *attached files*
fto communicate a problem (*personal opinion*) :-(

Tom, does the adage "Don't look a gift horse in the mouth" mean anything to you?  (This refers to the fact that a horse's teeth continue to erupt and thus provide a rough measure of its age.  In other words, if someone were to be so generous as to give you a horse, you shouldn't complain about it being an older one.)

Added to which; in this Intertubes age it's not beyond the wit of man to deposit said attachment on a public web server (www.dropbox.com, www.idrive.com, one.ubuntu.com etc. Or even www.thsitc.com) and then just post URL links to them in the message.  That way other member's mailboxes don't fill up with monster file attachments.  (Inbox space isn't free either, even if it's just quota limits.)

Alan.
--
Can't tweet, won't tweet!

_______________________________________________
Ibm-netrexx mailing list
[hidden email]

_______________________________________________
Ibm-netrexx mailing list
[hidden email]

[Aviatrexx]

On 8/20/10 16:07 Alan Sampson said:
> Added to which; in this Intertubes age it's not beyond the wit of man to
> deposit said attachment on a public web server (www.dropbox.com ...
> Or even www.thsitc.com) and then just post URL links to them in the
> message.  That way other member's mailboxes don't fill up with monster
> file attachments.  (Inbox space isn't free either, even if it's just
> quota limits.)

Delightfully expressed, Alan!  (Although your phrase does evoke Neil
Armstrong saying "man" when he intended to say "a man". ;-)

These days, another consideration is the length of time it takes to
download such an attachment on a handheld smartphone.

-Chip-
_______________________________________________
Ibm-netrexx mailing list
[hidden email]