Sponsored Content
The Lounge What is on Your Mind? Cyberspace Situational Awareness - End of Year Research Update Post 302988228 by rbatte1 on Thursday 22nd of December 2016 05:44:27 AM
Old 12-22-2016
I disagree with point 17

Happy Christmas Smilie
 

7 More Discussions You Might Find Interesting

1. What is on Your Mind?

Cyberspace Situation Graphs - Cyberspace Situational Awareness

Hi. I've been very busy this month working on resurrecting my old projects related to "cyberspace situational awareness" (CSA) which began last month by surveying the downstream literature that referenced my papers in this area using Google Scholar and also ResearchGate and posting updates on my... (5 Replies)
Discussion started by: Neo
5 Replies

2. What is on Your Mind?

Speed Bumps on the Road to Cyber Situational Awareness - Tim Bass

Speed Bumps on the Road to Cyber Situational Awareness Happy Holidays! (0 Replies)
Discussion started by: Neo
0 Replies

3. What is on Your Mind?

Calculating Warp Coordinates in Cyberspace - Cyberspace Situational Awareness

Please message me or post in this thread if anyone is interested in contributing some C, C++, or C# code for this project. Right now we have an open source C++ git project (created by someone else a few years ago) that fails when we try to compile on Ubuntu. I need someone to fix the make... (4 Replies)
Discussion started by: Neo
4 Replies

4. What is on Your Mind?

Application for Virtualizing CyberSpace like Outer Space for Cyberspace Situational Awareness

Richard Zuech annotates his first experience flying in virtualized cyberspace hunting the bad guys! ... and he finds some! Application for Virtualizing CyberSpace like Outer Space for Cyberspace Situational Awareness (0 Replies)
Discussion started by: Neo
0 Replies

5. What is on Your Mind?

Virtualized Cyberspace, Cyberspace Consciousness and Simulation Theory - What Do You Think?

What do you think? Read this: Virtualized Cyberspace, Cyberspace Consciousness and Simulation Theory and comment below.... Are we in a computer simulation? Yes or No? Thanks! (0 Replies)
Discussion started by: Neo
0 Replies

6. What is on Your Mind?

Virtualized Cyberspace - Visualizing Patterns & Anomalies for Cognitive Cyber Situational Awareness

Our team just published this technical report on ResearchGate: Virtualized Cyberspace - Visualizing Patterns & Anomalies for Cognitive Cyber Situational Awareness ABSTRACT ACKNOWLEDGMENTS Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International Public License This... (0 Replies)
Discussion started by: Neo
0 Replies

7. What is on Your Mind?

Back to Cyber Situational Awareness Software Development

After mulling over self-publishing a cyberspace situational awareness mini-series starting with a short book on human cyber consciousness, I think it is best I delay writing a book and focus on software development. The general idea of human cyber consciousness is indirectly discussed in this... (0 Replies)
Discussion started by: Neo
0 Replies
HAPPY(1)						      Happy Parser Generator							  HAPPY(1)

NAME
happy - the parser generator for Haskell SYNOPSIS
happy [OPTION]... file [OPTION]... DESCRIPTION
This manual page documents briefly the happy command. This manual page was written for the Debian GNU/Linux distribution because the original program does not have a manual page. Instead, it has documentation in various other formats, including DVI, Info and HTML; see below. Happy is a parser generator system for Haskell. `HAPPY' is a dyslexic acronym for `A Yacc-like Haskell Parser generator'. There are two types of grammar files, file.y and file.ly, with the latter observing the reverse comment bird track convention (i.e. each code line must begin with `>'). The examples distributed with Happy are all of the .ly form. Caveat: When using hbc (Chalmers Haskell) the command argument structure is slightly different. This is because the hbc run time system takes some flags as its own (for setting things like the heap size, etc). This problem can be circumvented by adding a single dash (`-') to your command line. So when using a hbc generated version of Happy, the argument structure is: happy - [OPTION]... file [OPTION]... OPTIONS
The programs follow the usual GNU command line syntax, with long options starting with two dashes (`--'). A summary of options is included below. For a complete description, see the other documentation. -h, --help Show summary of options. -v, --version Print version information on standard output then exit successfully. -a, --array Instructs Happy to generate a parser using an array-based shift reduce parser. When used in conjunction with -g, the arrays will be encoded as strings, resulting in faster parsers. Without -g, standard Haskell arrays will be used. -g, --ghc Instructs Happy to generate a parser that uses GHC-specific extensions to obtain faster code. -c, --coerce Use GHC's unsafeCoerce# extension to generate smaller faster parsers. One drawback is that some type safety is lost, which means that a parser generated with -c may compile fine but crash at run-time. Be sure to compile your grammar without -c first to ensure it is type-correct. This option has quite a significant effect on the performance of the resulting parser, but remember that parsers generated this way can only be compiled by GHC 3.02 and above. This option may only be used in conjuction with -g. -d, --debug Generate a parser that will print debugging information to stderr at run-time, including all the shifts, reductions, state transi- tions and token inputs performed by the parser. This option may only be used in conjuction with -a. -i [FILE], --info[=FILE] Directs Happy to produce an info file containing detailed information about the grammar, parser states, parser actions, and con- flicts. Info files are vital during the debugging of grammars. The filename argument is optional, and if omitted the info file will be written to FILE.info (where FILE is the input file name with any extension removed). -o FILE, --outfile=FILE Specifies the destination of the generated parser module. If omitted, the parser will be placed in FILE.hs, where FILE is the name of the input file with any extension removed. If FILE is - the generated parser is sent to the standard output. -m NAME, --magic-name=NAME Happy prefixes all the symbols it uses internally with either happy or Happy. To use a different string, for example if the use of happy is conflicting with one of your own functions, specify the prefix using the -m option. -t DIR, --template=DIR Instructs Happy to use this directory when looking for template files: these files contain the static code that Happy includes in every generated parser. You shouldn't need to use this option if Happy is properly configured for your computer. -l, --glr Instructs Happy to output a GLR parser instead of an LALR(1) parser. -k, --decode Causes the GLR parser to generate code for decoding the parse forest to a list of semantic results (requires --ghc). -f, --filter Causes the GLR parser to filter out nodes which aren't required for the semantic results (an experimental optimisation, requires --ghc). FILES
/usr/share/happy-1.18.9 SEE ALSO
/usr/share/doc/happy, the Happy homepage (http://haskell.org/happy/) <http://haskell.org/happy/> COPYRIGHT
Happy Version 1.18.9 Copyright (c) 1993-1996 Andy Gill, Simon Marlow; (c) 1997-2001 Simon Marlow AUTHOR
This manual page was written by Michael Weber <michaelw@debian.org>, for the Debian GNU/Linux system (but may be used by others). Glasgow FP Suite 2000-12-23 HAPPY(1)
All times are GMT -4. The time now is 03:56 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy