Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Contribute to GitLab
Sign in
Toggle navigation
C
cpdt
Project
Project
Details
Activity
Cycle Analytics
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Charts
Issues
0
Issues
0
List
Board
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Charts
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Charts
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
research
cpdt
Commits
11966a58
Commit
11966a58
authored
Jun 28, 2011
by
Adam Chlipala
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Clarify need to insert hidden commands
parent
2f84edf6
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
1 addition
and
1 deletion
+1
-1
StackMachine.v
src/StackMachine.v
+1
-1
No files found.
src/StackMachine.v
View file @
11966a58
...
...
@@ -44,7 +44,7 @@ The extra arguments demonstrated here are the proper choices for working with th
#
</
ol
>
#
%
\
end
{
enumerate
}%
As
always
,
you
can
step
through
the
source
file
%
\
texttt
{%
#
<
tt
>
#
StackMachine
.
v
#
</
tt
>
#
%}%
for
this
chapter
interactively
in
Proof
General
.
Alternatively
,
to
get
a
feel
for
the
whole
lifecycle
of
creating
a
Coq
development
,
you
can
enter
the
pieces
of
source
code
in
this
chapter
in
a
new
%
\
texttt
{%
#
<
tt
>
#
.
v
#
</
tt
>
#
%}%
file
in
an
Emacs
buffer
.
If
you
do
the
latter
,
include
two
lines
[
Require
Import
Arith
Bool
List
Tactics
.
]
and
[
Set
Implicit
Arguments
.
]
at
the
start
of
the
file
,
to
match
some
code
hidden
in
this
rendering
of
the
chapter
source
,
and
be
sure
to
run
the
Coq
binary
%
\
texttt
{%
#
<
tt
>
#
coqtop
#
</
tt
>
#
%}%
with
the
command
-
line
argument
%
\
texttt
{%
#
<
tt
>
#
-
I
DIR
/
src
#
</
tt
>
#
%}%.
If
you
have
installed
Proof
General
properly
,
it
should
start
automatically
when
you
visit
a
%
\
texttt
{%
#
<
tt
>
#
.
v
#
</
tt
>
#
%}%
buffer
in
Emacs
.
As
always
,
you
can
step
through
the
source
file
%
\
texttt
{%
#
<
tt
>
#
StackMachine
.
v
#
</
tt
>
#
%}%
for
this
chapter
interactively
in
Proof
General
.
Alternatively
,
to
get
a
feel
for
the
whole
lifecycle
of
creating
a
Coq
development
,
you
can
enter
the
pieces
of
source
code
in
this
chapter
in
a
new
%
\
texttt
{%
#
<
tt
>
#
.
v
#
</
tt
>
#
%}%
file
in
an
Emacs
buffer
.
If
you
do
the
latter
,
include
two
lines
[
Require
Import
Arith
Bool
List
Tactics
.
]
and
[
Set
Implicit
Arguments
.
]
at
the
start
of
the
file
,
to
match
some
code
hidden
in
this
rendering
of
the
chapter
source
.
In
general
,
similar
commands
will
be
hidden
in
the
book
rendering
of
each
chapter
'
s
source
code
,
so
you
will
need
to
insert
them
in
from
-
scratch
replayings
of
the
code
that
is
presented
.
Also
,
be
sure
to
run
the
Coq
binary
%
\
texttt
{%
#
<
tt
>
#
coqtop
#
</
tt
>
#
%}%
with
the
command
-
line
argument
%
\
texttt
{%
#
<
tt
>
#
-
I
DIR
/
src
#
</
tt
>
#
%}%.
If
you
have
installed
Proof
General
properly
,
it
should
start
automatically
when
you
visit
a
%
\
texttt
{%
#
<
tt
>
#
.
v
#
</
tt
>
#
%}%
buffer
in
Emacs
.
With
Proof
General
,
the
portion
of
a
buffer
that
Coq
has
processed
is
highlighted
in
some
way
,
like
being
given
a
blue
background
.
You
step
through
Coq
source
files
by
positioning
the
point
at
the
position
you
want
Coq
to
run
to
and
pressing
C
-
C
C
-
RET
.
This
can
be
used
both
for
normal
step
-
by
-
step
coding
,
by
placing
the
point
inside
some
command
past
the
end
of
the
highlighted
region
;
and
for
undoing
,
by
placing
the
point
inside
the
highlighted
region
.
*
)
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment