You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
c:\threadn\pompiers.fil' -> OPT Lire() OUT -> IN Select() OUT -> IN Ecrire() Select() REJECT -> IN Ecrire2() ... and so on is tough to scan! Should become:
c:\threadn\pompiers.fil' -> OPT Lire OUT -> IN Select OUT -> IN Ecrire, Select REJECT -> IN Ecrire2 ... and so on
The text was updated successfully, but these errors were encountered:
Dan has suggested we could make commas optional at the end of a line - I till feel this could cause problems, as that means our scanners have to be line-sensitive. I tend to dislike line-sensitive syntax, as I have found that you often have to some kind of escape convention meaning "this end of line is not really an end of line". And you can't divide up lines arbitrarily to make them look pretty!
For instance, let's take the line I showed in my previous note and carve it up arbitrarily as follows:
'c:\threadn\pompiers.fil' -> OPT Lire
OUT -> IN Select OUT -> IN Ecrire, Select
REJECT -> IN Ecrire2 ... and so on
IMO you have a similar problem to what I was trying to avoid - Lire is not the end of a branch because the next line starts with one token followed by an arrow, which is impossible at the beginning of a branch. I would really prefer to require commas at the end of every branch, even if it's end of line (except of course at the end of a network definition).
As suggested by @jpaulm
c:\threadn\pompiers.fil' -> OPT Lire() OUT -> IN Select() OUT -> IN Ecrire() Select() REJECT -> IN Ecrire2()
... and so on is tough to scan! Should become:c:\threadn\pompiers.fil' -> OPT Lire OUT -> IN Select OUT -> IN Ecrire, Select REJECT -> IN Ecrire2
... and so onThe text was updated successfully, but these errors were encountered: