HDTenEightyP/NetNews huggingface dataset:
From: deudon@goofi.greco-prog.fr (DEUDON Guillaume.)
Newsgroups: comp.lang.eiffel
Subject: Re: LaTeX style for Eiffel code
Date: 13 Apr 92 07:47:55 GMT
Organization: Computer Engineering,ENSERB,University Of Bordeaux,FRANCE.

In article <1992Apr8.011346.19205@monu6.cc.monash.edu.au> gmaughan@monu6.cc.monash.edu.au (Glenn Maughan) writes:
>Does anyone know of a LaTeX style sheet for formatting Eiffel code.
>
>I would like it to adhere to the standards set out in OOSC (Meyer). 
>That is, keywords highlighted, comments lighlighted with arguments in
>italics, etc.
>
>If anyone finds one could you email it me?
>
>Thanks,
>
>Glenn Maughan
>email: gmaughan@monu6.monash.edu.au
>
>-- 
>Glenn Maughan
>Software Development Honours
>email: gmaughan@monu6.monash.edu.au

From a recent posting to comp.sources.misc:

{Posting-number: Volume 26, Issue 113
{Archive-name: c++2latex/part01
{Environment: C++, LaTeX

{This is version 2.0 of C++2latex originally written by Norbert Kiesel.

{c++2latex is a tool for generating LaTeX sources from ANSI-C or C++
{programs.   It recogizes all keywords, strings, and comments. These 
{recognized parts can be typeset in different fonts.   c++2latex can
{generate complete LaTeX files which can pass directly through latex(1)
{or parts of LaTeX files which can be included in other files (either
{direct or by the \input or \include commands).

The source code for it may be available by ftp at 'ftp.uu.net'
in /usenet/comp.sources.misc/volume26 (I hope so !).

It seems to me you just have to change the 'c++2latex.l' file (a lex input file
wich contains a brief description of the language, ...) to get what you want !

Good luck !

Guillaume DEUDON.


-- 
[g.d]

-----------------------------------------------------------------------------
              "These are a few of my favourite things ..."
From: partha@aramis.rutgers.edu (a_zombie)
Newsgroups: comp.lang.eiffel
Subject: views and dynamic binding
Keywords: help, example in meyer's book (pg 272 in my version)
Date: 7 Apr 92 22:06:35 GMT
Organization: Rutgers Univ., New Brunswick, N.J.


This is related to the example given in the book (OOS/W Construction).
The example talks about how to create different 'views' ( in database sense)
of the same data structure using exports and inheritance:

It defines a class bank_account with all the procedures but without exporting 
any, different views like clerk_view,customer_view etc are direct children 
of the class bank_account with different exports.

Now suppose in one top level class ( like session) i need to have different
views of the a same account:

I am confused about how to do it:

first of all when i create a new account: should i create a bank_account entity
or a manager_view entity  or  a customer_view entity? Basically it is not clear
to me how different views could be refered to the same account object.

Perhaps reverse assignment attempt will be useful here: create the account as 
bank_account type and reverse assign to different views.
Then the routines in session has to  be written in terms of the class 
type  to which it dynamically binds after the reverse assignment to satisfay 
static type checking of eiffel.  Is this the correct
way to do it?  Am I missing some simple things?


Any help is greatly appreciated.



--partha
From: news@svin02.info.win.tue.nl (Usenet account)
Newsgroups: comp.lang.eiffel
Subject: Eiffel
Keywords: concurrency
Date: 14 Apr 92 14:11:50 GMT
Followup-To: poster
Organization: Eindhoven University of Technology, The Netherlands

This article should appear in An Eiffel Collection, but
I don't know how to get a copy of that. Please help me!!!
My interest is how to handle concurrency in Eiffel. Maybe by
asynchronous message passing?
Greetings, Roger W.H. Bons, dept. comp. science, 
Eindhoven University of Technology
From: pauls@parst1.uucp (Paul  Strydom)
Newsgroups: comp.lang.eiffel
Subject: D-Flat source code wanted
Date: 7 Apr 92 16:46:30 GMT
Organization: Paradigm Systems Technology

Does anybody know about a compact public domain version of Eiffel ?

Thanks in advance
-- 
Paul Strydom                | 
Paradigm Systems Technology |
Pretoria, South Africa      | UUCP : pauls@parst1.UUCP                 
++27-12-342-2835            | BANG : ..!ddsw1!olsa99!tabbs!parst1!pauls
From: priestm@sun.pcl.ac.uk (Mark Priestley)
Newsgroups: comp.lang.eiffel
Subject: Re: Assertions for programming design
Date: 7 Apr 92 11:42:21 GMT
Organization: Polytechnic of Central London

In article <1992Apr6.143103.6335@merlin.hgc.edu> jcm@hgc.edu (James McKim) writes:

>>[Stuff about specifying stacks deleted]
>>
>>One way of doing it would be to add "class axioms" to the language, by analogy
>>with the "package axioms" used in Anna (an annotation language defined by David
>>Luckham et al for specifying Ada programs: described in a book "Programming
>>with Specifications", pub. Springer Verlag). This would allow the writing of
>>assertions like (excuse the syntax which I've just made up)
>>
>>    after (push;pop) : top = (old self).top
>>
>>- but it would take a *lot* of work to translate this into run-time checks.

>  Is the translation into run-time checks done in Anna? Enquiring minds... :-)

I believe the Anna people have implemented a number of tools to support the use
of Anna, including the generation of at least some run-time checks - but I've
not had time to investigate in detail. There are more details in the back of
the book.


>   Well, there are only a finite number of attributes in a class, so I'm
>   not convinced there is any theoretical problem with specifying  "nothing else 
>   changes". There may well _be_ such a problem and I just don't see it yet.
>   Certainly there is no such problem in this example. Making up some syntax
>   of my own, we just need something like
>
>     for_all i, 1..(depth-1) (item(i) = old item(i))
>
>   as a postcondition on both push and pop. Obviously life for the
>   designer of the class would be a lot simpler if "no change" is the
>   default. 

Yes, like you I can see no theoretical problem in specifying "no change" -
though it can clutter up a specification something terrible - but how easy
would it be to generate the appropriate assertions automatically? And there are
cases where no change at the abstract level is not equivalent to no change at
the implementation level: I think Hoare has an example somewhere where a set is
implemented as a sequence - a membership test might reposition the element at
the front of the sequence, on the assupmtion that this will make subsequent
accesses quicker. This of course doesn't affect the logical properties of the
set. So maybe there's a danger of overspecifying an implementation if "no
change" is taken literally.

-- 
Mark Priestley  (priestm@sun.pcl.ac.uk)
School of Computer Science ...
Polytechnic of Central London
From: ForthNet@willett.pgh.pa.us (ForthNet articles from GEnie)
Newsgroups: comp.lang.forth
Subject: Graphics, GUIs, and Events
Date: 11 Apr 92 16:01:55 GMT
Organization: (n.) to be organized.  But that's not important right now.

Category 10,  Topic 33
Message 3         Tue Mar 31, 1992
B.DUNN5 [Brian]              at 02:25 EST
 
One funny thing about FIG, it's so small that it can sort of just 'declare'
something which people mostly agree on, and it's so.

Imagine if someone proposed this in C, most people wouldn't even hear of it
unless some big vendor used it.  And do Turbo C and Microsoft C use the same
commands for graphics???
-----
This message came from GEnie via willett.  You *cannot* reply to the author
using e-mail.  Please post a follow-up article, or use any instructions
the author may have included (USMail addresses, telephone #, etc.).
Report problems to: dwp@willett.pgh.pa.us
From: ForthNet@willett.pgh.pa.us (ForthNet articles from GEnie)
Newsgroups: comp.lang.forth
Subject: Forth project in New Orleans
Date: 10 Apr 92 11:18:31 GMT
Organization: (n.) to be organized.  But that's not important right now.

Category 11,  Topic 6
Message 1         Mon Apr 06, 1992
S.SQUIRES                    at 02:44 EDT
 
I'm re-posting this note from another BBS so don't leave E-mail here.
  -scott


Fm: JAY WILLIAMS 


I am trying to find a Forth users group I can contact who might help me find 3-
4 Forth consultants for a long term project in New Orleans. developers. 
Please give me a call at 212-410-1400.
                       Thanks- Jay

-----
This message came from GEnie via willett.  You *cannot* reply to the author
using e-mail.  Please post a follow-up article, or use any instructions
the author may have included (USMail addresses, telephone #, etc.).
Report problems to: dwp@willett.pgh.pa.us
From: ForthNet@willett.pgh.pa.us (ForthNet articles from GEnie)
Newsgroups: comp.lang.forth
Subject: ANS FORTH TECHNICAL COMMITTEE
Date: 11 Apr 92 16:01:31 GMT
Organization: (n.) to be organized.  But that's not important right now.

Category 10,  Topic 2
Message 134       Thu Apr 02, 1992
B.DUNN5 [Brian]              at 02:25 EST
 
 

 >         STACK DIAGRAMS ARE NOT ENOUGH!

 I also suggested quick examples for anything which seemed appropriate.

 The idea here is to let people start using ANS-Forth'ish code in examples for
other things, not so that every beginner may instantly make his own ANS
system.  I keep saying that the business of prelude files and such must be
done by someone who knows what they are doing.

 Just recently Jack posted a message including code which he says should be
ANS-Forth compatable.  Why can't the rest of us?

 I never dreamed that a glossary would be such a cause of war.

-----
This message came from GEnie via willett.  You *cannot* reply to the author
using e-mail.  Please post a follow-up article, or use any instructions
the author may have included (USMail addresses, telephone #, etc.).
Report problems to: dwp@willett.pgh.pa.us
Newsgroups: comp.lang.forth
From: anton@mips.complang.tuwien.ac.at (Anton Martin Ertl)
Subject: Electronic Distribution of Draft Standards
Organization: Technische Universitaet Wien
Date: Fri, 10 Apr 1992 14:13:19 GMT

A few weeks ago the draft standard for ISO Prolog was submitted.
And it's available electronically, for free (for details see message
<1992Apr9.152236.8792@doc.ic.ac.uk> in comp.lang.prolog,
"Subject: ISO Prolog draft standard available").

Free electronic distribution is fast, cheap, and adds some value
(searching by computer), but it has not been used for the last ANSI Forth
draft. The reason given was that ANSI needs the money.
If ANSI sells the standards, that's OK, since an accepted standard is
worth quite a bit (to some people, e.g. vendors).

However, a draft has no commercial value, so it should be distributed
cheaply to achieve good response. E.g., I did not invest the $65 and at
least an hour of work to get the last ANSI Forth draft (which is now
wastepaper), so I did not comment. I probably will order the final version.

So, could somone (i.e. the ANSI Forth TC members) get this message to ANSI.
I'm sure that "ISO is more state-of-the-art than ANSI" will make them
act:-) I guess that the drafts for this ANSI Forth will not yet be
distributed electronically and freely, but hopefully the drafts for the
next standard.

-- 
M. Anton Ertl                    Some things have to be seen to be believed
anton@mips.complang.tuwien.ac.at Most things have to be believed to be seen
From: ForthNet@willett.pgh.pa.us (ForthNet articles from GEnie)
Newsgroups: comp.lang.forth
Subject: What should the Standard include?
Date: 11 Apr 92 16:01:48 GMT
Organization: (n.) to be organized.  But that's not important right now.

Category 10,  Topic 30
Message 172       Mon Apr 06, 1992
E.RATHER [Elizabeth]         at 01:40 EDT
 
We've dicussed factoring the CORE EXTENSIONS further, but don't feel that
either CASE or DEFER merit such factoring.  It's not expected that CORE
EXTENSIONS has any coherance as an entity, beyond being a grab-bag of possibly
useful words that implementors will *select* their favorites from.  I'd be
inclined to regard someone intent on blindly including the whole thing as
lacking discrimination.  Some words there, for example, are being deprecated
and may be dropped next round (e.g., EXPECT, deprecated in favor of ACCEPT).

DEFER has been considered & rejected several times.  It will not be included.

CSI's structures have not been considered that I remember, but I believe the
TC would be extremely reluctant to consider them at this stage.
-----
This message came from GEnie via willett.  You *cannot* reply to the author
using e-mail.  Please post a follow-up article, or use any instructions
the author may have included (USMail addresses, telephone #, etc.).
Report problems to: dwp@willett.pgh.pa.us
From: ForthNet@willett.pgh.pa.us (ForthNet articles from GEnie)
Newsgroups: comp.lang.forth
Subject: Feedback to the Forth Interest Group
Date: 8 Apr 92 12:33:43 GMT
Organization: (n.) to be organized.  But that's not important right now.

Category 1,  Topic 2
Message 159       Sun Mar 29, 1992
B.RODRIGUEZ2 [Brad]          at 08:52 EST
 
Doug: two problems with the private BBS approach.

First, there is the problem of continuity; private BBSs tend to come and go as
their sysops get bored, get new jobs, move, get new computers, etc.  Perhaps
this could be remedied by having it run from the FIG office.

Second, public data networks are often more expensive.  Example: a year or two
ago GEnie announced that it was available through Canada's Datapac.  My hopes
were dashed when I found out that it's _cheaper_ for me to call a GEnie node
long-distance, than to subscribe to Datapac.  (Does PCPursuit cover Canada?)

- Brad

P.S. minor geographical note: the U.S. is not the Northern Hemisphere, or even
North America -- just part of it. :-)
-----
This message came from GEnie via willett.  You *cannot* reply to the author
using e-mail.  Please post a follow-up article, or use any instructions
the author may have included (USMail addresses, telephone #, etc.).
Report problems to: dwp@willett.pgh.pa.us
From: ForthNet@willett.pgh.pa.us (ForthNet articles from GEnie)
Newsgroups: comp.lang.forth
Subject: Graphics, GUIs, and Events
Date: 12 Apr 92 13:13:38 GMT
Organization: (n.) to be organized.  But that's not important right now.

Category 10,  Topic 33
Message 8         Thu Apr 09, 1992
B.RODRIGUEZ2 [Brad]          at 22:44 EDT
 
> ...assuming 'square' pixels.

NOT a safe assumption!  How do we deal with "real" aspect ratio?

Brad Rodriguez
 B.RODRIGUEZ2 on GEnie   |   bradford@maccs.dcss.mcmaster.ca
 So many projects....so little time.

-----
This message came from GEnie via willett.  You *cannot* reply to the author
using e-mail.  Please post a follow-up article, or use any instructions
the author may have included (USMail addresses, telephone #, etc.).
Report problems to: dwp@willett.pgh.pa.us
From: ForthNet@willett.pgh.pa.us (ForthNet articles from GEnie)
Newsgroups: comp.lang.forth
Subject: Who's here
Date: 13 Apr 92 12:08:33 GMT
Organization: (n.) to be organized.  But that's not important right now.


 Date: 04-07-92 (11:23)              Number: 31008 of 31027
   To: JIM WENZEL                    Refer#: 30955
 From: STEFAN BAKER                    Read: 04-10-92 (10:02)
 Subj: Hello and ??s                 Status: PUBLIC MESSAGE
 Conf: FORTH (58)                 Read Type: GENERAL (+)

 JW   due to the gracious work of Gary Smith, all messages are cross-posted
      both to Genie and InterNet/UseNet.

        Great!  Thanks for the reply.  I do appreciate it very much.

        I'm not a seasoned Forther, as yet, but I do find the language
 quite interesting and I am sure that it is going to provide me with
 everything that I will need - outside of Windows.  If WinForth is a good
 product (and I have no reason to believe that it won't be) then, maybe
 I'll drop Actor and switch to WinForth.  I dunno tho, Actor is quite a
 nice piece of work.  |-)

        Regards,
        Stefan
 ---
    JABBER v1.1   Remember - Life's a batch and then you die, or marry one.

 PCRelay:COMCTRII -> #1310 RelayNet (tm)
 4.11                Command Central II * 317-782-8094
 <<<>>>

-----
This message came from GEnie via willett.  You *cannot* reply to the author
using e-mail.  Please post a follow-up article, or use any instructions
the author may have included (USMail addresses, telephone #, etc.).
Report problems to: dwp@willett.pgh.pa.us
From: ForthNet@willett.pgh.pa.us (ForthNet articles from GEnie)
Newsgroups: comp.lang.forth
Subject: Graphics, GUIs, and Events
Date: 16 Apr 92 12:22:48 GMT
Organization: (n.) to be organized.  But that's not important right now.

Category 10,  Topic 33
Message 11        Thu Apr 16, 1992
B.DUNN5 [Brian]              at 05:15 EDT
 
 
 Re: A real metric for graphic coordinates:

 The software would need to know the physical size of your display device. It
might be useful to have both a virtual coordinate space and also a real
metric.  Example:

 The graphic operations take coordinates in a 16K by approx. 10K space , the
height being whatever will make square virtual pixels.  There is also a word
to tell the software the width and height of the physical display, and one
more word for millimeter units.

 1000   2000      10000   8000     draw_line   \ virtual coordinates
 20 mm  30 mm     250 mm  100 mm   draw_line   \ real millimeters

 Virtual coordinates are useful for making a window which takes half the
screen, no matter what particular screen size you are using.

 The word mm would be a simple */ whose ratio depends on the physical size of
the display.
-----
This message came from GEnie via willett.  You *cannot* reply to the author
using e-mail.  Please post a follow-up article, or use any instructions
the author may have included (USMail addresses, telephone #, etc.).
Report problems to: dwp@willett.pgh.pa.us
From: ForthNet@willett.pgh.pa.us (ForthNet articles from GEnie)
Newsgroups: comp.lang.forth
Subject: ANS FORTH TECHNICAL COMMITTEE
Date: 11 Apr 92 16:01:27 GMT
Organization: (n.) to be organized.  But that's not important right now.

Category 10,  Topic 2
Message 131       Mon Mar 30, 1992
E.RATHER [Elizabeth]         at 21:27 EST
 
>Without BLOCK-FID, how does one change the file used by BLOCK >and BUFFER?

There are several problems.  First, BLOCK-FID seems to imply there is only one
such file, whereas we (and others) frequently have quite a  number open at
once.  Jack Woehr coded a scheme for supporting that with BLOCK-FID, but even
he admitted it was pretty kludgy.  Second, it's really unclear what a Standard
Program that intends to migrate across a variety of host OSs (e.g. DOS, UNIX,
VMS) can do usefully. It was utterly unclear, for example, whether a user
program can store into it, when that would be legal, and what the consequence
would be. Finally, the principal intent of providing a BLOCKS/files overlap is
so that Standard Programs can migrate easily across both native and non-native
environments.  It's unclear what level support native systems would have been
forced to provide.

We received a number of comments from people who wanted BLOCK-FID to go away,
for reasons such as the above.  The proposal that passed was crafted by a
group with input from a number of people very experienced in maintaining
blocks in both native and non-native environments, who all thought that the
best way to handle the non-native situation was via a shell adapted to the
particular host Forth/OS combination which set up the block/file mapping
suitably.  All vendors of blocks-in-files provide one, and they're usually
easy to use.  Then within the standard program you can simply move about in
block space without  having to worry about files at all.
-----
This message came from GEnie via willett.  You *cannot* reply to the author
using e-mail.  Please post a follow-up article, or use any instructions
the author may have included (USMail addresses, telephone #, etc.).
Report problems to: dwp@willett.pgh.pa.us
Newsgroups: comp.lang.forth
From: jwoehr@isis.cs.du.edu (Jack J. Woehr)
Subject: Re: ANSI Forth Documentation
Keywords: ANSI
Organization: University of Denver, Dept. of Math & Comp. Sci.
Date: Sun, 12 Apr 92 02:50:54 GMT

cbbrowne@csi.uottawa.ca (Christopher Browne) writes:


< stuff deleted ... >

>- There ain't gonna be any "Starting FORTH: ANSI Version", because
>it's not the ANSI document.

	There is going to be _ANS Forth, The New Model_ by Jack
Woehr (hi, mom!) however.

>- Vesta Technology won't be able to sell a manual for their ANSI
>products, because that manual won't be the ANSI document.

	We've got that under control, thanx. You'll hear a lot of
airy theory on the 'net; but at Vesta, we're in business and we get
projects done, ergo, we'll have a manual carefully weasel-worded by
May 15, 1992 and a final document when the standard is approved, with
the weasel-words extracted like sore teeth.

>- ALL programmers working in ANSI Forth will use the infamous document
>as their only documentation, because it's the only document that can
>POSSIBLY describe the new language.

	I understand your sarcasm. What the posters should have been
saying is, "you either read the document or you buy a well-documented
Standard System to understand ANS Forth ... there ain't no middle ground".
I think my book, possibly published by the end of this year, should help
provide some middle ground. I sure as heck would be surprised if Martin
Tracy doesn't write a book, also.

>'Cmon!  There has GOT to be a time when briefer/more layman-
>approachable documentation will become available.  jaxForth must have
>a word-list in it somewhere.  Similarly, the ZenForth documentation
>probably has SOME useful information in it.

	The thing that word lists don't do is give you the Zen of
ANS Forth. You have to grok why and how it's platform independent.
Honestly, it is a very aesthetically pleasing model of Forth. It's
superb even. We just don't have time to write all the teaching stuff
this week, give us a few months and we'll have the full explanation
in your hands! Or buy the dpANS and read it yourself.

	jaxsays the quickest way to grok ans forth is to implement
dpANS.

>1) Words that are now pretty firm

	All of the CORE/DOUBLE/STRING/ERROR/SEARCH-ORDER and their 
extensions.

>2) Words that are still contentious

	This and that in all the other word sets ... not much really,
we're down to arguing about specific THROW codes and other pinhead-dancing
angels :-)

		=jax=

--
 # jax@well.{UUCP,sf.ca.us}  # #  Member, # # Vice President,       #
 # du!isis!koscej!jax        # # X3J14 TC # #  Forth Interest Group #
 # JAX on GEnie              # # for ANS  # #   P.O. Box 8231       #
 # SYSOP RCFB (303) 278-0364 # #  Forth   # #    San Jose CA 95155  #
From: ForthNet@willett.pgh.pa.us (ForthNet articles from GEnie)
Newsgroups: comp.lang.forth
Subject: Forth Taught at Schools/Universities
Date: 15 Apr 92 12:09:30 GMT
Organization: (n.) to be organized.  But that's not important right now.

Category 2,  Topic 2
Message 78        Tue Apr 14, 1992
LRWEBBER [larry]             at 21:10 EDT
 
Referencing lack of f-83 compliance,

I too would be interested in knowing violations of F-83 that were uncovered
during the committees' investigation.
-----
This message came from GEnie via willett.  You *cannot* reply to the author
using e-mail.  Please post a follow-up article, or use any instructions
the author may have included (USMail addresses, telephone #, etc.).
Report problems to: dwp@willett.pgh.pa.us