LADSoft / LADSoft/OCIDE

FR ocide: allow lexer files (.l) to be included in the source tree

Open
#17 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C
Stars
16
Forks
1
PR merge metrics
No merged PRs in 30d

Description

Currently all ".l" files added to the project seem to be recognized as linker files, which is understandable but inconvenient as ".l" is used for (f)lex source files, too.

Error: invalid object file in line 15686 in library X:\gnucobol\cobc\scanner.l
Error: invalid object file in line 15686 in library X:\gnucobol\cobc\pplex.l

[Note: the line number seems to be strange...]

Workaround (as no "exclude from compilation" LADSoft/OrangeC#107 is available): remove these files from the project.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the issue by adding the referenced .l lexer files, such as scanner.l and pplex.l, to an OCIDE project and observe how the source tree classifies them. Trace the project-file handling from that reproduction; done means .l lexer sources can remain in the project without being reported as invalid linker or object files.

Written by the indexing model from the issue text.

Assessment

Tech stack
c
Domain
tooling
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.