SCOUG Logo


Next Meeting: Sat, TBD
Meeting Directions


Be a Member
Join SCOUG

Navigation:


Help with Searching

20 Most Recent Documents
Search Archives
Index by date, title, author, category.


Features:

Mr. Know-It-All
Ink
Download!










SCOUG:

Home

Email Lists

SIGs (Internet, General Interest, Programming, Network, more..)

Online Chats

Business

Past Presentations

Credits

Submissions

Contact SCOUG

Copyright SCOUG



warp expowest
Pictures from Sept. 1999

The views expressed in articles on this site are those of their authors.

warptech
SCOUG was there!


Copyright 1998-2024, Southern California OS/2 User Group. ALL RIGHTS RESERVED.

SCOUG, Warp Expo West, and Warpfest are trademarks of the Southern California OS/2 User Group. OS/2, Workplace Shell, and IBM are registered trademarks of International Business Machines Corporation. All other trademarks remain the property of their respective owners.

The Southern California OS/2 User Group
USA

SCOUG-Programming Mailing List Archives

Return to [ 10 | August | 2003 ]

<< Previous Message << >> Next Message >>


Date: Sun, 10 Aug 2003 20:16:28 PDT7
From: Tom Novelli <tcn@mtdata.com >
Reply-To: scoug-programming@scoug.com
To: < "scoug-programming@scoug.com" > scoug-programming@scoug.com >
Subject: SCOUG-Programming: English as programming language (was: Warpstock 2003 Presentation)

Content Type: text/plain

On Sat, 9 Aug 2003, Lynn H. Maxson wrote:
>
> It's a pure Bill of Material (BOM) manufacturing system. Like
> any such system it allows you to "explode" an assembly down
> through its hierarchy of lower level assemblies and raw
> materials ultimately down to a list of all the raw materials
> (statements and sentences) used. It also allows you for any
> raw material or assembly to create a "where used" used
> listing. This latter allows you to make a change to source
> code, produce a listing of all affected assemblies, and alter
> the source text in those assemblies to correspond to the
> change.

I've used enough BOM systems to think there's gotta be a better way...
like plain-text files! (programmable parametric BOMs, you might say)
It's pretty typical to have 20 variations of a part on one drawing, but
the clumsy database requires 20 separate nearly identical BOMs with
nothing to indicate their similarity. As programmers we already have
plain-text source code with a well-defined syntax, so it shouldn't be that
hard to write a simplified parser to create BOMs and Where Used lists. I
haven't felt the need yet, but it might be worthwhile for something huge
like a Linux kernel.

=====================================================

To unsubscribe from this list, send an email message
to "steward@scoug.com". In the body of the message,
put the command "unsubscribe scoug-programming".

For problems, contact the list owner at
"rollin@scoug.com".

=====================================================


<< Previous Message << >> Next Message >>

Return to [ 10 | August | 2003 ]



The Southern California OS/2 User Group
P.O. Box 26904
Santa Ana, CA 92799-6904, USA

Copyright 2001 the Southern California OS/2 User Group. ALL RIGHTS RESERVED.

SCOUG, Warp Expo West, and Warpfest are trademarks of the Southern California OS/2 User Group. OS/2, Workplace Shell, and IBM are registered trademarks of International Business Machines Corporation. All other trademarks remain the property of their respective owners.